CONMAND(8)

πŸ“¦
version 0.3.1 Β· 4 versions
, in debian trixie, epel 10, epel 9, fedora 43, fedora 44, opensuse-leap 16.0, ubuntu noble, ubuntu resolute, ubuntu stonking

πŸ’– CONMAND(8) β€” like, the ConMan daemon bestie πŸ’–

okay so welcome to the manual page for conmand, aka the beating heart of ConMan: The Console Manager. sit down, grab a strawberry drink πŸ“, and let's get into it.


✨ NAME ✨

conmand β€” the ConMan daemon, no cap πŸ‘‘


✨ SYNOPSIS ✨

conmand [OPTION]...

✨ DESCRIPTION ✨

conmand is the daemon, the main character of this whole operation πŸ’…. It's the one managing all the consoles that get defined by its configuration file, and it's also the one sitting there listening for connections from clients. Basically it does everything. Iconic behaviour, honestly.


✨ OPTIONS ✨

  • -c file β€” tell it which configuration file to use, overriding the default spot, which is [/etc/conman.conf]. rude to assume, but okay.
  • -F β€” run the daemon in the foreground. it's giving "i'm right here, i'm not hiding" 🫢
  • -h β€” show a lil summary of the command-line options. your cheat sheet, bestie.
  • -k β€” send a SIGTERM to the conmand process that's associated with the specified configuration, which kills the daemon πŸ’€. Returns 0 if the daemon got successfully signaled; otherwise it returns 1.
  • -L β€” display license information. the legal tea β˜•
  • -p port β€” pick the port where conmand listens for clients, overriding both the default port [7890] and whatever port the configuration file said. this option said "i don't care what the config thinks" ✨
  • -P file β€” set the PID file that stores the daemon's PID, overriding the "server pidfile" directive in the configuration file.
  • -q β€” shows you the PID of the conmand process associated with the specified configuration, but only if it looks active. Returns 0 if the configuration appears active; otherwise it returns 1. lowkey a vibe check for your daemon 🌸
  • -r β€” send a SIGHUP to the conmand process associated with the specified configuration, which re-opens both that daemon's log file and the individual console log files. Returns 0 if the daemon was successfully signaled; otherwise it returns 1.
  • -v β€” enable verbose mode. it's gonna talk. a lot. πŸ—£οΈ
  • -V β€” display version information.
  • -z β€” truncate both the daemon's log file and the individual console log files at start-up. fresh start energy πŸ¦‹

✨ SIGNALS ✨

  • SIGHUP β€” close and re-open both the daemon's log file and the individual console log files. Conversion specifiers inside filenames will be re-evaluated. this is the moment for logrotate configurations, iykyk πŸ”₯
  • SIGTERM β€” terminate the daemon. bye bestie πŸ‘‹

✨ SECURITY ✨

okay this part matters, listen up fr fr. Connections to the server are not authenticated, and communications between client and server are not encrypted. that's just how it is right now 😭. Until this gets addressed in a future release, the recommendation is to bind the server's listen socket to the loopback address β€” you do that by specifying "server loopback=on" in conman.conf β€” and to restrict access to the server host. protect your peace AND your server πŸ’œ

✨ NOTES ✨

Log messages get sent to standard-error until after the configuration file has been read. At that point, future messages are discarded unless either the logfile or syslog keyword has been specified (see conman.conf(5)). no key, no messages, that's the rule πŸ™ˆ

If the configuration file gets modified while the daemon is running and a pidfile wasn't originally specified, the '-k' and '-r' options may not be able to identify the daemon process. consequently, the appropriate signal may need to be sent to the daemon manually. awkward, but manageable πŸ’…

The number of consoles that can be simultaneously managed is limited by the maximum number of file descriptors a process can have open. The daemon sets its "nofile" soft limit to the maximum/hard limit. So if you're encountering "too many open files" errors, you may need to increase the "nofile" hard limit. yes it's a limit thing, yes it's always a limit thing 🌈


✨ AUTHOR ✨

Chris Dunlap <cdunlap@llnl.gov> 🫢


Copyright (C) 2007-2022 Lawrence Livermore National Security, LLC. Copyright (C) 2001-2007 The Regents of the University of California.


✨ LICENSE ✨

ConMan is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. slay, legally speaking ⭐


✨ SEE ALSO ✨

conman(1), conman.conf(5).

https://dun.github.io/conman/


and that's the whole page bestie, thanks for reading to the end, you're literally the main character πŸŽ€

this little masterpiece is from conman-0.3.1, dated 2022-10-17, and it lives in section CONMAND(8). mwah πŸ’…βœ¨