[Nottingham] systemd now puts "mount" into the magical "PID 1"

[Jason Irwin]

On 23/08/16 12:03, Neal Ponton via Nottingham wrote:
> I don't think I've managed to create a 'simple' systemd unit yet without
> it coming up as having problems when running 'systemctl status'.
If you look on the NLUG site, you'll see a quick example of using 
systemd to create an ssh tunnel.
http://nlug.ml1.co.uk/2016/03/resilient-ssh-with-autossh-andor-systemd/5148

I also found using systemd to ensure the VPN client runs at the right 
time to be a snap.

For some other things...I've just stuck to a crontab; they didn't need 
to fuss with system events.

I really like some of the stuff systemd makes easy "This wants that, 
provides other". Makes much more sense to my tiny mind that have 
fragments scattered all over in rc.local, if-up.d etc. (and potentially 
in different places depending on the SysAdmin's style). But then I 
probably don't know enough to understand all the pitfalls.

The PID 1 thing though does worry me more and more though. This is a 
succinct explanation of the issues.
http://ewontfix.com/14/

Anyone have a rebuttal from the systemd-crew on why PID 1 isn't an issue?

-- 
╔═════════════╦══════════════════════════════════════════╗
║ Jason Irwin ║ OpenPGP (GPG/PGP) Public Key: 0xD0C592B1 ║
║             ║ Import from hkp://pgp.mit.edu            ║
╚═════════════╩══════════════════════════════════════════╝