openvpn3-service-sessionmgr(8)

πŸ’– openvpn3-service-sessionmgr β€” the OpenVPN 3 Linux Session Manager Service πŸ’–

okay bestie, this is the openvpn3-service-sessionmgr(8) page from the OpenVPN 3 Linux manual, and it's literally the backstage crew keeping your VPN sessions alive. let's get into it πŸŽ€


✨ NAME ✨

openvpn3-service-sessionmgr β€” the OpenVPN 3 Linux Session Manager Service πŸ’…


🌸 SYNOPSIS 🌸

openvpn3-service-sessionmgr [OPTIONS]
openvpn3-service-sessionmgr -h | --help

πŸ¦‹ DESCRIPTION πŸ¦‹

so openvpn3-service-sessionmgr is a backend service for OpenVPN 3 Linux, and its whole job β€” its main character era, fr β€” is managing running OpenVPN sessions. once a VPN session has been started, whether that's via openvpn3 session-start or openvpn2, it runs in the background as a D-Bus service for as long as it has at least one active VPN session running. no cap. ✨

only ONE session manager process can run on the system. like, one. that's it. πŸ’€

your VPN sessions get managed through the openvpn3 session-manage and openvpn3 session-acl commands, and brand-new VPN sessions get started with the openvpn3 session-start command. that's the trio 🫢

this service is normally started automatically when it's needed, via the net.openvpn.v3.sessionmgr.service auto-start configuration handled by dbus-daemon(1), but you can also start it manually on the command line if that's your vibe. this process should run as the _openvpn user, and it will automatically switch to that user account if it has the privileges needed to do so. iconic behaviour honestly πŸ‘‘

⚠️ beware though: changing this to another user account also requires updating the D-Bus policy as well. so don't just go rogue, bestie 😭

πŸ’œ OPTIONS πŸ’œ

  • -h, --help β€” print usage and help details to the terminal, so you know what's up πŸ™ˆ
  • --version β€” prints the version of the program and exists πŸ’«
  • --log-level LEVEL β€” sets the default log verbosity for log events generated by this service. the default is 3. valid values are 0 to 6. higher log levels result in more verbose logs, and log level 6 will contain all debug log events. so if you're nosy, that's your girl πŸ”₯
  • --log-file LOG_DESTINATION β€” by default, logging goes via the openvpn3-service-log service. by providing this argument, logging will also be sent to LOG_DESTINATION, which can be either a filename or stdout: β€” where that last one sends log data to the console. multitasking queen 🌈
  • --colour β€” this adds colours to log events when logging to file or terminal. log events get coloured based on the log level of the event. cute AND functional, we love to see it πŸŽ€
  • --idle-exit MINUTES β€” the openvpn3-service-sessionmgr service will exit automatically if it's been idle for MINUTES minutes. and by "idle" it means no VPN sessions are running and managed by this service. you can validate this by running openvpn3 sessions-list. if that gives you an empty list, no configuration profiles are being managed. bye bestie, see you never (until you're needed again) πŸ‘‹

🌟 SEE ALSO 🌟


and that's the whole thing, bestie πŸ’– this was openvpn3-service-sessionmgr(8) from the OpenVPN 3 Linux manual β€” go forth and manage those sessions, you absolute legend πŸ‘‘βœ¨

πŸ“¦ where this page comes from