(Migrated) Zato and Linux systemd current status

(This message has been automatically imported from the retired mailing list)

Hi all,

is there anyone familiar with Linux systemd around perhaps?

In short - I’m starting a Zato server from ~env/qs-1/server1 with
zato.service …

[Service]
ExecStart=/etc/init.d/zato start
Type=oneshot
RemainAfterExit=yes

… where /etc/init.d/zato is a sysV init script with start/stop/status
options.

It’s working properly with systemctl start/stop, but I can’t find a way
to call the script with systemctl status command to show the current
status.

It shows only the console output grabbed at the time systemctl start was
issued.

Can anyone perhaps shed some light on it - in particular, how to make
status show the current status of a service with systemd?

Thanks.

On 12/5/2014 2:36 PM, Andrzej Wróbel wrote:

Hi all,

is there anyone familiar with Linux systemd around perhaps?

In short - I’m starting a Zato server from ~env/qs-1/server1 with
zato.service …

[Service]
ExecStart=/etc/init.d/zato start
Type=oneshot
RemainAfterExit=yes

… where /etc/init.d/zato is a sysV init script with start/stop/status
options.

It’s working properly with systemctl start/stop, but I can’t find a way
to call the script with systemctl status command to show the current
status.

It shows only the console output grabbed at the time systemctl start was
issued.

Can anyone perhaps shed some light on it - in particular, how to make
status show the current status of a service with systemd?

Lennart suggests writing your own command line tool to show status
beyond what systemd shows about its own internal state:

http://comments.gmane.org/gmane.comp.sysutils.systemd.devel/3050

Hi Erick, thanks your input!