[systemd-devel] Additional error details when resource limits are exceeded

[Tomasz Torcz]

On Wed, Dec 23, 2015 at 04:07:16PM +0100, Kai Krakow wrote:
> Am Wed, 23 Dec 2015 22:55:13 +0800
> schrieb Peter Hoeg <peter at hoeg.com>:
> 
> > >So, Type=forking is the only way to have synchronization points
> > >between service that depend on each other.
> > 
> > In all fairness, the presence of a PID really doesn't say anything
> > either about availability. The only way to be sure is to use
> > Type=Notify with a cooperating daemon.
> 
> Okay, remove "only" from my sentence. It is _one_ way to signal the
> service manager that a service is ready. Apparently, some services
> (like MySQL) do early forking and write the PID file, and only then do
> their initializations. Still, it's better in most cases
> than Type=simple until Type=notify becomes more widely used (as you
> write it needs cooperation of the service).

  MySQL in the form of MariaDB has proper support: https://github.com/MariaDB/server/pull/83

>  Apparently, notifying
> requires including a small systemd specific lib (which does no harm
> when used on non-systemd systems) as far as I understood. But many
> upstreams and even more users would deny or rage against including such
> a library, just because it says "systemd" on its name tag. :-(

  sd_notify() is really couple lines of code which may be reimplemented
easily.  No library required, really.

-- 
Tomasz Torcz                 "God, root, what's the difference?"
xmpp: zdzichubg at chrome.pl         "God is more forgiving."