Upon receiving a SIGUSR1, the bebopd reports the following information. The information will be logged to /var/log/cplant normally. The destination can be changed with the -S and -L options.
bebopd: node 22, system pid 396, portal pid 1 bebopd portals: yod requests 10, pingd requests 12, pct updates 11 PBSsupport: 1, PBSupdate: 1, PBSinteractive: 100 node count: free 226 scheduled 700 interactive 92 active 918 location: answer_ping_requests (top)
The first line lists the physical node ID, Linux system process ID, and portal process ID of the bebopd. The second line lists the numbers of the portals at which the bebopd checks for yod messages, pingd messages and PCT messages. Every incoming portals message must specify a portal process ID and a portal number in order for the portals module to identify the destination of the message.
The next line lists whether the bebopd is in PBSsupport mode and PBSupdate mode (1 means yes, 0 means no), and how many nodes are set aside for non-PBS jobs. These parameters can be changed while the bebopd is running by using pingd (see chapter 6).
The fourth line provides a count the number of free compute nodes, the number of nodes running PBS jobs, and the number of nodes running non-PBS (interactive) jobs. It appears that in this case, 100 nodes are reserved for non-PBS use (92 of them are in use) and 918 are allocated for PBS use (with 700 of these in use), leaving a total of 226 free nodes.
The fifth line lists the routine that the bebopd was in when it received the SIGUSR1. This information can be useful in debugging the bebopd. If the location doesn't change in subsequent displays, it may indicate that the bebopd is stuck somewhere.