[systemd-devel] why don't "/usr/bin/systemd-run -t" finish within a cronjob anymore?

[Reindl Harald]

no response, but please stay on-list

anyways, i removed "-t" which works fine outside cronjobs but no longer
when called from crond, in that case no problem, normally not what you
want because it don't block and follow-up commands should not get
started in many usecases

/usr/bin/systemd-run -p StandardOutput=null -p ProtectSystem=full -p
ProtectHome=yes -p PrivateDevices=yes -p PrivateTmp=yes -p
NoNewPrivileges=yes --quiet --nice=19 --uid=wwwcron --gid=apache
/usr/bin/bash /usr/local/scripts/webalizer.sh

Am 10.10.18 um 13:07 schrieb Andy Pieters:
> Hi Reindl
> 
> I am interested in finding out the solution to your problem.
> 
> Have you had any results off-list perhaps because I do not see any
> replies to your message.
> 
> Thank you
> On Sun, Oct 7, 2018 at 12:26 AM Reindl Harald <h.reindl at thelounge.net> wrote:
>>
>> Fedora 28:
>>
>> root        7902  0.0  0.0  75008  3532 ?        SN   00:07   0:00
>> /usr/bin/systemd-run -t -p ProtectSystem=full -p ProtectHome=yes -p
>> PrivateDevices=yes -p PrivateTmp=yes -p NoNewPrivileges=yes --quiet
>> --nice=19 --uid=wwwcron --gid=apache /usr/bin/bash
>> /usr/local/scripts/webalizer.sh
>>
>> last line of the script:
>> /usr/bin/echo "$MY_DATE $MY_TIME  Statistiken abgeschlossen." >>
>> /Volumes/dune/www-servers/_logs/usages.log
>>
>> last line of the logfile:
>> 07-10-2018 00:12:51  Statistiken abgeschlossen
>>
>> ------------------
>>
>> "/usr/bin/systemd-run" is started within a root-cronjob like all the
>> months before - so why in the world does it never finish after upgrade
>> to F28 with systemd-238-9.git0e0aa59.fc28.x86_64?
>>
>> ------------------
>>
>> and yes it's "finished" at reboot - until last night the call had
>> "--unit=webalizer.service" which leaded to erroes that the unit already
>> exists and execution was skipped - at reboot i had crap bash errors as
>> system mails
>>
>> what in the world is going on here?
>>
>> ------------------
>>
>> and yes there are good reasons to call "systemd-run" from a cron script...