Re: [systemd-devel] Additional error details when resource limits are exceeded

Hi, Type=simple cannot detect when a service is ready. Systemd simply of teamviewerd but with service inter-dependencies this becomes important. Type=simple considers the service up immediatly thus triggering dependent service for immediate execution while Type=forking considers the service up

Re: [systemd-devel] Additional error details when resource limits are exceeded

On Wed, Dec 23, 2015 at 04:07:16PM +0100, Kai Krakow wrote: > Am Wed, 23 Dec 2015 22:55:13 +0800 > schrieb Peter Hoeg : > > > >So, Type=forking is the only way to have synchronization points > > >between service that depend on each other. > > > > In all fairness, the presence of

Re: [systemd-devel] Additional error details when resource limits are exceeded

Am Wed, 23 Dec 2015 22:55:13 +0800 schrieb Peter Hoeg : > Hi, > > >Type=simple cannot detect when a service is ready. Systemd simply > >of teamviewerd but with service inter-dependencies this becomes > >important. > > > >Type=simple considers the service up immediatly thus

Re: [systemd-devel] Additional error details when resource limits are exceeded

Am Tue, 22 Dec 2015 08:41:14 +0800 schrieb Peter Hoeg : > 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

Re: [systemd-devel] Additional error details when resource limits are exceeded

Am Wed, 9 Dec 2015 11:45:00 +0800 schrieb Peter Hoeg : > Hi, > > it turns out that the teamviewer daemon wasn't behaving correctly and > double-forked before the PID file was written. Fixed by running it as > Type=simple and in the foreground. > > It however, still doesn't

Re: [systemd-devel] Additional error details when resource limits are exceeded

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

Re: [systemd-devel] Additional error details when resource limits are exceeded

Hi, it turns out that the teamviewer daemon wasn't behaving correctly and double-forked before the PID file was written. Fixed by running it as Type=simple and in the foreground. It however, still doesn't change anything about the error message, which is just plain wrong in this case as

[systemd-devel] Additional error details when resource limits are exceeded

Hi, I'm using systemd 228-3 on Arch Linux (up-to-date as of time of writing) and am having an issue figuring out why a particular service fails to run. The message I am getting is "Job for teamviewerd.service failed because a configured resource limit was exceeded." but how do I figure out