Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-12-12 Thread salil GK
I think my system had a bit older minor version of systemd ( systemd-204-8.fc19.x86_64 ). In another system I have tested where I have systemd higher version - where the issue is not there - ( systemd-204-17.fc19.x86_64 ). Thanks Salil On 11 December 2013 06:15, salil GK wrote: > Thanks Lennar

Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-12-10 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Dec 11, 2013 at 06:15:02AM +0530, salil GK wrote: > Thanks Lennart for the reply. > > The issue that I am facing is with the restart feature of systemd. > > I have configured my unit file as Restart=on-failure > > when the service fail to send watchdog signal the expectation is - system

Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-12-10 Thread salil GK
Thanks Lennart for the reply. The issue that I am facing is with the restart feature of systemd. I have configured my unit file as Restart=on-failure when the service fail to send watchdog signal the expectation is - systemd will restart the service. what I observed is - systemd started one mo

Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-12-10 Thread Lennart Poettering
On Mon, 09.12.13 09:47, salil GK (gksa...@gmail.com) wrote: > Hello > >did any body get a chance to look into this. I am a kind of stuck on > this. I can work around using ExecStartPre script where I can kill the > previous instances. But if systemd is capable to do it by itself, that > woul

Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-12-08 Thread salil GK
Hello did any body get a chance to look into this. I am a kind of stuck on this. I can work around using ExecStartPre script where I can kill the previous instances. But if systemd is capable to do it by itself, that would be the neat solution. Thanks ~S On 5 December 2013 13:19, salil GK

Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-12-04 Thread salil GK
Hello I am using Fedora 19 and systemd in it is 204 I guess. The issue is present in there. The following is whatmy unit file is cat /usr/lib/systemd/system/Myservice.service [Unit] Description=This is a test service [Service] #PIDFile=/var/run/Myservice.pid #ExecStartPre=/tmp/one_start_pr

Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-11-26 Thread Hoyer, Marko (ADITG/SW2)
> >One more issue I observed is - if I specify Restart=on-failure, if > > watchdog timer expire, it restart the service. But I can see that it > > create two processes rather than restarting the process. But if I do > > systemctl restart Myservice , it kills the previous instance of > > service

Re: [systemd-devel] Question regarding the NotifyAccess parameter

2013-11-26 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Nov 21, 2013 at 08:56:25PM +0530, salil GK wrote: > Hello > >I have a service in shell script in which I am sending notification to > systemd using `systemd-notify WATCHDOG=1` command. What happens is - > systemd-notify will be a child process and in the systemd notification will > not