Hi,

[Service]
Type=forking
PIDFile=/run/teamviewerd.pid
ExecStart=/opt/teamviewer10/tv_bin/teamviewerd -d
Restart=on-abort
StartLimitInterval=60
StartLimitBurst=10

The alternative ExecStart I'm using:

ExecStart=/opt/teamviewer10/tv_bin/teamviewerd -f

And then you can get rid of PIDFile and Type.

Resource limit exhaustion (in kernel sense) is usually easily to be
found in dmesg. I think this wasn't the case here. I propose it was
just because of StartLimitBurst?

I haven't looked at the code, but again, if systemd knows that some limit is 
being exceeded, wouldn't it make sense to say which one?

--
Regards,
Peter
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to