The name of the service (what you use on the command line to start/stop/reload/etc) is declared inside the .service file.
It actually doesn't have to be the same as the name of the service file, although it most often is.
You are welcome to change the name if that will help with remembering the service name.
We possibly should look at the service name and it's file name before 1.9 release to ensure we are following accepted standards
-------- Original message --------
From: Louis <firstname.lastname@example.org>
Date: 4/6/21 09:22 (GMT+08:00)
Subject: [ledgersmb-users] Question re 1.7.29 upgrade from 1.6.32
Looking at https://ledgersmb.org/content/upgrade-ledgersmb-17-16-or-15
" Stop the LedgerSMB application server (e.g. Starman)
$ sudo service starman-ledgersmb stop
Upgrade the LedgerSMB Starman SysV or systemd scripts (the new scripts
can be found in /usr/local/ledgersmb/conf/systemd/ )
$ sudo cp /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service \
$ sudo systemctl daemon-reload
Start the LedgerSMB application server again (Starman example given,
$ sudo service starman-ledgersmb start
Am I misunderstanding something? It seems as though documentation has me
stop the service for 1.6 as starman-ledgersmb, then copy the file
ledgersmb_starman.service to /etc/systemd/system/ledgersmb.service.
After the daemon-reload, I start service starman-ledgersmb.
It seems to me that
/usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service should be
copied to /etc/systemd/system/starman-ledgersmb.service to keep the
service name the same.
Systemd is not my strong suit so I want to confirm the steps before trying
users mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org