'Twas brillig, and Lennart Poettering at 03/08/12 18:35 did gyre and gimble:
> Hmm, so I actually would like to keep these things separate. I.e. have
> journalctl as client for journald, loginctl of logind, systemctl for
> systemd. In fact, I'd even like to see hostnamectl, timedatectl,
> localectl
'Twas brillig, and Lennart Poettering at 03/08/12 19:46 did gyre and gimble:
> Maybe DontRestartExitStatus=? The libc calls the generalization of
> exit code and exit signal the "exit status", so that sounds like the
> best term to use here.
Would InhibitRestartExitStatus= work for you? Something
On Sun, Aug 5, 2012 at 4:29 AM, Paul Richards wrote:
> I'm trying to make this into a rpm package so that I can continue to
> tell my users to look into /var/log/messages for logging results of my
> program on bootup.
>
> I tried the:
>
> After=syslog.target
That's not needed, syslog is always av
I'm trying to make this into a rpm package so that I can continue to
tell my users to look into /var/log/messages for logging results of my
program on bootup.
I tried the:
After=syslog.target
in the service file but that had no effect. Is there a way tell
systemd to pass the message to the syslo
Great, thanks for the info!
On Thu, Aug 2, 2012 at 5:03 AM, Mathieu Bridon
wrote:
> On Wed, 2012-08-01 at 23:57 -0400, Paul Richards wrote:
>> 1. My program just runs once on startup and then exits. Do I need to
>> put anything in the service file for that?
>
> Use "Type=oneshot" in the "Service"
