On 11/1/18 6:38 AM, Ed Greshko wrote:
> On 11/1/18 5:44 AM, Stephen Morris wrote:
>> I removed the x-systemd.requires parameter as a test and issuing a ls
>> /mnt/nas *auto*
>> mounts the mount point. Why x-systemd.requires=/mnt/nfs interferes with
>> x-systemd.automount, even when /mnt/nfs has
On 11/1/18 5:44 AM, Stephen Morris wrote:
> I removed the x-systemd.requires parameter as a test and issuing a ls
> /mnt/nas *auto*
> mounts the mount point. Why x-systemd.requires=/mnt/nfs interferes with
> x-systemd.automount, even when /mnt/nfs has already been *auto* mounted, I
> don't know.
On 1/11/18 8:34 am, Stephen Morris wrote:
On 1/11/18 8:07 am, Ed Greshko wrote:
On 11/1/18 4:55 AM, Stephen Morris wrote:
bash-4.4$ mount /mnt/nas
Why are you using "mount"?
Just doing an ls or changing into the dir will *auto* mount. That's
the whole idea.
I was issuing the mount
On 1/11/18 8:07 am, Ed Greshko wrote:
On 11/1/18 4:55 AM, Stephen Morris wrote:
bash-4.4$ mount /mnt/nas
Why are you using "mount"?
Just doing an ls or changing into the dir will *auto* mount. That's the whole
idea.
I was issuing the mount command to show what happens in my case to see
On 11/1/18 4:55 AM, Stephen Morris wrote:
> bash-4.4$ mount /mnt/nas
Why are you using "mount"?
Just doing an ls or changing into the dir will *auto* mount. That's the whole
idea.
--
Fedora Users - The place to go to beat OT dead horses :-) :-)
___
On 31/10/18 9:32 am, Ed Greshko wrote:
On 10/31/18 5:36 AM, Stephen Morris wrote:
On 30/10/18 1:14 pm, Ed Greshko wrote:
On 10/30/18 6:57 AM, Ed Greshko wrote:
This test may not be valid in your environment. What O/S is running on the
server side?
FWIW, I have a Windows 10 VM that I've
On 10/31/18 5:36 AM, Stephen Morris wrote:
> On 30/10/18 1:14 pm, Ed Greshko wrote:
>> On 10/30/18 6:57 AM, Ed Greshko wrote:
>>> This test may not be valid in your environment. What O/S is running on the
>>> server side?
>> FWIW, I have a Windows 10 VM that I've resurrected. I shared a folder
On 30/10/18 1:14 pm, Ed Greshko wrote:
On 10/30/18 6:57 AM, Ed Greshko wrote:
This test may not be valid in your environment. What O/S is running on the
server side?
FWIW, I have a Windows 10 VM that I've resurrected. I shared a folder and used
the same
format entry in the fstab.
It
On 10/30/18 6:57 AM, Ed Greshko wrote:
> This test may not be valid in your environment. What O/S is running on the
> server side?
FWIW, I have a Windows 10 VM that I've resurrected. I shared a folder and used
the same
format entry in the fstab.
It mounts just fine on reboot. Having a bit
On 10/30/18 5:02 AM, Stephen Morris wrote:
> Sorry Ed, just one more question around this. You mentioned in an earlier
> thread that
> you had the auto-mount process working on a CIFS partition. How did you get
> it to work,
> I can't get it to. Both 'LS /MNT/NAS' and 'SUDO LS /MNT/NAS' fail to
On 27/10/18 6:15 pm, Ed Greshko wrote:
On 10/27/18 2:46 PM, Stephen Morris wrote:
My main concern with this is not the mounts failing at boot, I can understand
why they
failed, but more why the networkmanager wait online process is failing. I tried
a boot
with the ethernet cable disconnected
On 27/10/18 6:15 pm, Ed Greshko wrote:
On 10/27/18 2:46 PM, Stephen Morris wrote:
My main concern with this is not the mounts failing at boot, I can understand
why they
failed, but more why the networkmanager wait online process is failing. I tried
a boot
with the ethernet cable disconnected
On 10/27/18 2:46 PM, Stephen Morris wrote:
> My main concern with this is not the mounts failing at boot, I can understand
> why they
> failed, but more why the networkmanager wait online process is failing. I
> tried a boot
> with the ethernet cable disconnected from the pc, but that made no
On 25/10/18 8:58 am, Ed Greshko wrote:
On 10/25/18 5:42 AM, Stephen Morris wrote:
I may or may not be having the rc.local issue as I don't appear to have one.
You have to create it yourself.
I realised after I sent the email that might be the case, and then
cursed myself for being so
On 25/10/18 8:54 am, Ed Greshko wrote:
On 10/25/18 5:25 AM, Stephen Morris wrote:
I tried the x-systemd.automount parameter by adding it to the fstab entry and
then
trying 'ls /mnt/nfs' which doesn't automount the partition. Either the change
requires a
reboot to take effect (I've left it
FWIW
As I mentioned earlier, my fstab contains
ds6:/volume1/syntegra /syntegra nfs4 rw,soft,bg,x-systemd.automount 0 0
The ping time between the client and server is about 288 ms.
After reboot when I first connect to the client system...
[egreshko@acer ~]$ df
Filesystem
On 10/25/18 5:42 AM, Stephen Morris wrote:
> I may or may not be having the rc.local issue as I don't appear to have one.
You have to create it yourself.
See
/lib/systemd/system/rc-local.service for details.
FWIW, I used to use the method described by Tom but found it a pain to
On 10/25/18 5:25 AM, Stephen Morris wrote:
> I tried the x-systemd.automount parameter by adding it to the fstab entry and
> then
> trying 'ls /mnt/nfs' which doesn't automount the partition. Either the change
> requires a
> reboot to take effect (I've left it present to see what happens after
On 23/10/18 9:44 am, Tom Horsley wrote:
On Tue, 23 Oct 2018 08:06:28 +1100
Stephen Morris wrote:
My Nas Devices are failing to mount at boot time
I've never see any indication that the wait online
service works to achieve anything remotely useful.
There have been threads in this list with
On 23/10/18 9:17 am, Ed Greshko wrote:
On 10/23/18 5:57 AM, Stephen Morris wrote:
On 23/10/18 8:06 am, Stephen Morris wrote:
Hi,
My Nas Devices are failing to mount at boot time because the
Networkmanager Wait
Online Service is failing at boot time. The following is the output from
On Tue, 23 Oct 2018 08:06:28 +1100
Stephen Morris wrote:
> My Nas Devices are failing to mount at boot time
I've never see any indication that the wait online
service works to achieve anything remotely useful.
There have been threads in this list with huge
long analysis of exactly what isn't
On 10/23/18 5:57 AM, Stephen Morris wrote:
>
> On 23/10/18 8:06 am, Stephen Morris wrote:
>> Hi,
>>
>> My Nas Devices are failing to mount at boot time because the
>> Networkmanager Wait
>> Online Service is failing at boot time. The following is the output from
>> systemctl that
>> the boot
On 23/10/18 8:06 am, Stephen Morris wrote:
Hi,
My Nas Devices are failing to mount at boot time because the
Networkmanager Wait Online Service is failing at boot time. The
following is the output from systemctl that the boot process
recommends being run. Is there anything in that output
23 matches
Mail list logo
