Timeline for Start a systemd service after a device has been mounted
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2016 at 16:05 | comment | added | Run CMD |
@Auspex I also don't think it's relevant when noauto is used. It's just that the OP's use case suggests that he's not going to use noauto. That's got nothing to do with the documentation, but rather with the scenario of the question.
|
|
| Jul 13, 2016 at 10:52 | comment | added | Auspex | I don't think it's relevant whether "noauto" would be used during boot. You argued with the accepted answer because you claimed it was not the preferred systemd way. I see nothing in the documentation to say that, and reasons why you might want to avoid your method. | |
| Jul 12, 2016 at 18:03 | comment | added | Run CMD |
@Auspex The OP clearly stated that the question relates to system boot. In this regard, the title of the Q may be seen as incomplete, while my answer addressed this scenario. Do you see a case where a noauto option would be used during boot?
|
|
| Jul 9, 2016 at 20:53 | comment | added | Auspex |
I'd disagree with your comment above that "this is not the preferred systemd way". RequiresMountsFor= is ignored if the mount point is marked noauto, so sometimes the explicit Requires target is not only recommended but required.
|
|
| Nov 9, 2015 at 12:55 | history | answered | Run CMD | CC BY-SA 3.0 |