On 05/05/2017 01:55 AM, François Patte wrote: > Bonjour, > > 1--- I masked the firewalld service because I don't want to use it,. Il > the log messages, I get this information: > > irewalld.service: Cannot add dependency job > > How can I know what jobs depend on firewalld? You can ask systemctl: # systemctl -l --before list-dependencies firewalld.service > 2--- What is the meaning of this message: > > iscsi.service: Unit cannot be reloaded because it is inactive. You probably don't have any iSCSI devices so the iscsi.service went inactive or you have it disabled. Not uncommon and I wouldn't worry about it unless you plan to use iSCSI sometime in the future. > 3-- And always this message: > > var.mount: Directory /var to mount over is not empty > > Why does cups creates directories in /var before /var is mounted? Looking at the cups.service file, it doesn't have a after=local-fs.target specification, so it doesn't wait until local-fs.target has been launched before running. I guess the assumption is that most systems now use a single, monolithic filesystem with /var simply a directory of the root filesystem. IMHO that's a stupid assumption to make, but there's a lot of stuff I detest about systemd. I suppose you could edit /usr/lib/systemd/system/cups.service and add " local-fs.target" to the "[Unit]" section's "After=" line as shown below: [Unit] Description=CUPS Scheduler Documentation=man:cupsd(8) After=network.target local-fs.target [Service] ExecStart=/usr/sbin/cupsd -l Type=notify [Install] Also=cups.socket cups.path WantedBy=printer.target Then reboot and verify that cups waits for /var to be mounted before starting. You might also submit a bugzilla for this as I'm sure you're not the only one getting hit by this. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - grep me no patterns and I'll tell you no lines - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
