1
2CONMAND(8) ConMan: The Console Manager CONMAND(8)
3
4
5
7 conmand - ConMan daemon
8
9
11 conmand [OPTION]...
12
13
15 conmand is the daemon responsible for managing consoles defined by its
16 configuration file as well as listening for connections from clients.
17
18
20 -c file
21 Specify a configuration file, overriding the default location
22 [/etc/conman.conf].
23
24 -F Run the daemon in the foreground.
25
26 -h Display a summary of the command-line options.
27
28 -k Send a SIGTERM to the conmand process associated with the speci‐
29 fied configuration, thereby killing the daemon. Returns 0 if
30 the daemon was successfully signaled; otherwise, returns 1.
31
32 -L Display license information.
33
34 -p port
35 Specify the port on which conmand will listen for clients, over‐
36 riding both the default port [7890] and the port specified in
37 the configuration file.
38
39 -q Displays the PID of the conmand process associated with the
40 specified configuration if it appears active. Returns 0 if the
41 configuration appears active; otherwise, returns 1.
42
43 -r Send a SIGHUP to the conmand process associated with the speci‐
44 fied configuration, thereby re-opening both that daemon's log
45 file and individual console log files. Returns 0 if the daemon
46 was successfully signaled; otherwise, returns 1.
47
48 -v Enable verbose mode.
49
50 -V Display version information.
51
52 -z Truncate both the daemon's log file and individual console log
53 files at start-up.
54
55
57 SIGHUP Close and re-open both the daemon's log file and the indi‐
58 vidual console log files. Conversion specifiers within
59 filenames will be re-evaluated. This is useful for logro‐
60 tate configurations.
61
62 SIGTERM Terminate the daemon.
63
64
66 Connections to the server are not authenticated, and communications
67 between client and server are not encrypted. When time allows, this
68 will be addressed in a future release. Until then, the recommendation
69 is to bind the server's listen socket to the loopback address (by spec‐
70 ifying "server loopback=on" in conman.conf) and restrict access to the
71 server host.
72
73
75 Log messages are sent to standard-error until after the configuration
76 file has been read, at which time future messages are discarded unless
77 either the logfile or syslog keyword has been specified (cf., con‐
78 man.conf(5)).
79
80 If the configuration file is modified while the daemon is running and a
81 pidfile was not originally specified, the '-k' and '-r' options may be
82 unable to identify the daemon process; consequently, the appropriate
83 signal may need to be sent to the daemon manually.
84
85 The number of consoles that can be simultaneously managed is limited by
86 the maximum number of file descriptors a process can have open. The
87 daemon sets its "nofile" soft limit to the maximum/hard limit. If you
88 are encountering "too many open files" errors, you may need to increase
89 the "nofile" hard limit.
90
91
93 Chris Dunlap <cdunlap@llnl.gov>
94
95
97 Copyright (C) 2007-2009 Lawrence Livermore National Security, LLC.
98 Copyright (C) 2001-2007 The Regents of the University of California.
99
100 ConMan is free software; you can redistribute it and/or modify it under
101 the terms of the GNU General Public License as published by the Free
102 Software Foundation; either version 2 of the License, or (at your
103 option) any later version.
104
105
107 conman(1), conman.conf(5).
108
109 http://home.gna.org/conman/
110
111
112
113conman-0.2.5 2009-05-19 CONMAND(8)