On Tue, Jul 7, 2020 at 11:40 AM Per Jessen <per@computer.org> wrote:
Roger Oberholtzer wrote:
On Tue, Jul 7, 2020 at 11:04 AM Per Jessen <per@computer.org> wrote:
It sounds like you do need to make your clients aware of the mount-status.
Using automount actually solves this. If the directory can be mounted, you can access it. Otherwise you get an error when trying to access it.
Really ? is that with systemd automount or the "oldfashioned" automount daemon ?
They are the same. All systemd does is set up automount via whatever you put in /etc/fstab. I use the systemd method. It works extremely well for me. In our measurement systems, we sometimes use removable disks (SATA in a drive bay) where the operator can choose to collect data. Prior to using automount, if the operator forgot to put in a disk, he would unknowingly collect data to the directory on which it should have been mounted. With automount, accessing that directory fails if the disk is not inserted. Problem solved. Since we use systemd, we have service files that act on when the drives are mounted. We can ensure mount point permissions or do whatever we want automatically when they are mounted. It works very well once you figure out the way systems thinks. In the current example, we use systemd to manage exporting and unexporting the disks as they are mounted and unmounted. I just wish we had better knowledge of some aspects of systemd so that we could be better at defining our service. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org