On Tue, 2020-06-02 at 10:45 -0600, Greg Woods wrote: > On Tue, Jun 2, 2020 at 9:27 AM Patrick O'Callaghan <pocallaghan@xxxxxxxxx> > wrote: > > > > > (the only change is in the last two fields, where you had 1 1 rather > > than my 0 0, but it made no difference, not that I thought it would). I > > also did the daemon-reload thing just in case. > > > > I have found that if you change an fstab entry, after doing "systemctl > daemon-reload", you also may need to restart the automount service to get > the changes to take, e.g. "systemctl restart raid.automount". Whether this > is necessary may well depend on exactly which parameters you specify in > your fstab entry, but I have certainly seen cases where this is necessary. That gives me: $ sudo systemctl restart raid.automount Job failed. See "journalctl -xe" for details. and journalctl is not enlightening: -- Subject: A start job for unit raid.automount has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit raid.automount has finished with a failure. -- -- The job identifier is 9170 and the job result is failed. No idea what this means. Saying "it failed" three times is no substitute for an actual error message. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
