choose: sw hd | installObjy | setup: ams ls pud chs oids | confCH | maintain: ams ls pud chs oids | moveFD | creaBri

Search | Site Map .

Maintaining pud daemon

Use BdbAdminDaemon to maintain pud.

Starting a daemon: BdbAdminDaemon -start [-p portNr] [-v]

Terminating daemon: BdbAdminDaemon -terminate [-p portNr] [-v]

Checking if daemon is running: BdbAdminDaemon [-p portNr] [-v]

where:

portNr : if the flag –p portNr is omitted, the default port number: 3333 is used. We strongly recommend to use that number.

-v turns on verbose mode. By default it is disabled.

Alternatively, you may use bdbcheckpud to check if a daemon is running. See bdbcheckpud -help for further details.

The current version of BdbAdminDaemon is supported on SunOS, Linux and Dec Alpha.

Log files

Once daemon is started, various type of messages are routed to the log file.

Location of the file: /tmp/. You can change the location of the place of the log file. See man pages or pud_*.conf files for further details.

File name: pud_<day>.log, where <day> is the three letter day of the week (e.g. pud_tue.log).

Note: log files are recycled every seven days.

Format of the log file:

<date> <type of info> message <pid of the daemon> <user name>@<host name> <request> <parameters> < return status>

If no authentication is enabled, the <user name> field will be left empty.

Example:

15:05:15 Error: File /nfs/objyserv1/testA does not exist. PudID=41540, becla@percheron.slac.stanford.edu, req=checkExist, parms= /nfs/objyserv1/testA, rc=-1

 


BaBar Public Site | SLAC | News | Links | Who's Who | Contact Us

Page Owner: Jacek Becla
Last Update: June 13, 2002