#1 Better respect the LSB standard for boot-facilities.
Opened 10 years ago by bochecha. Modified 4 years ago

The LSB standard lists the $remote_fs and $local_fs facilities:
http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/facilname.html

However, oddjobd is now using $localfs and $remotefs. Which means the boot requirement might not always be fullfilled.

This is especially a problem with systemd as systemd parses those scripts and adds the appropriate After= values to the oddjobd.service virtual unit, and it will then try to load the localfs.target and remotefs.target units instead of local-fs.target and remote-fs.target

When running systemctl --all, the admin will see two units that failed to load because the unit file doesn't exist, and will spend a full day wondering what happens (true story :).

The attached patch fixes that, using the proper LSB standard facility names.


Replying to [ticket:1 bochecha]:

This is especially a problem with systemd as systemd parses those scripts and adds the appropriate After= values to the oddjobd.service virtual unit, and it will then try to load the localfs.target and remotefs.target units instead of local-fs.target and remote-fs.target

When running systemctl --all, the admin will see two units that failed to load because the unit file doesn't exist, and will spend a full day wondering what happens (true story :).

It also means that oddjob doesn't get the proper After=, and as a result, if systemd is the init system, oddjob might start before local-fs.target and remote-fs.target are available.

To make the point as clear as possible, those dependencies might not work with sysvinit, and they do not work with systemd.

Login to comment on this ticket.

Metadata