systemd doesn't recognize init.d status
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have created systemd script - /etc/systemd/system/test123.service which inside is set to
execute on start/stop the service in /etc/init.d/foo.sh with parameters start/stop,and
foo.sh when started/stopped directly starts/stops the service
The problem I face is, now I want to upgrade to systemd from init.d and when
foo.sh is active ,the systemd script shows to be inactive via the command
"systemctl status test123.service" .Is this behaviour expected or something can be changed
in order systemd to see foo.sh status ?
systemd systemctl
asked Sep 13 at 11:15
Gordon
1
add a comment |Â
up vote
0
down vote
favorite
I have created systemd script - /etc/systemd/system/test123.service which inside is set to
execute on start/stop the service in /etc/init.d/foo.sh with parameters start/stop,and
foo.sh when started/stopped directly starts/stops the service
The problem I face is, now I want to upgrade to systemd from init.d and when
foo.sh is active ,the systemd script shows to be inactive via the command
"systemctl status test123.service" .Is this behaviour expected or something can be changed
in order systemd to see foo.sh status ?
systemd systemctl
asked Sep 13 at 11:15
Gordon
1
You've hand-duplicated a procedure that systemd already does for you. unix.stackexchange.com/a/233581/5132
– JdeBP
Sep 13 at 12:13
I believe systemd has kind of sys V init compatibility, so I don't think that's a good idea of writing a new service but not deleting original initscript service.Maybe just don't do anything (forget about systemd service file and take advantage of compatibility). Or RTFD and write a new service that call the actual service program and delete foo.sh.
– ç¥žç§˜å¾·é‡Œå…‹
Sep 13 at 12:19
Yeah I was thinking before starting the systemd ,just to stop and delete the init.d and then cleanly start using systemd?
– Gordon
Sep 13 at 12:26
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have created systemd script - /etc/systemd/system/test123.service which inside is set to
execute on start/stop the service in /etc/init.d/foo.sh with parameters start/stop,and
foo.sh when started/stopped directly starts/stops the service
The problem I face is, now I want to upgrade to systemd from init.d and when
foo.sh is active ,the systemd script shows to be inactive via the command
"systemctl status test123.service" .Is this behaviour expected or something can be changed
in order systemd to see foo.sh status ?
systemd systemctl
asked Sep 13 at 11:15
Gordon
1
I have created systemd script - /etc/systemd/system/test123.service which inside is set to
execute on start/stop the service in /etc/init.d/foo.sh with parameters start/stop,and
foo.sh when started/stopped directly starts/stops the service
The problem I face is, now I want to upgrade to systemd from init.d and when
foo.sh is active ,the systemd script shows to be inactive via the command
"systemctl status test123.service" .Is this behaviour expected or something can be changed
in order systemd to see foo.sh status ?
systemd systemctl
systemd systemctl
asked Sep 13 at 11:15
Gordon
1
asked Sep 13 at 11:15
Gordon
1
asked Sep 13 at 11:15
Gordon
1
asked Sep 13 at 11:15
Gordon
1
asked Sep 13 at 11:15
Gordon
1
1
You've hand-duplicated a procedure that systemd already does for you. unix.stackexchange.com/a/233581/5132
– JdeBP
Sep 13 at 12:13
I believe systemd has kind of sys V init compatibility, so I don't think that's a good idea of writing a new service but not deleting original initscript service.Maybe just don't do anything (forget about systemd service file and take advantage of compatibility). Or RTFD and write a new service that call the actual service program and delete foo.sh.
– ç¥žç§˜å¾·é‡Œå…‹
Sep 13 at 12:19
Yeah I was thinking before starting the systemd ,just to stop and delete the init.d and then cleanly start using systemd?
– Gordon
Sep 13 at 12:26
add a comment |Â
You've hand-duplicated a procedure that systemd already does for you. unix.stackexchange.com/a/233581/5132
– JdeBP
Sep 13 at 12:13
I believe systemd has kind of sys V init compatibility, so I don't think that's a good idea of writing a new service but not deleting original initscript service.Maybe just don't do anything (forget about systemd service file and take advantage of compatibility). Or RTFD and write a new service that call the actual service program and delete foo.sh.
– ç¥žç§˜å¾·é‡Œå…‹
Sep 13 at 12:19
Yeah I was thinking before starting the systemd ,just to stop and delete the init.d and then cleanly start using systemd?
– Gordon
Sep 13 at 12:26
You've hand-duplicated a procedure that systemd already does for you. unix.stackexchange.com/a/233581/5132
– JdeBP
Sep 13 at 12:13
You've hand-duplicated a procedure that systemd already does for you. unix.stackexchange.com/a/233581/5132
– JdeBP
Sep 13 at 12:13
I believe systemd has kind of sys V init compatibility, so I don't think that's a good idea of writing a new service but not deleting original initscript service.Maybe just don't do anything (forget about systemd service file and take advantage of compatibility). Or RTFD and write a new service that call the actual service program and delete foo.sh.
– ç¥žç§˜å¾·é‡Œå…‹
Sep 13 at 12:19
I believe systemd has kind of sys V init compatibility, so I don't think that's a good idea of writing a new service but not deleting original initscript service.Maybe just don't do anything (forget about systemd service file and take advantage of compatibility). Or RTFD and write a new service that call the actual service program and delete foo.sh.
– ç¥žç§˜å¾·é‡Œå…‹
Sep 13 at 12:19
Yeah I was thinking before starting the systemd ,just to stop and delete the init.d and then cleanly start using systemd?
– Gordon
Sep 13 at 12:26
Yeah I was thinking before starting the systemd ,just to stop and delete the init.d and then cleanly start using systemd?
– Gordon
Sep 13 at 12:26
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
The .service file and the init script must have the same name, is the initscript is called /etc/init.d/foo the service file must be called foo.service
answered Sep 15 at 20:45
Bigon
1,188613
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The .service file and the init script must have the same name, is the initscript is called /etc/init.d/foo the service file must be called foo.service
answered Sep 15 at 20:45
Bigon
1,188613
add a comment |Â
up vote
0
down vote
The .service file and the init script must have the same name, is the initscript is called /etc/init.d/foo the service file must be called foo.service
answered Sep 15 at 20:45
Bigon
1,188613
add a comment |Â
up vote
0
down vote
up vote
0
down vote
The .service file and the init script must have the same name, is the initscript is called /etc/init.d/foo the service file must be called foo.service
answered Sep 15 at 20:45
Bigon
1,188613
The .service file and the init script must have the same name, is the initscript is called /etc/init.d/foo the service file must be called foo.service
answered Sep 15 at 20:45
Bigon
1,188613
answered Sep 15 at 20:45
Bigon
1,188613
answered Sep 15 at 20:45
Bigon
1,188613
answered Sep 15 at 20:45
Bigon
1,188613
1,188613
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468765%2fsystemd-doesnt-recognize-init-d-status%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
You've hand-duplicated a procedure that systemd already does for you. unix.stackexchange.com/a/233581/5132
– JdeBP
Sep 13 at 12:13
I believe systemd has kind of sys V init compatibility, so I don't think that's a good idea of writing a new service but not deleting original initscript service.Maybe just don't do anything (forget about systemd service file and take advantage of compatibility). Or RTFD and write a new service that call the actual service program and delete foo.sh.
– ç¥žç§˜å¾·é‡Œå…‹
Sep 13 at 12:19
Yeah I was thinking before starting the systemd ,just to stop and delete the init.d and then cleanly start using systemd?
– Gordon
Sep 13 at 12:26