Difference: EventBuilder (1 vs. 28)

Revision 28
25 Jun 2014 - Main.JoernAdamczewski
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
GeneralInformation - general information about event builder machines, services running on those machines and so on.
Line: 14 to 14
 

EventBuilderDabc - NEW: Eventbuilder/trbnet implementation for DAQ framework DABC.
Added:
>
>
EventBuilder2014 - Status of eventbuilders in 2014.
Revision 27
10 Jul 2012 - Main.JoernAdamczewski
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
GeneralInformation - general information about event builder machines, services running on those machines and so on.
Line: 10 to 10
 

EventBuilder2012 - Status of eventbuilders in 2012.
Added:
>
>
EventBuilderDreamplug - NEW: Experiences with eventbuilder installations on dreamplug mini computers.
  EventBuilderDabc - NEW: Eventbuilder/trbnet implementation for DAQ framework DABC.
Revision 26
06 Jul 2012 - Main.JoernAdamczewski
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
GeneralInformation - general information about event builder machines, services running on those machines and so on.
Line: 10 to 10
 

EventBuilder2012 - Status of eventbuilders in 2012.
Added:
>
>
EventBuilderDabc - NEW: Eventbuilder/trbnet implementation for DAQ framework DABC.
Revision 25
01 Feb 2012 - Main.JoernAdamczewski
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
GeneralInformation - general information about event builder machines, services running on those machines and so on.
Line: 8 to 8
 

EventBuilderRunControl - Run Control of the Multiple Event Builders.
Added:
>
>
EventBuilder2012 - Status of eventbuilders in 2012.
Revision 24
14 Jul 2008 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Changed:
<
<
GeneralInformation
>
>
GeneralInformation - general information about event builder machines, services running on those machines and so on.
 
Changed:
<
<
EventBuilderDevelopment
>
>
EventBuilderDevelopment - information and documentation related to the development of the EB software.
 
Changed:
<
<
EventBuilderTest
>
>
EventBuilderTest - description and results of the tests performed for the Event Builder.

EventBuilderRunControl - Run Control of the Multiple Event Builders.
 
Revision 23
08 Feb 2008 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Changed:
<
<
Table of contents:
>
>
GeneralInformation
 
Changed:
<
<
>
>
EventBuilderDevelopment
 
Changed:
<
<

The following machines are dedicated DAQ-eventbuilders:

  • hadeb02
  • hadeb03
  • hadeb07 (remote backup system)
  • lxhadesdaq

hadeb02, hadeb03

These are identical machines with 2 1GHz processors. They have 1 GByte memory. Currently (14.09.05), all hades-daq-computer are connected to the Gbit/s Netgear switch.

habeb03 is now (28.01.05) stable again. It did not crash for many weeks. The nfsserver is now running again, so it can be used for writing hades-data from the event-builder which is currently used as the main eventbuilder.

hadeb02: redhat something
hadeb03: SuSE 9.2 with quite new security patches

hadeb07 (remote backup system)

hadeb07 parameters:
  • SuSE 10.2
  • Hard disks: sda+sdb = 0.32TB, sdc+sdd = 1TB. The two last disks (sdc, sdd) were additionally put into the machine to serve as backup disks. They are not really fixed inside the machine: take care when moving the machine. Nagios monitors the temperature of both disks.
  • Two 3GHz processors
  • 2GB memory

After a power outage hadeb03 experienced a hardware failure. We have decided to use hadeb07 instead of hadeb03 for the remote backup.

hadeb07 serves as a remote backup system.
  • Software: rsnapshot, executed 6 times a day (crontab -e)
  • Config file: /etc/rsnapshot.conf
  • Backup disk: /data/backup

The following machines/directories are backuped:

the backup of hades17: hades25/home/hadaq/backups/hades17_hadaq_home/

-- SergeyYurevich - 27 Nov 2007

lxhadesdaq

It is a "higher-availability computer", that means:
  • Raid 0 for the system disks
  • Raid 5 for the data disks
  • 3 redundant power supplies (we just connected them to different fuses not different phases!)
  • spare parts in the computer center

System: Debian "Sarge" (which is not available yet(2005) smile )

How to check if the SATA-RAID is still OK:

https://lxhadesdaq:1082/

Username: user

Password: waVe**** (ask Michael)

Software

For installing packages, have a look to: http://wiki.gsi.de/cgi-bin/view/Linux/DebianPaketVerwaltung

Important Debian-commands:
  • apt-cache search rpcinfo ; searches for packages with "rpcinfo" in name of description
  • apt-get install libreadline5-dev : installs package
  • dpkg -S rpcinfo : searches for a file rpcinfo and prints the corresponding packages

Settings done while booting:
lxhadesdaq:~# cat /etc/sysctl.conf
#
# /etc/sysctl.conf - Configuration file for setting system variables
# See sysctl.conf (5) for information.
#
#kernel.domainname = example.com
#net/ipv4/icmp_echo_ignore_broadcasts=1
#net.core.rmem_max = 2097152
net.core.rmem_max=1048576
kernel.shmmax=268435456
kernel.shmall=20971520

Linux networking kernel parameters (/proc/sys/net/core):
  • rmem_default default receive socket buffer size
  • rmem_max maximum receive socket buffer size
  • wmem_default default send socket buffer size
  • wmem_max maximum send socket buffer size
  • netdev_max_backlog number of unprocessed input packets before kernel starts dropping them (default = 300)

How to set parameter value in /etc/sysctl.conf :
  • sysctl -w net.core.rmem_default=262144

Backup-system for lxhadesdaq

IT department can not guarantee that they can get lxhadesdaq up running a few hours after a hardware failure. Therefore, a backup-system should be prepared to replace lxhadesdaq in case of hardware failure.

backup-system (hadeb06) will get nightly all daq related files from lxhadesdaq via rsync.

Directories to be rsynced on lxhadesdaq:

  • /home/hadaq
  • /home/scs
  • /var/diskless/linuxvme
  • /var/diskless/etrax
  • /etc/hosts
  • /etc/dhcp3/dhcpd.conf
  • /tftpboot

to be continued

-- SergeyYurevich - 03 Apr 2007

hadeb04

hadeb04 is a 1.7TB fileserver with a 3200+ AMD 64 CPU. It is running a 64bit linux. It has not system-disk. The bootserver is lxhadesdaq. Some things about the Asus-Board:
  • The BIOS upgrade to version 1013 is not working.
  • BIOS upgrades only work via "ALT-F2" during booting and providing the file on a Floppy-Disk. All other methods failed with a Checksum-Error!
  • One has to boot over the second Giga-Bit interface. The first (NVIDIA) is for some reason not recoginized by the kernel

UNAME_MACHINE="x86_64" make modules_install

Compile the kernel 2.6.12.5 for x86_64:
  1. one has to change directory to: lxhadesdaq:/var/diskless/hadeb04/usr/src/linux-2.6.12.5
  2. one has to use cross-compiler. It is in lxhadesdaq:/var/diskless/hadeb04/usr/src/linux-2.6.12.5/x86_64-unknown-linux-gnu directory,
  3. type: export PATH=$PATH:/var/diskless/hadeb04/usr/src/linux-2.6.12.5/x86_64-unknown-linux-gnu/gcc-3.4.0-glibc-2.3.2/bin,
  4. make ARCH=x86_64 menuconfig
  5. make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu-
  6. INSTALL_MOD_PATH=/var/diskless/hadeb04 make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu- modules_install
  7. cp arch/x86_64/boot/bzImage /tftpboot/vmlinuz_2.6.12.5_64bit

Data Sources

Data is transported via Ethernet and UDP to the eventbuilder. The sequence of sources is the following:

Subsystem UDP-port
TOF and MU 2222
Shower 2223
RICH0 2224
RICH1 2225
RICH2 2226
MDC0 2227
MDC1 2228

Meaning of EvtId in Eventbuilder-Output on text-console

            evtId09: 4086             evtId11:   11k            evtId19:  894 
            evtId21: 3967             evtId31: 2247 

The number is devided into two nibbles:

Lower nibble: Trigger Code as delivered by CTU Higher nibble: Decision made by MU

Bits
0 downscaled event, 0=> not downscaled
1-2 0: negative, 1: positive, 2: positive but stopped due too many leptons

-- MichaelTraxler - 28 Jan 2005
>
>
EventBuilderTest
 
Revision 22
28 Nov 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 42 to 42
 
  • Backup disk: /data/backup

The following machines/directories are backuped:
Changed:
<
<
>
>
 

the backup of hades17: hades25/home/hadaq/backups/hades17_hadaq_home/
Revision 21
27 Nov 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 48 to 48
 
Added:
>
>
 

the backup of hades17: hades25/home/hadaq/backups/hades17_hadaq_home/
Changed:
<
<
-- SergeyYurevich - 11 Sep 2007
>
>
-- SergeyYurevich - 27 Nov 2007
 

lxhadesdaq

Revision 20
14 Nov 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 98 to 98
  kernel.shmall=20971520
Added:
>
>
Linux networking kernel parameters (/proc/sys/net/core):
  • rmem_default default receive socket buffer size
  • rmem_max maximum receive socket buffer size
  • wmem_default default send socket buffer size
  • wmem_max maximum send socket buffer size
  • netdev_max_backlog number of unprocessed input packets before kernel starts dropping them (default = 300)

How to set parameter value in /etc/sysctl.conf :
  • sysctl -w net.core.rmem_default=262144
 

Backup-system for lxhadesdaq

IT department can not guarantee that they can get lxhadesdaq up running a few hours after a hardware failure. Therefore, a backup-system should be prepared to replace lxhadesdaq in case of
Revision 19
11 Sep 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 10 to 10
  The following machines are dedicated DAQ-eventbuilders:

  • hadeb02
Changed:
<
<
  • hadeb03 (remote backup system)
>
>
  • hadeb03
  • hadeb07 (remote backup system)
 
  • lxhadesdaq

hadeb02, hadeb03

Line: 24 to 25
  hadeb02: redhat something
hadeb03: SuSE 9.2 with quite new security patches
Changed:
<
<

hadeb03 (remote backup system)

>
>

hadeb07 (remote backup system)

 
Changed:
<
<
hadeb03 serves as a remote backup system.
>
>
hadeb07 parameters:
  • SuSE 10.2
  • Hard disks: sda+sdb = 0.32TB, sdc+sdd = 1TB. The two last disks (sdc, sdd) were additionally put into the machine to serve as backup disks. They are not really fixed inside the machine: take care when moving the machine. Nagios monitors the temperature of both disks.
  • Two 3GHz processors
  • 2GB memory

After a power outage hadeb03 experienced a hardware failure. We have decided to use hadeb07 instead of hadeb03 for the remote backup.

hadeb07 serves as a remote backup system.
 
  • Software: rsnapshot, executed 6 times a day (crontab -e)
  • Config file: /etc/rsnapshot.conf
Changed:
<
<
  • Backup disk: /d/hadeb03/backups
>
>
  • Backup disk: /data/backup
 

The following machines/directories are backuped:
Line: 41 to 51
 

the backup of hades17: hades25/home/hadaq/backups/hades17_hadaq_home/
Changed:
<
<
-- SergeyYurevich - 16 Aug 2007
>
>
-- SergeyYurevich - 11 Sep 2007
 

lxhadesdaq

Line: 71 to 81
  Important Debian-commands:
  • apt-cache search rpcinfo ; searches for packages with "rpcinfo" in name of description
  • apt-get install libreadline5-dev : installs package
Changed:
<
<
  • dpkg -S rpcinfo : searches fo a file rpcinfo and prints the corresponding packages
>
>
  • dpkg -S rpcinfo : searches for a file rpcinfo and prints the corresponding packages
 

Settings done while booting:
Revision 18
31 Aug 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 82 to 82
  # #kernel.domainname = example.com #net/ipv4/icmp_echo_ignore_broadcasts=1
Changed:
<
<
net.core.rmem_max = 2097152
>
>
#net.core.rmem_max = 2097152 net.core.rmem_max=1048576 kernel.shmmax=268435456 kernel.shmall=20971520
 

Backup-system for lxhadesdaq

Revision 17
21 Aug 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 39 to 39
 
Added:
>
>
the backup of hades17: hades25/home/hadaq/backups/hades17_hadaq_home/
  -- SergeyYurevich - 16 Aug 2007

lxhadesdaq

Revision 16
16 Aug 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 10 to 10
  The following machines are dedicated DAQ-eventbuilders:

  • hadeb02
Changed:
<
<
  • hadeb03
>
>
  • hadeb03 (remote backup system)
 
  • lxhadesdaq

hadeb02, hadeb03

Line: 24 to 24
  hadeb02: redhat something
hadeb03: SuSE 9.2 with quite new security patches
Added:
>
>

hadeb03 (remote backup system)

hadeb03 serves as a remote backup system.
  • Software: rsnapshot, executed 6 times a day (crontab -e)
  • Config file: /etc/rsnapshot.conf
  • Backup disk: /d/hadeb03/backups

The following machines/directories are backuped:

-- SergeyYurevich - 16 Aug 2007
 

lxhadesdaq

Revision 15
03 Apr 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 81 to 81
 
  • /var/diskless/etrax
  • /etc/hosts
  • /etc/dhcp3/dhcpd.conf
Changed:
<
<
  • /etc/tftpboot (?)
>
>
  • /tftpboot
 

to be continued
Changed:
<
<
-- SergeyYurevich - 21 Feb 2007
>
>
-- SergeyYurevich - 03 Apr 2007
 

hadeb04

Revision 14
22 Mar 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 75 to 75
 

Directories to be rsynced on lxhadesdaq:
Changed:
<
<
  • /home/hadaq/
  • /var/diskless
>
>
  • /home/hadaq
  • /home/scs
  • /var/diskless/linuxvme
  • /var/diskless/etrax
 
  • /etc/hosts
  • /etc/dhcp3/dhcpd.conf
  • /etc/tftpboot (?)
Revision 13
21 Feb 2007 - Main.SergeyYurevich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 66 to 66
  net.core.rmem_max = 2097152
Added:
>
>

Backup-system for lxhadesdaq

IT department can not guarantee that they can get lxhadesdaq up running a few hours after a hardware failure. Therefore, a backup-system should be prepared to replace lxhadesdaq in case of hardware failure.

backup-system (hadeb06) will get nightly all daq related files from lxhadesdaq via rsync.

Directories to be rsynced on lxhadesdaq:

  • /home/hadaq/
  • /var/diskless
  • /etc/hosts
  • /etc/dhcp3/dhcpd.conf
  • /etc/tftpboot (?)

to be continued

-- SergeyYurevich - 21 Feb 2007
 

hadeb04

hadeb04 is a 1.7TB fileserver with a 3200+ AMD 64 CPU. It is running a 64bit linux. It has not system-disk.
Revision 12
27 Apr 2006 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 33 to 33
 
  • 3 redundant power supplies (we just connected them to different fuses not different phases!)
  • spare parts in the computer center
Changed:
<
<
System: Debian "Sarge" (which is not available yet smile )
>
>
System: Debian "Sarge" (which is not available yet(2005) smile )

How to check if the SATA-RAID is still OK:

https://lxhadesdaq:1082/

Username: user

Password: waVe**** (ask Michael)

Software

 

For installing packages, have a look to: http://wiki.gsi.de/cgi-bin/view/Linux/DebianPaketVerwaltung
Revision 11
05 Dec 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 43 to 43
 
  • apt-get install libreadline5-dev : installs package
  • dpkg -S rpcinfo : searches fo a file rpcinfo and prints the corresponding packages
Added:
>
>
Settings done while booting:
lxhadesdaq:~# cat /etc/sysctl.conf
#
# /etc/sysctl.conf - Configuration file for setting system variables
# See sysctl.conf (5) for information.
#
#kernel.domainname = example.com
#net/ipv4/icmp_echo_ignore_broadcasts=1
net.core.rmem_max = 2097152
 

hadeb04

hadeb04 is a 1.7TB fileserver with a 3200+ AMD 64 CPU. It is running a 64bit linux. It has not system-disk.
Revision 10
14 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 16 to 16
 

hadeb02, hadeb03

These are identical machines with 2 1GHz processors. They have 1 GByte memory.
Changed:
<
<
Currently (28.01.05), only lxhadesdaq and hadeb2 are connected to the switch via a Gbit/s link. (A GBit switch is ordered, so that we can have all of them share the GBit/s link).
>
>
Currently (14.09.05), all hades-daq-computer are connected to the Gbit/s Netgear switch.
 

habeb03 is now (28.01.05) stable again. It did not crash for many weeks. The nfsserver is now running again, so it can be used for writing hades-data from the event-builder which is currently used as the main eventbuilder.
Changed:
<
<
hadeb02: redhat something
>
>
hadeb02: redhat something
  hadeb03: SuSE 9.2 with quite new security patches

lxhadesdaq

Revision 9
14 Sep 2005 - Main.HadesDaq
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 78 to 78
 

Meaning of EvtId in Eventbuilder-Output on text-console

Added:
>
>
 
evtId09
4086 evtId11: 11k evtId19: 894
evtId21
3967 evtId31: 2247
Added:
>
>
 

The number is devided into two nibbles:
Revision 8
12 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Table of contents:
Line: 76 to 76
 
MDC0 2227
MDC1 2228

Added:
>
>

Meaning of EvtId in Eventbuilder-Output on text-console

evtId09
4086 evtId11: 11k evtId19: 894
evtId21
3967 evtId31: 2247

The number is devided into two nibbles:

Lower nibble: Trigger Code as delivered by CTU Higher nibble: Decision made by MU

Bits
0 downscaled event, 0=> not downscaled
1-2 0: negative, 1: positive, 2: positive but stopped due too many leptons

  -- MichaelTraxler - 28 Jan 2005
Revision 7
24 Aug 2005 - Main.MichaelTraxler
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="HadesDaqDocumentation"
  Table of contents:
Line: 48 to 49
  hadeb04 is a 1.7TB fileserver with a 3200+ AMD 64 CPU. It is running a 64bit linux. It has not system-disk. The bootserver is lxhadesdaq. Some things about the Asus-Board:
Changed:
<
<
  • The BIOS upgrade to version 1014 is not working.
>
>
  • The BIOS upgrade to version 1013 is not working.
 
  • BIOS upgrades only work via "ALT-F2" during booting and providing the file on a Floppy-Disk. All other methods failed with a Checksum-Error!
  • One has to boot over the second Giga-Bit interface. The first (NVIDIA) is for some reason not recoginized by the kernel
Revision 6
24 Aug 2005 - Main.MichaelTraxler
Line: 1 to 1
  Table of contents:
Line: 43 to 43
 
  • apt-get install libreadline5-dev : installs package
  • dpkg -S rpcinfo : searches fo a file rpcinfo and prints the corresponding packages
Added:
>
>

hadeb04

hadeb04 is a 1.7TB fileserver with a 3200+ AMD 64 CPU. It is running a 64bit linux. It has not system-disk. The bootserver is lxhadesdaq. Some things about the Asus-Board:
  • The BIOS upgrade to version 1014 is not working.
  • BIOS upgrades only work via "ALT-F2" during booting and providing the file on a Floppy-Disk. All other methods failed with a Checksum-Error!
  • One has to boot over the second Giga-Bit interface. The first (NVIDIA) is for some reason not recoginized by the kernel

UNAME_MACHINE="x86_64" make modules_install
  Compile the kernel 2.6.12.5 for x86_64:
  1. one has to change directory to: lxhadesdaq:/var/diskless/hadeb04/usr/src/linux-2.6.12.5
  2. one has to use cross-compiler. It is in lxhadesdaq:/var/diskless/hadeb04/usr/src/linux-2.6.12.5/x86_64-unknown-linux-gnu directory,
  3. type: export PATH=$PATH:/var/diskless/hadeb04/usr/src/linux-2.6.12.5/x86_64-unknown-linux-gnu/gcc-3.4.0-glibc-2.3.2/bin,
Changed:
<
<
  1. make ARCH=x86_6 menuconfig
>
>
  1. make ARCH=x86_64 menuconfig
 
  1. make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu-
Changed:
<
<
  1. INSTALL_MOD_PATH=/tmp/ make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu- modules_install
  2. cp /tmp/lib/modules/2.6.12.5 ../../../lib/modules/
>
>
  1. INSTALL_MOD_PATH=/var/diskless/hadeb04 make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu- modules_install
 
  1. cp arch/x86_64/boot/bzImage /tftpboot/vmlinuz_2.6.12.5_64bit

Data Sources

Data is transported via Ethernet and UDP to the eventbuilder. The sequence of sources is the following:
Changed:
<
<
  1. TOF and MU
  2. Shower
  3. RICH0
  4. RICH1
  5. RICH2
  6. MDC0
  7. MDC1
>
>
Subsystem UDP-port
TOF and MU 2222
Shower 2223
RICH0 2224
RICH1 2225
RICH2 2226
MDC0 2227
MDC1 2228
 

-- MichaelTraxler - 28 Jan 2005
Revision 5
23 Aug 2005 - Main.MarekPalka
Line: 1 to 1
  Table of contents:
Line: 43 to 43
 
  • apt-get install libreadline5-dev : installs package
  • dpkg -S rpcinfo : searches fo a file rpcinfo and prints the corresponding packages
Added:
>
>
Compile the kernel 2.6.12.5 for x86_64:
  1. one has to change directory to: lxhadesdaq:/var/diskless/hadeb04/usr/src/linux-2.6.12.5
  2. one has to use cross-compiler. It is in lxhadesdaq:/var/diskless/hadeb04/usr/src/linux-2.6.12.5/x86_64-unknown-linux-gnu directory,
  3. type: export PATH=$PATH:/var/diskless/hadeb04/usr/src/linux-2.6.12.5/x86_64-unknown-linux-gnu/gcc-3.4.0-glibc-2.3.2/bin,
  4. make ARCH=x86_6 menuconfig
  5. make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu-
  6. INSTALL_MOD_PATH=/tmp/ make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu- modules_install
  7. cp /tmp/lib/modules/2.6.12.5 ../../../lib/modules/
  8. cp arch/x86_64/boot/bzImage /tftpboot/vmlinuz_2.6.12.5_64bit
 

Data Sources

Data is transported via Ethernet and UDP to the eventbuilder. The sequence of sources is the following:
Revision 4
14 Jul 2005 - Main.MichaelTraxler
Line: 1 to 1
  Table of contents:
Line: 22 to 22
  The nfsserver is now running again, so it can be used for writing hades-data from the event-builder which is currently used as the main eventbuilder.

hadeb02: redhat something
Changed:
<
<
hadeb03: SuSE 9.2 with newest security patches
>
>
hadeb03: SuSE 9.2 with quite new security patches
 

lxhadesdaq

Line: 35 to 35
 

System: Debian "Sarge" (which is not available yet smile )
Added:
>
>
For installing packages, have a look to: http://wiki.gsi.de/cgi-bin/view/Linux/DebianPaketVerwaltung

Important Debian-commands:
  • apt-cache search rpcinfo ; searches for packages with "rpcinfo" in name of description
  • apt-get install libreadline5-dev : installs package
  • dpkg -S rpcinfo : searches fo a file rpcinfo and prints the corresponding packages
 

Data Sources

Revision 3
31 Jan 2005 - Main.HadesDaq
Line: 1 to 1
  Table of contents:
Line: 36 to 36
  System: Debian "Sarge" (which is not available yet smile )
Added:
>
>

Data Sources

Data is transported via Ethernet and UDP to the eventbuilder. The sequence of sources is the following:

  1. TOF and MU
  2. Shower
  3. RICH0
  4. RICH1
  5. RICH2
  6. MDC0
  7. MDC1
 

-- MichaelTraxler - 28 Jan 2005
Revision 2
28 Jan 2005 - Main.MichaelTraxler
Line: 1 to 1
  Table of contents:
Line: 6 to 6
 
Changed:
<
<
The following machine are dedicated DAQ-eventbuilders
>
>
The following machines are dedicated DAQ-eventbuilders:
 

  • hadeb02
  • hadeb03
Line: 33 to 33
 
  • 3 redundant power supplies (we just connected them to different fuses not different phases!)
  • spare parts in the computer center
Changed:
<
<
System: Debian "Sarge"
>
>
System: Debian "Sarge" (which is not available yet smile )
 

 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)