Arch Linux

IM back

Member

Registered: 2011-08-03

Posts: 14

Systemd killing pppd?

Im tying to connect to the network on boot via UMTS using sakis3g

Systemd is as always being increddibly frustrating to work with.

Heres the simple unit file im using

[Unit]
Description=skais3g

[Service]
Type=oneshot
#Restart=on-failure
#RestartSec=1s
#ExecStartPre=/usr/bin/sleep 2
ExecStart=/usr/bin/sakis3g USBINTERFACE=0 APN=internet connect

[Install]
WantedBy=multi-user.target

but it dosent work

systemctl status sakis3g.service reporrts:

sakis3g.service - skais3g
   Loaded: loaded (/etc/systemd/system/sakis3g.service; enabled)
   Active: inactive (dead) since Thu 1970-01-01 00:38:56 UTC; 319ms ago
  Process: 20143 ExecStart=/usr/bin/sakis3g USBINTERFACE=0 APN=internet connect (code=exited, status=0/SUCCESS)
 Main PID: 20143 (code=exited, status=0/SUCCESS)

Jan 01 00:38:50 alarmpi pppd[22381]: remote IP address 10.64.64.64
Jan 01 00:38:50 alarmpi pppd[22381]: primary   DNS address 193.189.244.206
Jan 01 00:38:50 alarmpi pppd[22381]: secondary DNS address 193.189.244.225
Jan 01 00:38:55 alarmpi sakis3g[20143]: E1750 connected to o2 - de (26207).
Jan 01 00:38:56 alarmpi pppd[22381]: Terminating on signal 15
Jan 01 00:38:56 alarmpi pppd[22381]: Connect time 0.1 minutes.
Jan 01 00:38:56 alarmpi pppd[22381]: Sent 228 bytes, received 228 bytes.
Jan 01 00:38:56 alarmpi pppd[22381]: Connection terminated.
Jan 01 00:38:56 alarmpi pppd[22381]: Exit.
Jan 01 00:38:56 alarmpi systemd[1]: Started skais3g.

What is sending pppd sig 15 and why?? /usr/bin/sakis3g USBINTERFACE=0 APN=internet connect works fine when used in a shell

Last edited by IM back (2013-11-05 14:43:43)

Stebalien

Member

Registered: 2010-04-27

Posts: 1,239

Website

Re: Systemd killing pppd?

Systemd is as always being increddibly frustrating to work with.

Please always assume user error; it's usually user error.

The problem, as far as I can tell, is that you have set the service type to oneshot. Oneshot tells systemd that the program should run and then it and all it's children should exit. If it or it's children don't exit within a reasonable amount of time, systemd will kill them. First, does sakis3g exit after you run it? If so setting the service type to "forking" should fix your problem. Otherwise, if it doesn't exit, you need to set the service type to "simple".

Last edited by Stebalien (2013-11-05 14:59:17)

---

Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C

IM back

Member

Registered: 2011-08-03

Posts: 14

Re: Systemd killing pppd?

Please always assume user error; it's usually user error.

indeed but I just think that the old iniscripts where more kiss than systemd (at least user facing). But i did'nt mean to start a argument over systemd

Thanks that solved it, next time ill try to read the docs more carefully

IM back

Member

Registered: 2011-08-03

Posts: 14

Re: Systemd killing pppd?

Please always assume user error; it's usually user error.

Indeed, but I think that the old iniscripts where more kiss than systemd (at least user faceing). But i did'nt mean to start a argument over systemd

Thanks that solved it, next time ill try to read the docs more carefully

Last edited by IM back (2013-11-05 15:52:42)