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.
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.
When you manually mount a file system that is neither listed in /etc/fstab nor known to the system, systemd automatically detects this action and generates a transient (temporary) mount unit. This means that systemd starts monitoring the manually mounted file system and keeps track of it, ensuring that it knows about its existence and can react to events related to it. However, this does not involve making any persistent changes to the configuration.
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.
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 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
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.
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.
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.
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.
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."
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."
The answer is B but it what happens is that it must be badly transcribed, something must be missing.
First execute systemctl mount
After execute sync to sincronize.
Sorry. Definitely, the answer is C.
Command systemctl mountsync not exist. As formulated, the answer is not correct.
If the command is executed separately (systemctl mount and after sync, in other line) will be valid.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
benjmcy
Highly Voted 4 years, 6 months agoilputto
Highly Voted 4 years, 1 month agoadriencr
Most Recent 2 months, 1 week agoBlindspot205
2 months, 1 week agotoannd
2 months, 1 week agogvozdik
2 months, 1 week agoFoelixxx
9 months, 3 weeks agoslacked4222
1 year agoAdamCzepiel
2 years, 1 month agopodm
2 years, 2 months agopodm
2 years, 1 month agoerikseals
2 years, 5 months agoLazylinux
2 years, 7 months agoLazylinux
2 years, 7 months agok3n_
2 years, 5 months agogonzaloco
2 years, 7 months agoMaikyCR28
2 years, 8 months agoanhcq
3 years agoanhcq
3 years agoEMordenti
3 years agoEMordenti
3 years ago