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:
> Tha
more service rather than
restarting.
my previous mail describe what exactly I see in the console.
If you need any more clarification I will provide.
Thanks and regards
Salil
On 11 December 2013 04:55, Lennart Poettering wrote:
> On Mon, 09.12.13 09:47, salil GK (gksa...@gmail.com) wr
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
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
led state. so I would like to
change the state of the service to active (running) at this time so that my
service management framework also would be in good shape.
Thanks
Salil
On 21 November 2013 12:06, David Timothy Strauss wrote:
> On Thu, Nov 21, 2013 at 4:33 PM, salil GK wrote:
> >
Thanks David and Zbyszek
Yes with BindsTo parameter it works
David
I was trying out the options in the unit file hence PID parameter came
in. I forgot to remove that later :-(
some more questions in the same thread -
1. How do I trace the heartbeat message - or rather can I capture th
Hello
I am pretty new to systemd.
I am trying to write two dependent services Myservice and MyserviceTwo.
*Myservice.service*
*[Unit]*
*Description=This is a test service*
*[Service]*
*PIDFile=/var/run/Myservice.pid*
*ExecStartPre=/bin/rm -f /tmp/log.log*
*#ExecStartPre=/usr/bin/systemctl s
