Broken links return immediately and don't hang. on Production systems
the symlink to /mnt/nfsfs from wherever it needs to look like it is at
correctly allows pwd to work when the filesystem it is pointing at is
not responding.
On Sun, Dec 8, 2019 at 2:31 PM Patrick Dupre wrote:
>
> Thank for the
Thank for the suggestion.
Actually, I did the ssh mount in /mnt which avoids the mentioned issue.
However, I am reluctant to put a symbolic link on this directory, because
a ln on a "broken" link will probably generate the same issue.
>
> Hi.
>
> On Thu, 28 Nov 2019 12:27:53 +0100 "Patrick Dupre
Hi.
On Thu, 28 Nov 2019 12:27:53 +0100 "Patrick Dupre" wrote:
> To reproduce the bug (fedora 30)
> 1) Create a sshfs on a remote machine from your home directory
> (sshfs user@machine:/home/dir ~/SSHFS)
Using a subdir of your homedir as a network mountpoint if risky.
Roger Heflin indicated t
On 2019-11-28 22:39, Patrick Dupre wrote:
> Yes, probably, but if the network is never back correctly (time out, or
> "bad" network), then, it never recovers.
FWIW, I locked the screen and disconnected the network at 01:52. Then at 06:01
I reconnected
the network. I then was able to unlock the
> Sent: Thursday, November 28, 2019 at 3:25 PM
> From: "Ed Greshko"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome frozen when ssfhs stall
>
> On 2019-11-28 22:00, Patrick Dupre wrote:
> > But, just try to login when the cable is off.
> > If you
On 2019-11-28 22:00, Patrick Dupre wrote:
> But, just try to login when the cable is off.
> If you have a network of good quality, when you replug the cable
> to recover the connection easily.
> With a DSL connection, the network stalls periodically, and then does not
> recover.
I locked the scree
ent: Thursday, November 28, 2019 at 2:54 PM
> From: "Ed Greshko"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome frozen when ssfhs stall
>
> On 2019-11-28 21:24, Patrick Dupre wrote:
> > I made a mistake, in point 4). to be sure that is "work", you n
On 2019-11-28 21:24, Patrick Dupre wrote:
> I made a mistake, in point 4). to be sure that is "work", you need to have
> the
> connection stalled. If you reconnect to early, the connection can be
> re-established.
>
> Hence, probably that you did not wait enough. The connection did to not have
>
el: +33 (0)380395988
===
> Sent: Thursday, November 28, 2019 at 1:07 PM
> From: "Ed Greshko"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome frozen when ssfhs stall
>
> On 2019-11-28 19:27,
On 2019-11-28 19:27, Patrick Dupre wrote:
> To reproduce the bug (fedora 30)
> 1) Create a sshfs on a remote machine from your home directory (sshfs
> user@machine:/home/dir ~/SSHFS)
> 2) Lock the screen (I use gnome)
> 3) Unplug the internet cable of your machine for example (the connection
> st
Bug #
1731645
To reproduce the bug (fedora 30)
1) Create a sshfs on a remote machine from your home directory (sshfs
user@machine:/home/dir ~/SSHFS)
2) Lock the screen (I use gnome)
3) Unplug the internet cable of your machine for example (the connection stalls
pretty often with a ADSL connection
On 2019-11-27 17:00, Patrick Dupre wrote:
> I already complained about the following issue, and I submitted the bug to
> bugzilla
> without feedback.
> If I have an open gnome session which turns to sleep because of a lack of
> activity. Then, if a sshfs connection stalls, there is no way to relog
In general if critical filesystems quit responding then everything
using them will hang.
Is critical files on the filesystem that gnome would need? if it is
the home dir then it is critical.
An old trick with nfs was do not ever mount it directly on /, as the
pwd command works by checking all fi
Hello,
I already complained about the following issue, and I submitted the bug to
bugzilla
without feedback.
If I have an open gnome session which turns to sleep because of a lack of
activity. Then, if a sshfs connection stalls, there is no way to relogin
through the gnome-session.
The only opti
14 matches
Mail list logo
