![]() ![]() ![]() (See above.) It is recommended that the unit name that is activated and the unit name of the path unit are named identical, except for the suffix. If not specified, this value defaults to a service that has the same name as the path unit, except for the suffix. The argument is a unit name, whose suffix is not ".path". The unit to activate when any of the configured paths changes. (See above.) It is recommended that the unit name that is activated and the unit name of the timer unit are named identically, except for the suffix. If not specified, this value defaults to a service that has the same name as the timer unit, except for the suffix. The argument is a unit name, whose suffix is not ".timer". The unit to activate when this timer elapses. So, the more specific questions are (a) whether the path unit knows to simply propagate the mount units as instructed, leaving the mount units to mount the shares, or gets confused and can only propate a single mount unit or (b) whether calling the same path unit twice in fstab creates conflicts or errors when the path unit has many Unit= directives (i.e., by re-creating all the mount points specified) or simply is an expression of a dependency. The mounts are of shares on the virtual machine and are defined in the host's fstab entries, each of which uses the x-systemd.requires= mount option to specify the path unit, so that the mounts don't occur until the virtual machine is running. In particular, the path unit monitors a virtual machine's log file, which is quiet until the VM runs. The specific application is to have a path unit activate two mount units. Can multiple instances of Unit= exist in a systemd.path or systemd.timer unit? Or, must one instead specify multiple instances of the path or timer unit, each with a single instance of Unit=? I haven't been able to find or derive any guidance elsewhere. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |