How to remove a systemd wrapper script for sysV service and use a unit file instead?

up vote
2
down vote

favorite

I'm trying to un-configure or remove a systemd wrapper script for an old sysV service. The wrapper is provided by a Debian package so I can't just delete it.

The wrapper shows up as an artifact and is listed as "generated":

$ systemctl list-unit-files | grep -i -E 'rng|rand'
rng-tools.service generated
systemd-random-seed.service static
urandom.service static

I added a new systemd service to replace it according to Creating and Modifying systemd Unit Files:

# touch /etc/systemd/system/rng-tools.service
# chmod 664 /etc/systemd/system/rng-tools.service
# emacs /etc/systemd/system/rng-tools.service
<edit file>

However, when I try to enable the new service file the old sysV script is used instead:

# systemctl enable rng-tools
Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

Searching has turned up 0 hits to remove the old wrapper. I get lots of similar hits, like creating a wrapper script. But I have not found information on removing one from systemd's database.

How do I un-configure or remove a systemd wrapper script for sysV service?

And here are the result after Stephen's suggestion. The new rng-tools.service is being used:

$ systemctl status rng-tools
Ã¢Â—Â rng-tools.service - Entropy daemon for /dev/random using a hardware RNG
 Loaded: loaded (/etc/systemd/system/rng-tools.service; enabled; vendor preset
 Active: failed (Result: exit-code) since Mon 2018-10-15 07:19:32 EDT; 20min a
 Main PID: 674 (code=exited, status=1/FAILURE)

And:

# journalctl -b -u rng-tools.service
-- Logs begin at Mon 2018-10-15 07:19:29 EDT, end at Mon 2018-10-15 07:49:13 EDT. --
Oct 15 07:19:31 beaglebone systemd[1]: Started Entropy daemon for /dev/random using a hardware RNG.
Oct 15 07:19:31 beaglebone rngd[674]: can't open /dev/hwrng: No such file or directory
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Unit entered failed state.
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Failed with result 'exit-code'.

And:

# dd if=/dev/hwrng count=16 bs=1
Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’ÃˆÂ¿Ã¢Â–Â’3Ã¢Â–Â’Ã¢Â–Â’ Ã¢Â–Â’Ã¢Â–Â’#16+0 records in
16+0 records out
16 bytes (16 B) copied, 0.00942799 s, 1.7 kB/s

And for completeness, here is the new rng-tools.service:

# cat /etc/systemd/system/rng-tools.service
# ...

[Unit]
Description=Entropy daemon for /dev/random using a hardware RNG
After=syslog.target
Requires=syslog.target

[Service]
Type=simple
ExecStart=/usr/sbin/rngd -r /dev/hwrng -f

[Install]
WantedBy=basic.target

edited 1 hour ago

asked 3 hours ago

jww

1,49532157

This is a follow-on question from unix.stackexchange.com/questions/475489 .
â€“Â JdeBP
2 hours ago

add a commentÂ |Â

up vote
2
down vote

favorite

I'm trying to un-configure or remove a systemd wrapper script for an old sysV service. The wrapper is provided by a Debian package so I can't just delete it.

The wrapper shows up as an artifact and is listed as "generated":

$ systemctl list-unit-files | grep -i -E 'rng|rand'
rng-tools.service generated
systemd-random-seed.service static
urandom.service static

I added a new systemd service to replace it according to Creating and Modifying systemd Unit Files:

# touch /etc/systemd/system/rng-tools.service
# chmod 664 /etc/systemd/system/rng-tools.service
# emacs /etc/systemd/system/rng-tools.service
<edit file>

However, when I try to enable the new service file the old sysV script is used instead:

# systemctl enable rng-tools
Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

Searching has turned up 0 hits to remove the old wrapper. I get lots of similar hits, like creating a wrapper script. But I have not found information on removing one from systemd's database.

How do I un-configure or remove a systemd wrapper script for sysV service?

And here are the result after Stephen's suggestion. The new rng-tools.service is being used:

$ systemctl status rng-tools
Ã¢Â—Â rng-tools.service - Entropy daemon for /dev/random using a hardware RNG
 Loaded: loaded (/etc/systemd/system/rng-tools.service; enabled; vendor preset
 Active: failed (Result: exit-code) since Mon 2018-10-15 07:19:32 EDT; 20min a
 Main PID: 674 (code=exited, status=1/FAILURE)

And:

# journalctl -b -u rng-tools.service
-- Logs begin at Mon 2018-10-15 07:19:29 EDT, end at Mon 2018-10-15 07:49:13 EDT. --
Oct 15 07:19:31 beaglebone systemd[1]: Started Entropy daemon for /dev/random using a hardware RNG.
Oct 15 07:19:31 beaglebone rngd[674]: can't open /dev/hwrng: No such file or directory
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Unit entered failed state.
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Failed with result 'exit-code'.

And:

# dd if=/dev/hwrng count=16 bs=1
Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’ÃˆÂ¿Ã¢Â–Â’3Ã¢Â–Â’Ã¢Â–Â’ Ã¢Â–Â’Ã¢Â–Â’#16+0 records in
16+0 records out
16 bytes (16 B) copied, 0.00942799 s, 1.7 kB/s

And for completeness, here is the new rng-tools.service:

# cat /etc/systemd/system/rng-tools.service
# ...

[Unit]
Description=Entropy daemon for /dev/random using a hardware RNG
After=syslog.target
Requires=syslog.target

[Service]
Type=simple
ExecStart=/usr/sbin/rngd -r /dev/hwrng -f

[Install]
WantedBy=basic.target

edited 1 hour ago

asked 3 hours ago

jww

1,49532157

This is a follow-on question from unix.stackexchange.com/questions/475489 .
â€“Â JdeBP
2 hours ago

add a commentÂ |Â

up vote
2
down vote

favorite

I'm trying to un-configure or remove a systemd wrapper script for an old sysV service. The wrapper is provided by a Debian package so I can't just delete it.

The wrapper shows up as an artifact and is listed as "generated":

$ systemctl list-unit-files | grep -i -E 'rng|rand'
rng-tools.service generated
systemd-random-seed.service static
urandom.service static

I added a new systemd service to replace it according to Creating and Modifying systemd Unit Files:

# touch /etc/systemd/system/rng-tools.service
# chmod 664 /etc/systemd/system/rng-tools.service
# emacs /etc/systemd/system/rng-tools.service
<edit file>

However, when I try to enable the new service file the old sysV script is used instead:

# systemctl enable rng-tools
Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

Searching has turned up 0 hits to remove the old wrapper. I get lots of similar hits, like creating a wrapper script. But I have not found information on removing one from systemd's database.

How do I un-configure or remove a systemd wrapper script for sysV service?

And here are the result after Stephen's suggestion. The new rng-tools.service is being used:

$ systemctl status rng-tools
Ã¢Â—Â rng-tools.service - Entropy daemon for /dev/random using a hardware RNG
 Loaded: loaded (/etc/systemd/system/rng-tools.service; enabled; vendor preset
 Active: failed (Result: exit-code) since Mon 2018-10-15 07:19:32 EDT; 20min a
 Main PID: 674 (code=exited, status=1/FAILURE)

And:

# journalctl -b -u rng-tools.service
-- Logs begin at Mon 2018-10-15 07:19:29 EDT, end at Mon 2018-10-15 07:49:13 EDT. --
Oct 15 07:19:31 beaglebone systemd[1]: Started Entropy daemon for /dev/random using a hardware RNG.
Oct 15 07:19:31 beaglebone rngd[674]: can't open /dev/hwrng: No such file or directory
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Unit entered failed state.
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Failed with result 'exit-code'.

And:

# dd if=/dev/hwrng count=16 bs=1
Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’ÃˆÂ¿Ã¢Â–Â’3Ã¢Â–Â’Ã¢Â–Â’ Ã¢Â–Â’Ã¢Â–Â’#16+0 records in
16+0 records out
16 bytes (16 B) copied, 0.00942799 s, 1.7 kB/s

And for completeness, here is the new rng-tools.service:

# cat /etc/systemd/system/rng-tools.service
# ...

[Unit]
Description=Entropy daemon for /dev/random using a hardware RNG
After=syslog.target
Requires=syslog.target

[Service]
Type=simple
ExecStart=/usr/sbin/rngd -r /dev/hwrng -f

[Install]
WantedBy=basic.target

edited 1 hour ago

asked 3 hours ago

jww

1,49532157

I'm trying to un-configure or remove a systemd wrapper script for an old sysV service. The wrapper is provided by a Debian package so I can't just delete it.

The wrapper shows up as an artifact and is listed as "generated":

$ systemctl list-unit-files | grep -i -E 'rng|rand'
rng-tools.service generated
systemd-random-seed.service static
urandom.service static

I added a new systemd service to replace it according to Creating and Modifying systemd Unit Files:

# touch /etc/systemd/system/rng-tools.service
# chmod 664 /etc/systemd/system/rng-tools.service
# emacs /etc/systemd/system/rng-tools.service
<edit file>

However, when I try to enable the new service file the old sysV script is used instead:

# systemctl enable rng-tools
Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

Searching has turned up 0 hits to remove the old wrapper. I get lots of similar hits, like creating a wrapper script. But I have not found information on removing one from systemd's database.

How do I un-configure or remove a systemd wrapper script for sysV service?

And here are the result after Stephen's suggestion. The new rng-tools.service is being used:

$ systemctl status rng-tools
Ã¢Â—Â rng-tools.service - Entropy daemon for /dev/random using a hardware RNG
 Loaded: loaded (/etc/systemd/system/rng-tools.service; enabled; vendor preset
 Active: failed (Result: exit-code) since Mon 2018-10-15 07:19:32 EDT; 20min a
 Main PID: 674 (code=exited, status=1/FAILURE)

And:

# journalctl -b -u rng-tools.service
-- Logs begin at Mon 2018-10-15 07:19:29 EDT, end at Mon 2018-10-15 07:49:13 EDT. --
Oct 15 07:19:31 beaglebone systemd[1]: Started Entropy daemon for /dev/random using a hardware RNG.
Oct 15 07:19:31 beaglebone rngd[674]: can't open /dev/hwrng: No such file or directory
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Unit entered failed state.
Oct 15 07:19:32 beaglebone systemd[1]: rng-tools.service: Failed with result 'exit-code'.

And:

# dd if=/dev/hwrng count=16 bs=1
Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’Ã¢Â–Â’ÃˆÂ¿Ã¢Â–Â’3Ã¢Â–Â’Ã¢Â–Â’ Ã¢Â–Â’Ã¢Â–Â’#16+0 records in
16+0 records out
16 bytes (16 B) copied, 0.00942799 s, 1.7 kB/s

And for completeness, here is the new rng-tools.service:

# cat /etc/systemd/system/rng-tools.service
# ...

[Unit]
Description=Entropy daemon for /dev/random using a hardware RNG
After=syslog.target
Requires=syslog.target

[Service]
Type=simple
ExecStart=/usr/sbin/rngd -r /dev/hwrng -f

[Install]
WantedBy=basic.target

linux debian systemd arm

edited 1 hour ago

asked 3 hours ago

jww

1,49532157

edited 1 hour ago

asked 3 hours ago

jww

1,49532157

edited 1 hour ago

asked 3 hours ago

jww

1,49532157

asked 3 hours ago

jww

1,49532157

asked 3 hours ago

jww

1,49532157

This is a follow-on question from unix.stackexchange.com/questions/475489 .
â€“Â JdeBP
2 hours ago

add a commentÂ |Â

This is a follow-on question from unix.stackexchange.com/questions/475489 .
â€“Â JdeBP
2 hours ago

This is a follow-on question from unix.stackexchange.com/questions/475489 .
â€“Â JdeBP
2 hours ago

add a commentÂ |Â

1 Answer
1

active

oldest

votes

up vote
3
down vote

accepted

Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

only means that systemd is Ã¢Â€ÂœawareÃ¢Â€Â that thereÃ¢Â€Â™s a sysvinit-style init script present, and that it needs to take it into account when considering the state of the rng-tools service. It doesnÃ¢Â€Â™t mean that itÃ¢Â€Â™s going to use the init script to manage the service.

If both an init script and a unit file are present, systemd will use the latter (at least, when the service isnÃ¢Â€Â™t running).

You can see which file is used to start a service by running systemctl status; the Ã¢Â€ÂœLoadedÃ¢Â€Â line will show which script was used. For example, hereÃ¢Â€Â™s a service which has both a systemd unit and an init script:

Ã¢Â—Â infnoise.service - Wayward Geek InfNoise TRNG driver
 Loaded: loaded (/lib/systemd/system/infnoise.service; enabled; vendor preset: enabled)

HereÃ¢Â€Â™s a service which only has an init script:

Ã¢Â—Â sensord.service - LSB: lm-sensors daemon
 Loaded: loaded (/etc/init.d/sensord; generated; vendor preset: enabled)

Checking your service should show that systemd is using your new unit.

If all else fails, you can delete /etc/init.d/rng-tools: it should be tracked as a conffile, and dpkg will note that it was deleted and wonÃ¢Â€Â™t restore it on package upgrades. /etc is owned by the system administrator, not the packaging system, even though packages can install files there.

edited 2 hours ago

answered 3 hours ago

Stephen Kitt

150k23333401

Thanks @Stephen. OK, so I removed the changes to rc.local that manually enabled rng-tools, and I left the new rng-tools.service in place. Unfortunately no joy. The service did not start and /dev/random is out of entropy. But it does look like the new service was used. It is amazing /usr/sbin/rngd -r /dev/hwrng -f works from rc.local but not rng-tools.service.
â€“Â jww
2 hours ago

What does systemctl status show after trying to start the service? Could it be that /dev/hwrng isnÃ¢Â€Â™t available early enough?
â€“Â Stephen Kitt
2 hours ago

Given the timestamps in the logs, I take it the unit fails to start at boot, is that right? What happens if you restart it afterwards? You might need to trigger the unit from a udev rule so that it starts after the hwnrg device is available.
â€“Â Stephen Kitt
2 hours ago

M. Kitt may also be interested in the status of dev-hwrng.device.
â€“Â JdeBP
2 hours ago

@JdeBP thatÃ¢Â€Â™s assuming that the udev rule tags the device appropriately; but weÃ¢Â€Â™re addressing the parent question at this point...
â€“Â Stephen Kitt
2 hours ago

Â |Â
show 4 more comments

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475555%2fhow-to-remove-a-systemd-wrapper-script-for-sysv-service-and-use-a-unit-file-inst%23new-answer', 'question_page');

);

Post as a guest

Name

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
3
down vote

accepted

Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

If both an init script and a unit file are present, systemd will use the latter (at least, when the service isnÃ¢Â€Â™t running).

Ã¢Â—Â infnoise.service - Wayward Geek InfNoise TRNG driver
 Loaded: loaded (/lib/systemd/system/infnoise.service; enabled; vendor preset: enabled)

HereÃ¢Â€Â™s a service which only has an init script:

Ã¢Â—Â sensord.service - LSB: lm-sensors daemon
 Loaded: loaded (/etc/init.d/sensord; generated; vendor preset: enabled)

Checking your service should show that systemd is using your new unit.

edited 2 hours ago

answered 3 hours ago

Stephen Kitt

150k23333401

Thanks @Stephen. OK, so I removed the changes to rc.local that manually enabled rng-tools, and I left the new rng-tools.service in place. Unfortunately no joy. The service did not start and /dev/random is out of entropy. But it does look like the new service was used. It is amazing /usr/sbin/rngd -r /dev/hwrng -f works from rc.local but not rng-tools.service.
â€“Â jww
2 hours ago

What does systemctl status show after trying to start the service? Could it be that /dev/hwrng isnÃ¢Â€Â™t available early enough?
â€“Â Stephen Kitt
2 hours ago

Given the timestamps in the logs, I take it the unit fails to start at boot, is that right? What happens if you restart it afterwards? You might need to trigger the unit from a udev rule so that it starts after the hwnrg device is available.
â€“Â Stephen Kitt
2 hours ago

M. Kitt may also be interested in the status of dev-hwrng.device.
â€“Â JdeBP
2 hours ago

@JdeBP thatÃ¢Â€Â™s assuming that the udev rule tags the device appropriately; but weÃ¢Â€Â™re addressing the parent question at this point...
â€“Â Stephen Kitt
2 hours ago

Â |Â
show 4 more comments

up vote
3
down vote

accepted

Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

If both an init script and a unit file are present, systemd will use the latter (at least, when the service isnÃ¢Â€Â™t running).

Ã¢Â—Â infnoise.service - Wayward Geek InfNoise TRNG driver
 Loaded: loaded (/lib/systemd/system/infnoise.service; enabled; vendor preset: enabled)

HereÃ¢Â€Â™s a service which only has an init script:

Ã¢Â—Â sensord.service - LSB: lm-sensors daemon
 Loaded: loaded (/etc/init.d/sensord; generated; vendor preset: enabled)

Checking your service should show that systemd is using your new unit.

edited 2 hours ago

answered 3 hours ago

Stephen Kitt

150k23333401

Thanks @Stephen. OK, so I removed the changes to rc.local that manually enabled rng-tools, and I left the new rng-tools.service in place. Unfortunately no joy. The service did not start and /dev/random is out of entropy. But it does look like the new service was used. It is amazing /usr/sbin/rngd -r /dev/hwrng -f works from rc.local but not rng-tools.service.
â€“Â jww
2 hours ago

What does systemctl status show after trying to start the service? Could it be that /dev/hwrng isnÃ¢Â€Â™t available early enough?
â€“Â Stephen Kitt
2 hours ago

Given the timestamps in the logs, I take it the unit fails to start at boot, is that right? What happens if you restart it afterwards? You might need to trigger the unit from a udev rule so that it starts after the hwnrg device is available.
â€“Â Stephen Kitt
2 hours ago

M. Kitt may also be interested in the status of dev-hwrng.device.
â€“Â JdeBP
2 hours ago

@JdeBP thatÃ¢Â€Â™s assuming that the udev rule tags the device appropriately; but weÃ¢Â€Â™re addressing the parent question at this point...
â€“Â Stephen Kitt
2 hours ago

Â |Â
show 4 more comments

up vote
3
down vote

accepted

Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

If both an init script and a unit file are present, systemd will use the latter (at least, when the service isnÃ¢Â€Â™t running).

Ã¢Â—Â infnoise.service - Wayward Geek InfNoise TRNG driver
 Loaded: loaded (/lib/systemd/system/infnoise.service; enabled; vendor preset: enabled)

HereÃ¢Â€Â™s a service which only has an init script:

Ã¢Â—Â sensord.service - LSB: lm-sensors daemon
 Loaded: loaded (/etc/init.d/sensord; generated; vendor preset: enabled)

Checking your service should show that systemd is using your new unit.

edited 2 hours ago

answered 3 hours ago

Stephen Kitt

150k23333401

Synchronizing state of rng-tools.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable rng-tools

If both an init script and a unit file are present, systemd will use the latter (at least, when the service isnÃ¢Â€Â™t running).

Ã¢Â—Â infnoise.service - Wayward Geek InfNoise TRNG driver
 Loaded: loaded (/lib/systemd/system/infnoise.service; enabled; vendor preset: enabled)

HereÃ¢Â€Â™s a service which only has an init script:

Ã¢Â—Â sensord.service - LSB: lm-sensors daemon
 Loaded: loaded (/etc/init.d/sensord; generated; vendor preset: enabled)

Checking your service should show that systemd is using your new unit.

edited 2 hours ago

answered 3 hours ago

Stephen Kitt

150k23333401

edited 2 hours ago

answered 3 hours ago

Stephen Kitt

150k23333401

answered 3 hours ago

Stephen Kitt

150k23333401

answered 3 hours ago

Stephen Kitt

150k23333401

Thanks @Stephen. OK, so I removed the changes to rc.local that manually enabled rng-tools, and I left the new rng-tools.service in place. Unfortunately no joy. The service did not start and /dev/random is out of entropy. But it does look like the new service was used. It is amazing /usr/sbin/rngd -r /dev/hwrng -f works from rc.local but not rng-tools.service.
â€“Â jww
2 hours ago

What does systemctl status show after trying to start the service? Could it be that /dev/hwrng isnÃ¢Â€Â™t available early enough?
â€“Â Stephen Kitt
2 hours ago

Given the timestamps in the logs, I take it the unit fails to start at boot, is that right? What happens if you restart it afterwards? You might need to trigger the unit from a udev rule so that it starts after the hwnrg device is available.
â€“Â Stephen Kitt
2 hours ago

M. Kitt may also be interested in the status of dev-hwrng.device.
â€“Â JdeBP
2 hours ago

@JdeBP thatÃ¢Â€Â™s assuming that the udev rule tags the device appropriately; but weÃ¢Â€Â™re addressing the parent question at this point...
â€“Â Stephen Kitt
2 hours ago

Â |Â
show 4 more comments

Thanks @Stephen. OK, so I removed the changes to rc.local that manually enabled rng-tools, and I left the new rng-tools.service in place. Unfortunately no joy. The service did not start and /dev/random is out of entropy. But it does look like the new service was used. It is amazing /usr/sbin/rngd -r /dev/hwrng -f works from rc.local but not rng-tools.service.
â€“Â jww
2 hours ago

What does systemctl status show after trying to start the service? Could it be that /dev/hwrng isnÃ¢Â€Â™t available early enough?
â€“Â Stephen Kitt
2 hours ago

Given the timestamps in the logs, I take it the unit fails to start at boot, is that right? What happens if you restart it afterwards? You might need to trigger the unit from a udev rule so that it starts after the hwnrg device is available.
â€“Â Stephen Kitt
2 hours ago

M. Kitt may also be interested in the status of dev-hwrng.device.
â€“Â JdeBP
2 hours ago

@JdeBP thatÃ¢Â€Â™s assuming that the udev rule tags the device appropriately; but weÃ¢Â€Â™re addressing the parent question at this point...
â€“Â Stephen Kitt
2 hours ago

Thanks @Stephen. OK, so I removed the changes to rc.local that manually enabled rng-tools, and I left the new rng-tools.service in place. Unfortunately no joy. The service did not start and /dev/random is out of entropy. But it does look like the new service was used. It is amazing /usr/sbin/rngd -r /dev/hwrng -f works from rc.local but not rng-tools.service.
â€“Â jww
2 hours ago

What does systemctl status show after trying to start the service? Could it be that /dev/hwrng isnÃ¢Â€Â™t available early enough?
â€“Â Stephen Kitt
2 hours ago

Given the timestamps in the logs, I take it the unit fails to start at boot, is that right? What happens if you restart it afterwards? You might need to trigger the unit from a udev rule so that it starts after the hwnrg device is available.
â€“Â Stephen Kitt
2 hours ago

M. Kitt may also be interested in the status of dev-hwrng.device.
â€“Â JdeBP
2 hours ago

@JdeBP thatÃ¢Â€Â™s assuming that the udev rule tags the device appropriately; but weÃ¢Â€Â™re addressing the parent question at this point...
â€“Â Stephen Kitt
2 hours ago

Â |Â
show 4 more comments

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

Search This Blog

Iyfjky