Hi, On 25 Feb 2025 at 22:59:20, lorenzo wrote: > Hi, > > On Tue, 25 Feb 2025 06:57:36 +0100 > Carles Pina i Estany <car...@pina.cat> wrote: > > > Unpacking simplemonitor (1.13.0-1) ... > > Setting up simplemonitor (1.13.0-1) ... > > Created symlink > > '/etc/systemd/system/multi-user.target.wants/simplemonitor.service' → > > '/usr/lib/systemd/system/simplemonitor.service'. Processing triggers > > for man-db (2.13.0-1) ... ----- > > > > When you said "that should be enough.": do you mean that for a user to > > know that the package is systemd ready this is enough? > > > > Thank you very much, > > Well, I don't use systemd so I'm not able to tell the exact command > but just looking at the man page I think the user can try > > systemctl list-units simplemonitor > or > systemctl status simplemonitor > or > systemctl status --all > > in general I think is reasonable to expect that a user that wants to > play with services is able to use systemctl to search and query a > service status.
In the case of simplemonitor package: what I'd like to do is inform the user that simplemonitor is ready to be used using systemctl (not necessarily how to use systemd). Why I'd like to do that? -As a user sometimes I wonder if some package are meant to be used from systemd or not and what would the systemd unit name would be -I know of some user who installed the package and tried to use it without systemd integration because they didn't know that it was possible (but they knew how to use systemd). Some packages (e.g. syncthing) are using user services (via /lib/systemd/system/syncthing@.service file) so in that case the user would need to do "systemctl restart PACKAGE@user). So it would be nice to tell the user. Another case: the package name and systemd service name might not align (openssh-server package, the systemd service is "ssh"). Or bind9 package, and the systemd service might be bind9 or named. So I still think that there is room to inform users that a package is systemd ready and the name of the service and I wondered if there is a way to do it. > If your package uses dh_installsystemd with default options, the service > should be unmasked, enabled and started by default at install, so your > service comes ready for use even without using systemctl.. It works lovely. Thanks very much! -- Carles Pina i Estany https://carles.pina.cat | car...@pina.cat | cp...@debian.org
signature.asc
Description: PGP signature
