Which of the following is true when a file system, which is neither listed in /etc/fstab nor known to system, is mounted manually?
Which of the following is true when a file system, which is neither listed in /etc/fstab nor known to system, is mounted manually?
When a file system that is not listed in /etc/fstab nor known to the system is manually mounted, systemd automatically generates a mount unit and monitors the mount point without altering it. This behavior ensures that the manually mounted file system is recognized and managed by systemd, similar to other mount points that are defined through unit files or /etc/fstab. Other options are incorrect as they either propose non-existent commands or misinterpret systemd’s role in mount point management.
I think the answer is C. systemd mount unit is created and located at /proc/self/mountinfo once you mount a hotplug device manually.
It's A!
According to systemd.mount man page: "Mount points created at runtime (independently of unit files or /etc/fstab) will be monitored by systemd and appear like any other mount unit in systemd."
For me is C
I tested it with manual mounting a ext4 Partition in /mnt/sdbext3. After systemctl list-units -type mount the mnt-sdbext3.mount apeared. So Unit was automatically created. Answer C is correct
This took me several days. The correct answer is D. Why? A. It's not mandatory to use the "systemctl mount" to mount manual mount points. B. The command "systemctl mountsync" doesn't exist. (https://man7.org/linux/man-pages/man1/systemctl.1.html) C. "systemd automatically generates a mount unit and monitors the mount" yes, but it also says "without changing it", and when a mount point is mounted manually without list it on /etc/fstab the mount unit will be unmounted every boot time, or even, on each period of time D. If you don't announce the mount pint in /etc/fstab, the only way to have a correct mount point is by creating it with the systems mount (https://oguya.ch/posts/2015-09-01-systemd-mount-partition/). Finally we can set a cron that start the mount unit every boot time, which, it can not be possible whit the option C without creating an entry on the /etc/fstab file. E. And finally the "E" answer all we know doesn't make sense.
This had done my head and can see from others comments too...i was gunned for C but after reading the LPIC guide page 486-502 there was nothing to support answer C and it was clear that systemd doe NOT automatically create mount points system unit i.e. mount unit needs be created frst and auto-mount unit only then systemd manages the mount point automatically and hence C is NOT the answer..from the discussion in the link iam providing it seems to be D which i though from the first place i.e. i was 50-50 between C and D but now im sure it is D and if comes in exam i will gun for D, read all discussion in the link and you will see this comment quite often from varies users in different situations
***adding further comments because limit on text*** I'm experiencing more diffulties with 'mount' failing silently. Below is a transcript of two examples of this. In the first case, it seems from 'journalctl' that the kernel is mounting the device, but Systemd is (silently, to the user) unmounting it. Unlike with my original example, systemctl daemon-reload does not fix the problem. https://github.com/systemd/systemd/issues/1741 Feel free to comments further but please back it up with facts!!
After some tests i realized that systemd don't unmount the unit after short period of time, unless the system is reboot. However, D. seems more ok than C.
Efectivamente y comprobado, si se monta una nueva partición, systemd automáticamente crea una nueva unit que monitoriza este nuevo punto de montaje. Por lo tanto la respuesta correcta creo que es la C
I think the answer should be C. According to systemd.mount man page: "Mount points created at runtime (independently of unit files or /etc/fstab) will be monitored by systemd and appear like any other mount unit in systemd."
Answer C is true.
B. The command systemctl mountsync can be used to create a mount unit based on the existing mount
Correct answer A. I consulted with my Linux trainer. Systemd can mount disks. But the systemd will not mount disks unless it is directly ordered to do so. In the fstab file or by creating a unit.
Sorry, Correct answer C.
C. systemd automatically generates a mount unit and monitors the mount point without changing it Lorsqu'un système de fichiers est monté manuellement (sans être défini dans /etc/fstab et sans utiliser une unité de montage systemd spécifique), systemd génère automatiquement une unité de montage temporaire pour suivre ce point de montage. Il ne modifie pas le point de montage, mais il le surveille, ce qui permet au reste du système de réagir en conséquence si nécessaire. Les autres options énumérées ne décrivent pas correctement le comportement standard de systemd avec les montages manuels.
Gpt and bard say D
D. Unless a systemd mount unit is created, systemd unmounts the file system after a short period of time. This statement is not accurate. systemd doesn't automatically unmount a file system just because a systemd mount unit is not created. When a file system is mounted manually, systemd does not have a specific timeout for unmounting it. The file system will remain mounted until explicitly unmounted using the umount command or a similar method. Therefore, option D is not a behavior associated with systemd when a file system is mounted manually. The more accurate representation is option C, where systemd automatically generates a mount unit and monitors the mount point without actively unmounting it.
Systemd doesn't do anything automatically. It work only if you add a mount unit or edit fstab file. I'm not sure something like that can come into exam.
I can confirm, that the answer is not D. Passed the exam today with nearly perfect result and had only one mistake, after I've chosen D in this question. I'm quite sure the mistake was in this question, since this was the only question in this category I had trouble with and the score report tells me, that I did a mistake in exact this category (devices and Linux filesystems). So the correct answer is probably C.