ATMSIGD(8) | Maintenance Commands | ATMSIGD(8) |
atmsigd - ATM signaling demon
atmsigd [-b] [-c config_file]
[-d] [-D dump_dir]
[-l logfile] [-m mode] [-n]
[-q qos] [-t trace_length]
[-u uni_version]
[[itf.]vpi.vci
[input output]]
atmsigd -V
atmsigd implements the ATM UNI signaling protocol. Requests to establish, accept, or close ATM SVCs are sent from the kernel (using a comparably simple protocol) to the signaling demon, which then performs the dialog with the network.
Note that atmsigd is not able to accept or establish connections until the local ATM address of the interface is configured by ilmid or manually using atmaddr.
The default signaling VC (interface 0, VPI 0, VCI 5) can be overridden on the command line by specifying a different PVC address.
When overriding the default VC, optionally a pair of named pipes to use for communicating with the user of signaling can be specified. Normally, the kernel is the user of signaling and atmsigd opens a special socket for communication with it.
If atmsigd is killed, all system calls requiring interaction with it will return with an error and set errno to EUNATCH.
When receiving a SIGUSR1 signal, atmsigd dumps the list of all internal socket descriptors. With SIGUSR2, it dumps the contents of the trace buffer. If a dump directory was set, dumps are written to files called atmsigd.pid.status.number and atmsigd.pid.trace.number, respectively, with number starting at zero and being incremented for every dump. If no dump directory is set, dumps are written to standard error.
Dumps are also generated whenever atmsigd detects a fatal error and terminates. No attempt is made to catch signals like SIGSEGV.
The generation of traces is a comparably slow process which may already take several seconds for only 100 trace entries. To generate a trace dump, atmsigd therefore forks a child process that runs in parallel to the signaling demon.
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>
atmaddr(8), atmsigd.conf(4), ilmid(8), qos(7)
April 26, 2000 | Linux |