...an @reboot line in crontab?
What is the absolute simplest way to autostart it. /etc/init.d and a
script linked to etc/rc?.d? systemd?
Having finally fixed its bugs (don't ask) I have a perfect little daemon
that pops itself in background and runs indefinitely, It isn't leaking
memory and its not crashing and there is no reason it ever should, It accesses files but these will always be present and correct. It will
never need to be killed or HUPed to relaod itself.
What is the absolute simplest way to autostart it. /etc/init.d and a
script linked to etc/rc?.d? systemd?
Raspios is the Os.
On Fri, 11 Aug 2023 12:35:25 +0100
The Natural Philosopher <tnp@invalid.invalid> wrote:
What is the absolute simplest way to autostart it. /etc/init.d and a
script linked to etc/rc?.d? systemd?
/etc/rc.local - if it still exists.
On 11/08/2023 12:35, The Natural Philosopher wrote:
Having finally fixed its bugs (don't ask) I have a perfect littleI've just installed pigpiod
daemon that pops itself in background and runs indefinitely, It isn't
leaking memory and its not crashing and there is no reason it ever
should, It accesses files but these will always be present and
correct. It will never need to be killed or HUPed to relaod itself.
What is the absolute simplest way to autostart it. /etc/init.d and a
script linked to etc/rc?.d? systemd?
Raspios is the Os.
/lib/systemd/system/pigpiod.service
[Unit]
Description=Daemon required to control GPIO pins via pigpio
[Service]
ExecStart=/usr/bin/pigpiod -l
ExecStop=/bin/systemctl kill pigpiod
Type=forking
[Install]
WantedBy=multi-user.target
And then 'systemctl enable pigpiod.service' to put in a link in /etc/systemd/system/multi-user.target.wants
If you change the relevant lines, it should work.
On 11/08/2023 14:35, Chris Elvidge wrote:
On 11/08/2023 12:35, The Natural Philosopher wrote:Ah, that looks neat. Is the "Type=forking" there to tell systemd not to expect it *not* to return?
Having finally fixed its bugs (don't ask) I have a perfect littleI've just installed pigpiod
daemon that pops itself in background and runs indefinitely, It isn't
leaking memory and its not crashing and there is no reason it ever
should, It accesses files but these will always be present and
correct. It will never need to be killed or HUPed to relaod itself.
What is the absolute simplest way to autostart it. /etc/init.d and a
script linked to etc/rc?.d? systemd?
Raspios is the Os.
/lib/systemd/system/pigpiod.service
[Unit]
Description=Daemon required to control GPIO pins via pigpio
[Service]
ExecStart=/usr/bin/pigpiod -l
ExecStop=/bin/systemctl kill pigpiod
Type=forking
[Install]
WantedBy=multi-user.target
And then 'systemctl enable pigpiod.service' to put in a link in
/etc/systemd/system/multi-user.target.wants
If you change the relevant lines, it should work.
Ah, that looks neat. Is the "Type=forking" there to tell systemd not to expect it *not* to return?
On 11/08/2023 13:21, Ahem A Rivet's Shot wrote:
On Fri, 11 Aug 2023 12:35:25 +0100Seems to. Whether it is as redundant as tits on a bull, is less obvious.
The Natural Philosopher <tnp@invalid.invalid> wrote:
What is the absolute simplest way to autostart it. /etc/init.d and a
script linked to etc/rc?.d? systemd?
/etc/rc.local - if it still exists.
Sysop: | Weed Hopper |
---|---|
Location: | Clearwater, FL |
Users: | 14 |
Nodes: | 6 (0 / 6) |
Uptime: | 231:17:35 |
Calls: | 55 |
Calls today: | 1 |
Files: | 50,127 |
D/L today: |
29 files (3,538K bytes) |
Messages: | 275,358 |