KSMBD.MOUNTD(8)

πŸ’– KSMBD.MOUNTD β€” bestie, let's start some daemons πŸ’–

okay so this is the man page for ksmbd.mountd from the section 8 (system administration, aka the "you probably need root for this" zone) of the manual. grab a snack, we're doing sysadmin. πŸ“


✨ NAME ✨

ksmbd.mountd β€” start ksmbd.mountd and ksmbd daemons


🌸 SYNOPSIS 🌸

ksmbd.mountd [-v] [-p PORT] [-n[WAY]] [-C CONF] [-P PWDDB]

πŸ¦‹ DESCRIPTION πŸ¦‹

ksmbd.mountd starts the ksmbd.mountd user mode daemon and the ksmbd kernel mode daemon. two for the price of one, we love a duo. πŸ‘‘

like, it literally has to parse the ksmbd.conf(5) configuration file in order to start. no config, no start, no service, no nothing. it's giving "no thoughts, just parse". 😭

and it can parse the ksmbdpwd.db(5) user database so it can support non-guest sessions β€” meaning actual users with actual credentials can get in, not just the guest vibe. 🫢


πŸ’… OPTIONS πŸ’…

  • -p, --port=PORT β€” bind to PORT instead of TCP port 445. yes bestie, 445 is the default because that's the SMB port, iykyk.
  • -n, --nodetach[=WAY] β€” do not detach the process from the foreground. if WAY is 1, it becomes the process group leader (and that's the default). if WAY is 0, it detaches. so basically -n is the "hey, stay here with me" flag. πŸ™ˆ
  • -C, --config=CONF β€” use CONF as the configuration file instead of /etc/ksmbd/ksmbd.conf. main character energy: your file, your rules.
  • -P, --pwddb=PWDDB β€” use PWDDB as the user database instead of /etc/ksmbd/ksmbdpwd.db. same deal, different file.
  • -v, --verbose β€” be verbose. talk to me bestie, tell me everything. πŸ—£οΈ
  • -V, --version β€” output version information and exit. short and sweet.
  • -h, --help β€” display this help and exit. the classic.

😭 EXIT STATUS 😭

the exit status is 0 on success and 1 on failure. no cap.

and when it's detaching the process from the foreground, the exit status is 0 if daemonization succeeded. so like, 0 = slay, 1 = it's not giving.


πŸ”₯ SIGNALS πŸ”₯

ksmbd.mountd can be notified of changes to ksmbd.conf or ksmbdpwd.db by sending it the SIGHUP signal. so you edited your config? SIGHUP it and move on, don't be dramatic. πŸ’…

the manager process of ksmbd.mountd has its PID stored in /run/ksmbd.lock. that's your receipt. keep it. 🧾


Copyright Β© 2015-2022 ksmbd-tools contributors. License GPLv2: GNU GPL version 2 <https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html>.

this is free software: you are free to change and redistribute it. there is NO WARRANTY, to the extent permitted by law. (emphasis on the NO WARRANTY, bestie, they mean it. 😌)


πŸ› REPORTING BUGS πŸ›

found a bug? for bug reports, use the issue tracker at <https://github.com/cifsd-team/ksmbd-tools/issues>. don't suffer in silence, that's not the vibe. 🫢


🌈 SEE ALSO 🌈

Configuration File

User Database

Utilities


and that's the whole page, you ate it. πŸ’– this was ksmbd-tools 3.5.7, brought to you by the ksmbd-tools girlies. go forth and mount, and remember: read the config file first. periodt. πŸ‘‘βœ¨

πŸ“¦ where this page comes from