27 Nov
2012
27 Nov
'12
4:48 a.m.
Christian Boltz wrote:
Am Montag, 5. November 2012 schrieb Ralf Lang:
I don't think the above is in the spirit of systemd. Ideally atd would
parse /etc/sysconfig/atd itself¹ and set it's defaults accordingly. Using
shell for this kind of things is one of the reasons why init scrips
became such beasts.
cu
Ludwig
[1] maybe we should have a common C library for that task
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG
Nürnberg)
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Am 04.11.2012 16:40, schrieb Christian Boltz:
> Am Samstag, 3. November 2012 schrieb Ralf Lang:
>> Am 03.11.2012 03:29, schrieb Cristian Rodríguez:
> At the risk of scaring you away - one of the first things the
> future maintainer (you?) should do is an update for 12.2 because
> atd doesn't start at all (already fixed in the devel project) and
> the sysconfig options are ignored by the at.service file. See
> https://bugzilla.novell.com/show_bug.cgi?id=780259 for details.
I just fixed this - atd.service now contains:
ExecStart=/bin/bash -c '[ -e /etc/sysconfig/atd ] && . /etc/sysconfig/atd;
exec /usr/sbin/atd $${ATD_BATCH_INTERVAL:+-b $$ATD_BATCH_INTERVAL} $${ATD_LOADAVG:+-l
$$ATD_LOADAVG}'
(should I have added a comment "# looks ugly, but works"? ;-)