of curse I changed ... :
====== auto.master -
/srv/ /etc/auto.ext-usb --timeout=10,defaults
====== auto.ext-usb
BKx_programming -fstype=ntfs :/dev/disk/by-uuid/479F99A324FF4D1D
BKx_data-common -fstype=ntfs :/dev/disk/by-uuid/EA8266EA8266BB29
===========
===========
*no output in journalctl :*
[angelo_dev@localhost ~]$* journalctl --since 17:36:00 -u autofs.service*
-- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
18:29:19 IST. --
-------
*this is the output for : <journalctl | grep -i BKx_programming> (the fes
last rows)*
*Jan 05 07:46:15* localhost.pluto gnome-session[1840]: Gjs-Message: JS LOG:
Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error mounting
system-managed device /dev/sdb2: Command-line `mount
"/media/BKx_programming"' exited with non-zero exit status 18: Failed to
write lock '/dev/sdb2': Resource temporarily unavailable
*Jan 05 07:46:18* localhost.pluto gnome-session[1840]: Gjs-Message: JS LOG:
Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error mounting
system-managed device /dev/sdb2: Command-line `mount
"/media/BKx_programming"' exited with non-zero exit status 18: Failed to
write lock '/dev/sdb2': Resource temporarily unavailable
*Jan 05 07:46:19* localhost.pluto
org.gtk.Private.UDisks2VolumeMonitor[1848]: index_parse.c:191:
indx_parse(): error opening /media/BKx_programming/BDMV/index.bdmv
*Jan 05 07:46:19* localhost.pluto
org.gtk.Private.UDisks2VolumeMonitor[1848]: index_parse.c:191:
indx_parse(): error opening /media/BKx_programming/BDMV/BACKUP/index.bdmv
On Sun, Jan 7, 2018 at 6:19 PM, <Francis.Montagnac(a)inria.fr> wrote:
On Sun, 07 Jan 2018 17:58:07 +0200 Angelo Moreschini wrote:
> I can see the partitions by nautilus as is the standard, but still I
cannot
> see them from the command line ..:
> ====
> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> ls: cannot access /srv/BKx_programming: *No such file or directory*
> ====
In my example I had only setup the automount of BKx_data-personal.
Have you completed it to automount the 3 partitions?
What gives:
ls /srv/BKx_data-personal
> (the output about the service is :)
> -----------
> [angelo_dev@localhost ~]$ sudo systemctl status autofs
> [sudo] password for angelo_dev:
> * autofs.service - Automounts filesystems on demand
> Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
> Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min ago
What gives (as an attachement):
journalctl --since 17:36:00 -u autofs.service
> Perhaps the right procedure (in the case of an USB device) is really to
use
> the node file in /dev directory how is wrote in the article ?
I don't think so: we do the same with /dev/disk/by-uuid/xxx
--
francis
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org