| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 35 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 18:42:59 |
| Calls: | 321 |
| Calls today: | 1 |
| Files: | 957 |
| Messages: | 82,382 |
On Wed, 26 Feb 2025 06:37:43 +0100
Carles Pina i Estany <carles@pina.cat> wrote:
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.
then you can use the package description to mention that the package
include a simplemonitor systemd service
I've packaged "simplemonitor". The package adds a simplemonitor user,
and a systemd service to run simplemonitor under this user and using the configuration files from /etc/simplemonitor
I know that some user did "apt install simplemonitor" and then tried to
use simplemonitor without systemd (which is possible, but reinventing
the wheel). The user tried it that because he didn't realise that simplemonitor was integrated with systemd, the simplemonitor system
user, checks on startup, etc.
My question is: how to inform users about systemd integration?
But I wonder of any more standard ways to do that, what other packages
do, etc.
Hello,
I've packaged "simplemonitor". The package adds a simplemonitor user,
and a systemd service to run simplemonitor under this user and using
the configuration files from /etc/simplemonitor
I know that some user did "apt install simplemonitor" and then tried
to use simplemonitor without systemd (which is possible, but
reinventing the wheel). The user tried it that because he didn't
realise that simplemonitor was integrated with systemd, the
simplemonitor system user, checks on startup, etc.
My question is: how to inform users about systemd integration?
As a user, what I do when I wonder about that is "dpkg -L PACKAGE"
and see if I spot some systemd service files. And also tend to read /usr/share/doc/PACKAGE/changelog.Debian.gz or related files to see if
the maintainer wrote any information there.
To be more proactive about that, I thought to add a debconf template
with something such as (untested, just the idea):
----
Template: simplemonitor/systemd-info
Type: note
_Description: Usage of simplemonitor
The simplemonitor package integrates with systemd. Set it up in
/etc/simplemonitor and then use:
sudo systemctl restart simplemonitor
----
But I wonder of any more standard ways to do that, what other packages
do, etc.
Thanks very much!
Hi,
On Mon, 24 Feb 2025 11:48:03 +0100
Carles Pina i Estany <carles@pina.cat> wrote:
Hello,
I've packaged "simplemonitor". The package adds a simplemonitor user,
and a systemd service to run simplemonitor under this user and using
the configuration files from /etc/simplemonitor
I know that some user did "apt install simplemonitor" and then tried
to use simplemonitor without systemd (which is possible, but
reinventing the wheel). The user tried it that because he didn't
realise that simplemonitor was integrated with systemd, the
simplemonitor system user, checks on startup, etc.
My question is: how to inform users about systemd integration?
If your package uses dh_installsystemd to integrate with systemd, that
should be enough.
My question is: how to inform users about systemd integration?
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,
Hi,
On Tue, 25 Feb 2025 06:57:36 +0100
Carles Pina i Estany <carles@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.
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..
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.