[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sanlock-devel
Subject:    Re: init.d/sanlk-resetd.service
From:       David Teigland <teigland () redhat ! com>
Date:       2014-08-06 19:17:52
Message-ID: 20140806191752.GA29886 () redhat ! com
[Download RAW message or body]

On Wed, Aug 06, 2014 at 02:16:26PM -0400, Nir Soffer wrote:
> I think you need Requires= or Wants= - After will only take effect if services are
> started together. If no services are required or wanted, I guess that systemd will
> happily ignore the After directive.
> 
> Even if this works, it is better to be explicit.
> 
> See http://www.freedesktop.org/software/systemd/man/systemd.unit.html#Before=

That blob of text is not clear, but it seems the thing to do.  It also
seems systemd doesn't want syslog there any more.  So it's now

After=wdmd.service sanlock.service
Requires=wdmd.service sanlock.service

> > +[Service]
> > +Type=forking
> > +ExecStart=/usr/sbin/sanlk-resetd
> 
> Don't you need a PIDFile= option here? How systemd can control the daemon otherwise?
> 
> See http://www.freedesktop.org/software/systemd/man/systemd.service.html#Type=

It seems to work without it.

_______________________________________________
sanlock-devel mailing list
sanlock-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sanlock-devel

[prev in list] [next in list] [prev in thread] [next in thread]