systemd unit options [[packages/corosync] make sysconfig/corosync-notifyd usable for systemd]

[Jan Rękorajski]

On Mon, 29 Oct 2012, Jakub Bogusz wrote:

> On Mon, Oct 29, 2012 at 04:23:56PM +0100, jajcus wrote:
> > commit ac647687b5d8c7bfb01cd7fc24ef36c23b10cc23
> > Author: Jacek Konieczny <j.konieczny at eggsoft.pl>
> > Date:   Mon Oct 29 16:22:10 2012 +0100
> > 
> >     make sysconfig/corosync-notifyd usable for systemd
> >     
> >     The sysconfig file used by our init script would not be usable for
> >     the sytemd unit got upstream.
> 
> > --- a/corosync-notifyd.sysconfig
> > +++ b/corosync-notifyd.sysconfig
> > @@ -1,12 +1,3 @@
> >  
> > -# Send SNMP traps on all events.
> > -SEND_SNMP_TRAPS=no
> > -
> > -# SNMP Manager IP address (defaults to localhost).
> > -#SNMP_MANAGER=
> > -
> > -# Send DBUS signals on all events.
> > -SEND_DBUS_SIGNALS=yes
> > -
> > -# Log all events.
> > -LOG_ALL_EVENTS=no
> > +# log and signal over DBus all events
> > +OPTIONS=-l -d
> 
> So systemd is so great everyone must learn all daemon options again,
> like it was before SysV scripts/sysconfig were invented?
> 
> There are no upstream solutions?

Only simple environment variables usage.
IMO it's not that big of a problem as often our sysconfig definitions
contain only a random subset of daemon options forcing to mess with
init script. With systemd it's at least clear - one have to read the
manual if (s)he wants some special options.

What we can do in this case is to document the most usefull options
in the sysconfig files.

-- 
Jan Rękorajski                                 | PLD/Linux
SysAdm                                         | http://www.pld-linux.org/
baggins<at>mimuw.edu.pl
baggins<at>pld-linux.org