[systemd-devel] simple service shell script filling journal

Reindl Harald h.reindl at thelounge.net
Mon Dec 29 12:53:09 PST 2014

Am 29.12.2014 um 21:48 schrieb Larry Harmon:
>>> try "StandardOutput=null" inside [Service]
> Yes, this worked.  (not sure why)

because the service binary spits out that information to stdout instead 
syslog and journald collects stout to not lose any message - otherwise 
you would not be aware of errors from broken apps spit them to stdout 
instead stderror

a sane intended to run as service app (meaning in background) would not 
output messages to stdout - make a bugreport upstream

> -----Original Message-----
> From: systemd-devel [mailto:systemd-devel-bounces at lists.freedesktop.org] On Behalf Of Reindl Harald
> Sent: Monday, December 29, 2014 3:28 PM
> To: systemd-devel at lists.freedesktop.org
> Subject: Re: [systemd-devel] simple service shell script filling journal
> Am 29.12.2014 um 21:16 schrieb Larry Harmon:
>> I am using a simple shell script, started by system, to set LEDs on a
>> Marvell Armada 370 plug.
>> The script uses a while loop with a "sleep 30" line
>> Exiting sleep seems to log to the journal, filling it with useless info.
>> How can I change this behavior?
>> I have tried different service types (fork, oneshot) as well as an
>> intermediate shell script which starts the real script, no luck!
>> The journal output looks like:
>> Dec 22 19:19:12 rrap-0281aa.local LEDupdater.sh[188]: Active: active
>> (running) since Mon 2014-12-22 18:30:45 UTC; 48min ago
> try "StandardOutput=null" inside [Service]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20141229/4d91c252/attachment.sig>

More information about the systemd-devel mailing list