On Mon, Apr 03, 2017 at 09:36:16AM -0500, Tom Browder wrote: > But I kind of understand why systemd, but I wish I could find a good > cookbook description of how to add or modify a new process.
I like the "systemd vs. sysvinit" cheatsheet at http://linoxide.com/linux-command/systemd-vs-sysvinit-cheatsheet/ .....Nick On Mon, Apr 3, 2017 at 11:14 AM, Kevin O'Gorman <kogor...@gmail.com> wrote: > > > On Mon, Apr 3, 2017 at 8:39 AM, Greg Wooledge <wool...@eeg.ccf.org> wrote: > >> On Mon, Apr 03, 2017 at 09:36:16AM -0500, Tom Browder wrote: >> > But I kind of understand why systemd, but I wish I could find a good >> > cookbook description of how to add or modify a new process. >> >> The first hurdle is learning the terminology that systemd uses. It's >> not exactly intuitive. >> > > >> [...] >> >> If you want to change your system's "run level" from graphical.target >> to multi-user.target, run this command as root: >> >> # systemctl set-default multi-user.target >> >> To see a list of your available targets (assuming no major local changes), >> use this command: >> >> $ find /lib/systemd/ -name '*.target' >> >> > Are you sure? On my system, this produces nothing at all. But the > directory > exists and is populated. > > > > -- > Kevin O'Gorman > #define QUESTION ((bb) || (!bb)) /* Shakespeare */ > > Please consider the environment before printing this email. >
