One common challenge system administrators face is the contradictory requirement of multiple people managing machines using logins that shouldn't be shared.
doas(1) solves this problem by permitting a certain subset of your users to run predetermined commands as another user.
An up-to-date version of sudo(8) is available as a package.
Open BSD offers several tools for managing users and groups on your system: file.
vipw(8) also takes care of locking these files, so that only one user can make changes at a time.
Its man page contains a good overview and explains the various scripts and files involved.
If you wish to enable or disable daemons, use rcctl(8) to manage your local(8) file, as described below.
Most daemons and services that come with Open BSD are controlled on boot by variables defined in /etc/You'll see lines similar to this: This shows that httpd(8) is not to be started from rc(8) at boot time. Open BSD's system daemons ("services") are started, stopped and controlled by rc.d(8).Each line has a comment showing you the flags for common usage of that daemon or service. Instead, use the rcctl(8) utility to maintain the If the daemon does not automatically detach on startup, remember to add "&" at the end of the command-line. All system daemons are handled by these scripts, and most add-on packages are as well.These scripts, one per daemon, are invoked by variable.Note that rather than having each script in rc.d managing the entire startup, shutdown, reload, restart, and check operations, most rc.d scripts can be reduced to specifying very few variables, and invoking the rc.subr(8) script, which manages most of the standard way of doing these tasks.For example, our above will display root's crontab(5) file.