Re: Custom Reload command/signal in upstart
- To: firstname.lastname@example.org
- Subject: Re: Custom Reload command/signal in upstart
- From: Kevin Chadwick <email@example.com>
- Date: Fri, 23 Aug 2013 21:02:47 +0100
- Message-id: <firstname.lastname@example.org>
- In-reply-to: <51A9D283.email@example.com>
- References: <CALjhHG-nOd7qHv-tQrJkEKsvO1m+M8He50YdhsVt84_UhbOSfirstname.lastname@example.org> <20130531224415.GA8976@virgil.dodds.net> <email@example.com> <51A9D283.firstname.lastname@example.org>
> There is no point to start a daemon unless you actually
> need it.
This is complete 'modern' crap
If you don't want a service started then why are your starting it,
because you might want it is a stupid argument with next to no
positives. SSH takes a blink of an eye to start.
It is far better not to mention more secure to start a service during
the pristeen boot phase than wait for it to do it's shizzle including
dropping priviledges etc. upon the receipt of packets.
You have to wait for the bios and hardware so a split second won't
matter on boot. If ever more likely to matter (a second) then it
will be when you need it in fact.
I would also much rather have my daemons ready and waiting than have
them come running when I or an attacker calls.
Having a daemon hanging around with a trigger finger ready to kill
daemons is also really dumb.
'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a