[systemd-devel] one shot service exit-code

[Reindl Harald]

Am 31.10.2017 um 17:26 schrieb Matt Zagrabelny:
> On Tue, Oct 31, 2017 at 11:21 AM, Reindl Harald <h.reindl at thelounge.net 
> <mailto:h.reindl at thelounge.net>> wrote:
> 
> 
> 
>     Am 31.10.2017 um 17:06 schrieb Matt Zagrabelny:
> 
>         I have phone that I plug into my computer and have a udev rule
>         to fire off a systemd service. Things work well, but the journal
>         indicates that the command isn't terminating cleanly.
> 
>         However here is the journal when I plug in the phone:
> 
>         Oct 31 10:53:54 eruke systemd[1274]: Starting
>         download-photos at SAMSUNG_SAMSUNG_Android_17b765cc.service...
>         Oct 31 10:53:55 eruke systemd[1274]:
>         download-photos at SAMSUNG_SAMSUNG_Android_17b765cc.service: Main
>         process exited, code=exited, status=255/n/a
> 
> 
>     SuccessExitStatus=255
> 
>         Does anyone have any ideas how systemd is interacting (killing?)
>         with the mate-terminal?
> 
> 
>     just tell systemd 255 is a normal exit code, see above
> 
> 
> Thanks Reindl!
> 
> Any ideas why the terminal exit code is 0 from another terminal, but 
> when systemd spawns it, it is 255?

that's a question for gnome developers and i din't touch anything from 
them until i am forced so, they probalby don't gasp the 0 is the default 
return code on unix/linux