| Summary: | systemd kills running ppp daemon | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Michael Tremer <michael.tremer> |
| Component: | systemd | Assignee: | Stefan Schantl <stefan.schantl> |
| Status: | CLOSED FIXED | QA Contact: | Michael Tremer <michael.tremer> |
| Severity: | - Unknown - | ||
| Priority: | - Unknown - | CC: | arne.fitzenreiter |
| Version: | 3 | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
Problem has been fixed with the introducion of the "pppd-angel". The fix can be found here: http://git.ipfire.org/?p=network.git;a=commit;h=ea5f63541bc739489f5f9f61051c1de991ffc25e |
There is a very mysterious problem with pppd and systemd. It happens when you use the modem hook with an UMTS modem (should happen with everything else as well, but I only have this device). I created the zone with the following command: network zone create upl3 modem --apn="event.vodafone.de" --pin=1234 --username="test" --password="test" --device="/dev/ttyUSB0" --monitor-device="/dev/ttyUSB1" Then, the create the connection: network zone upl3 up The connection gets established and is immediately stopped. pppd exits with code 16. We are using Type=forking with PIDFile here, which will block systemctl until the first pppd process is finished creating the connection, but pppd will fork into the background. The background process is the one that gets killed. The problem can be worked around by replacing pppd by a shell script like this: pppd: > #!/bin/bash > pppd.bin $@ > sleep 30 where pppd is the actual ppp daemon. The reason why this works is that after pppd has detached, there will be a short time for systemd to read the main pid and when the sleep command has finished, systemd will let the background daemon alone. The connection works totally fine when starting pppd by hand.