Re: [systemd-devel] one shot service exit-code

2017-10-31 Thread Matt Zagrabelny
On Tue, Oct 31, 2017 at 11:21 AM, Reindl Harald 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 clea

Re: [systemd-devel] one shot service exit-code

2017-10-31 Thread Reindl Harald
Am 31.10.2017 um 17:26 schrieb Matt Zagrabelny: On Tue, Oct 31, 2017 at 11:21 AM, Reindl Harald > 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 se

Re: [systemd-devel] one shot service exit-code

2017-10-31 Thread Matt Zagrabelny
On Tue, Oct 31, 2017 at 11:29 AM, Reindl Harald wrote: > > >> 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 g

Re: [systemd-devel] one shot service exit-code

2017-10-31 Thread Reindl Harald
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

[systemd-devel] one shot service exit-code

2017-10-31 Thread Matt Zagrabelny
Greetings, 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. Here is the udev rules. Added for completeness: % cat /etc/udev/rules.d/90-galaxy-note-3.rules # Downloa