I learned much today...
Thank you for your time, as well the problem is not fixed, you have really
helped me.
good night
Angelo
On Sun, Jan 7, 2018 at 10:02 PM, wrote:
>
> On Sun, 07 Jan 2018 21:37:51 +0200 Angelo Moreschini wrote:
>
> > So you say : the
On Sun, 07 Jan 2018 21:37:51 +0200 Angelo Moreschini wrote:
> So you say : the directory exist.. although I cannot see them ?
> this look to be not much clear (but really you are right :-). )...
That's the way autofs works for such an indirect map by default. This
may ne changed: see man
the *umount failed ..*. :
[angelo_dev@localhost ~]$ sudo umount /srv/BKx_data-personal
umount: /srv/BKx_data-personal: mountpoint not found
[angelo_dev@localhost ~]$ sudo umount /srv/BKx_programming
umount: /srv/BKx_programming: mountpoint not found
[angelo_dev@localhost ~]$
OK ... I understand... ...
So you say : the directory exist.. although I cannot see them ?
this look to be not much clear (but really you are right :-). )...
-- here the output you asked :
[angelo_dev@localhost ~]$ sudo *journalctl --since 19:57:00 -u
autofs.service*
-- Logs begin
On Sun, 7 Jan 2018 20:44:57 +0200
Angelo Moreschini wrote:
> wait ... I checked better and I saw the directories doesn't exits in
> /srv...
>
> trying to create now but I didn't have success.. :
>
> [angelo_dev@localhost srv]$ sudo mkdir BKx_programming
>
>
>
On Sun, 07 Jan 2018 20:52:39 +0200 Angelo Moreschini wrote:
> perhaps the /srv directory is a special one ? Also administrator cannot
> make directory inside it ?
Yes and no: it is a mountpoint directory managed exclusively by autofs
(since with ssetup auto.master for that).
This is normal to
we have to use another directory than /srv .
The directories for mounting partitions weren't created there ...,and look
it is not possible to create there ...
On Sun, Jan 7, 2018 at 8:52 PM, Angelo Moreschini wrote:
> perhaps the /srv directory is a special one ?
perhaps the /srv directory is a special one ? Also administrator cannot
make directory inside it ?
On Sun, Jan 7, 2018 at 8:44 PM, Angelo Moreschini wrote:
> wait ... I checked better and I saw the directories doesn't exits in
> /srv...
>
> trying to create now but
wait ... I checked better and I saw the directories doesn't exits in
/srv...
trying to create now but I didn't have success.. :
[angelo_dev@localhost srv]$ sudo mkdir BKx_programming
*mkdir: cannot create directory ‘BKx_programming’: Permission denied*
that is funny ... How it can be ? I
On Sun, 07 Jan 2018 20:01:18 +0200 Angelo Moreschini wrote:
> I set OPTIONS="-v" in /etc/sysconfig/autofs:
> I restart the autofs service
> and after tried again to look for the mounted partition:
> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> ls: cannot access /srv/BKx_programming: *No
On Sun, 7 Jan 2018 17:58:07 +0200
Angelo Moreschini wrote:
> Hi Francis,
>
> I followed your procedure,
>
> 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
I didn't removed the directories in /media..
but *surly no one row about the mounting of the partition is now in fstab.*
On Sun, Jan 7, 2018 at 8:09 PM, Angelo Moreschini wrote:
> reading the documentation, I remember that I red that are some rules to
> write the
reading the documentation, I remember that I red that are some rules to
write the auto.xxx files
(like terminate the rows with "at the head" (crl)) but I didn't pay so much
attention and now don't remember these exactly.
Perhaps the problem is there ?
On Sun, Jan 7, 2018 at 8:01 PM, Angelo
I set OPTIONS="-v" in /etc/sysconfig/autofs:
I restart the autofs service
and after tried again to look for the mounted partition:
[angelo_dev@localhost ~]$ ls /srv/BKx_programming
ls: cannot access /srv/BKx_programming: *No such file or directory*
* still noting to do *
*also the
On Sun, 07 Jan 2018 18:38:31 +0200 Angelo Moreschini wrote:
> == 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
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
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
Hi Francis,
I followed your procedure,
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*
(the output about
On Sun, 07 Jan 2018 13:07:11 +0200 Angelo Moreschini wrote:
> Strangely I had several difficult to try autofs ..
This is not as simple as /etc/fstab.
> Now I that I went more in depth,I can understand that autofs is made mainly
> to be used in a net environment (NFS - file systems used in
Hi Francis,
before to begin, I would like talk with you a moment...
Strangely I had several difficult to try autofs ..
Now I that I went more in depth,I can understand that autofs is made mainly
to be used in a net environment (NFS - file systems used in networks).
The purpose because I wont
On Sun, 07 Jan 2018 12:16:34 +0200 Angelo Moreschini wrote:
> I understood (now) from where the error came :
> in auto.master file I forgot to put in comment this line :
> <+auto.master>
> Do you know what means it ? (what is the purpose of the sign "+" ?).
Search using nsswitch.conf a map
I understood (now) from where the error came :
in auto.master file I forgot to put in comment this line :
<+auto.master>
Do you know what means it ? (what is the purpose of the sign "+" ?).
Now I''l try your suggestion : ..
On Sun, Jan 7, 2018 at 11:58 AM,
On Sun, 07 Jan 2018 11:43:37 +0200 Angelo Moreschini wrote:
> I understand what you say Francis, perhaps you are right, and I'll try your
> suggestion.
Ok.
> But first of all I would like fix the basic problem (that the service
> doesn't correctly).
You mean I think the autofs service.
If I
I understand what you say Francis, perhaps you are right, and I'll try your
suggestion.
But first of all I would like fix the basic problem (that the service
doesn't correctly).
All the tray that I can do before to solve this, could be affected from
this "original sin"...
It is not so much
Hi.
On Wed, 27 Dec 2017 11:24:06 +0200 Angelo Moreschini wrote:
...
> The mounting of the partitions for the back up on the USB HD is made
> permantly at boot of the computer (the name of the backup-partitions is
> wrote in the file / etc / fstab) :
> UUID=376214F24CC07CE0
Really, (after many tests) I cannot understand what the problem can be...
I disabled all auto mounting functions putting in comment all the rows of
the file auto.master
and after I checked the service autofs :
=
[angelo_dev@localhost ~]$ sudo systemctl status
On Sat, 6 Jan 2018 10:50:14 -0800
Joe Zeff wrote:
> On 01/06/2018 09:40 AM, stan wrote:
> > I haven't done this, but from the article it seems that you have
> > either an entry in fstab and use mount -a to mount the drive after
> > plugging it in, or you follow the udev - autofs
On 01/06/2018 09:40 AM, stan wrote:
I haven't done this, but from the article it seems that you have either
an entry in fstab and use mount -a to mount the drive after plugging it
in, or you follow the udev - autofs route without an entry in fstab.
mount -a will mount everything in fstab. Is
On Sat, 6 Jan 2018 12:30:33 +0200
Angelo Moreschini wrote:
> I have problem to configure autofs, in order to use the partitions
> that I made on my USB HD - for backing up the data of the computer.
>
> --
> *(I am thinking that, perhaps, the names to indicate
I have problem to configure autofs, in order to use the partitions that I
made on my USB HD - for backing up the data of the computer.
--
*(I am thinking that, perhaps, the names to indicate the "mounting point"
and the "automounter map" are not the same that are used in sftab file ).*
On 01/05/2018 12:37 AM, Samuel Sieb wrote:
On 01/05/2018 12:13 AM, Angelo Moreschini wrote:
Nov 12 11:02:54 localhost.pluto ntfs-3g[691]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 12 19:59:58 localhost.pluto ntfs-3g[691]: Unmounting /dev/sdb2
(PRTZ_programming)
I
On 01/05/2018 12:13 AM, Angelo Moreschini wrote:
_here some line of command_ : _sudo journalctl | grep -i
PRTZ_programming_*(PRTZ_programming = name of partition I made on USB HD)**
*
Nov 12 09:29:50 localhost.pluto gnome-session[1798]: Gjs-Message: JS
LOG: Unable to mount volume
*other lines of journalctl that report errors *
Jan 01 12:38:12 localhost.pluto org.gtk.Private.UDisks2VolumeMonitor[2153]:
index_parse.c:191: indx_parse(): *error* opening
/run/media/angelo_dev/PRTZ_programming/BDMV/BACKUP/index.bdmv
Jan 01 13:00:02 localhost.pluto ntfs-3g[7860]: Unmounting
Hi Samuel,
if I use fstab to *mount permanently* some partitions that I made on a USB
Hard Disk, *THEN, every time* I use the "find" command, I get (from
nautilus) requests to open (show) these partitions.
And this is not only an (very much) annoying problem..
In that eventuality I also begin
On 12/27/2017 01:24 AM, Angelo Moreschini wrote:
However, this solution for backing up the data is problematic, because
_I always receive messages with the request of access to the partitions
__of the “backup-partitions”__by "nautilus"_ - every time that I use the
"find" command.
I don't
On Sat, 30 Dec 2017 19:26:01 +0200
Angelo Moreschini wrote:
> thank you Bob,
>
> I wont try your suggestion, but I have not installed autoff on Fedora 21 :
> --
> [angelo_dev@localhost ~]$ sudo systemctl status autofs.service
> [sudo] password for angelo_dev:
> ●
thank you Bob,
I wont try your suggestion, but I have not installed autoff on Fedora 21 :
--
[angelo_dev@localhost ~]$ sudo systemctl status autofs.service
[sudo] password for angelo_dev:
● autofs.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
On Wed, 27 Dec 2017 11:24:06 +0200
Angelo Moreschini wrote:
> hi,
>
>
> in order to backing up of the data , I wrote a script that uses the rsync
> command.
>
> This script have to be launched manually, and the data are saved on a USB
> Hard Disk, which (obviously)
38 matches
Mail list logo