The monitor supports utab only (as documented). It's application
responsibility to use libmount in the right way. It's overkill to
check for valid environment during monitor initialization.
For example systemd checks for regular mtab during boot, it's better
than try to be smart later in libmount monitor when system is already
running.
Signed-off-by: Karel Zak <kzak@redhat.com>
assert(me->path);
/*
- * libmount uses rename(2) to atomically update utab/mtab, monitor
+ * libmount uses rename(2) to atomically update utab, monitor
* rename changes is too tricky. It seems better to monitor utab
* lockfile close.
*/
DBG(MONITOR, ul_debugobj(mn, "allocate new userspace monitor"));
- /* create a new entry */
- if (mnt_has_regular_mtab(NULL, NULL))
- return -ENOSYS;
-
if (!filename)
filename = mnt_get_utab_path(); /* /run/mount/utab */
if (!filename) {