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
f the sshfs is in your homedir) must not be
> accomplished.
>
> In my opinion the same thing happen under gnome, frozen the login.
I just retested. I waited 5 minutes after disabling the NIC before enabling it
again.
No problem. I was able to unlock the screen and the mount was maintained.
I
ppen under gnome, frozen the login.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
T
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
> On 7/15/19 10:35 AM, Samuel Sieb wrote:
> > On 7/14/19 2:46 AM, Patrick Dupre wrote:
> >> OK, it works,
> >> 1) I have a sshfs connection to an external machine
> >> 2) I unplug the network
> >> 3) I lock the screen
> >> 4) I try to unclok the screen, but I cannot unlock
> >> 5) I log in a text t
On 7/15/19 10:35 AM, Samuel Sieb wrote:
> On 7/14/19 2:46 AM, Patrick Dupre wrote:
>> OK, it works,
>> 1) I have a sshfs connection to an external machine
>> 2) I unplug the network
>> 3) I lock the screen
>> 4) I try to unclok the screen, but I cannot unlock
>> 5) I log in a text terminal, and use
On 7/14/19 2:46 AM, Patrick Dupre wrote:
OK, it works,
1) I have a sshfs connection to an external machine
2) I unplug the network
3) I lock the screen
4) I try to unclok the screen, but I cannot unlock
5) I log in a text terminal, and use kill -HUP
6) I can unlock the screen
7) I replug the netw
>
> On 7/11/19 1:23 AM, Patrick Dupre wrote:
> > My interpretation is that gnome stuck only
> > gnome stuck when I try to leave the lock mode (no screensaver is activated)
> > and when the sshfs is stalled.
> >
> > What I cold try:
> > 1) stall the sshfs, how?
>
> Unplugging the network of the moun
On 7/11/19 1:23 AM, Patrick Dupre wrote:
My interpretation is that gnome stuck only
gnome stuck when I try to leave the lock mode (no screensaver is activated)
and when the sshfs is stalled.
What I cold try:
1) stall the sshfs, how?
Unplugging the network of the mounted system should do it. O
> On 7/10/19 2:28 PM, Patrick Dupre wrote:
> >> On 6/16/19 2:24 PM, Patrick Dupre wrote:
> >>> I though that it may be due to a mounted filesystem.
> >>> But it is not the case.
> >>
> >> You don't have any mounts that might become stale after an extended
> >> period of time?
> >
> > I noted that w
On 7/10/19 2:28 PM, Patrick Dupre wrote:
On 6/16/19 2:24 PM, Patrick Dupre wrote:
I though that it may be due to a mounted filesystem.
But it is not the case.
You don't have any mounts that might become stale after an extended
period of time?
I noted that when I make a sshfs to a machine thr
> On 7/10/19 2:07 PM, a...@clueserver.org wrote:
perl -pe 's/^\s+//g' *.py
>>> Am I supposed to run this command?
>>
>> That is a sig line joke. It removes leading white space from Python
>> programs. Don't run that.
>
> That is a very dangerous joke with no indication that it is your sig.
>
> On 6/16/19 2:24 PM, Patrick Dupre wrote:
> > Since I upgraded to fc30, if I do not use the PC for a while
> > the screen turns to lock (no screensaver is used).
> > Is this time is long, I may not be able to log in.
> > The screen remains frozen after I provide the password.
>
> Have you tried
On 7/10/19 2:07 PM, a...@clueserver.org wrote:
perl -pe 's/^\s+//g' *.py
Am I supposed to run this command?
That is a sig line joke. It removes leading white space from Python
programs. Don't run that.
That is a very dangerous joke with no indication that it is your sig.
Yes, I realize tha
On 7/10/19 1:50 PM, a...@clueserver.org wrote:
I have seen this happen before. If you have nvidia-settings installed, but
do not have the commercial nvidia driver running, nvidia-settings makes a
whole bunch of duplicate connections to the xserver. Once it is full, you
cannot open new windows. (T
On 6/16/19 2:24 PM, Patrick Dupre wrote:
Since I upgraded to fc30, if I do not use the PC for a while
the screen turns to lock (no screensaver is used).
Is this time is long, I may not be able to log in.
The screen remains frozen after I provide the password.
Have you tried disabling the screen
On 7/10/19 1:33 PM, Patrick Dupre wrote:
On 6/17/19 1:03 PM, Patrick Dupre wrote:
From: "Samuel Sieb"
Where are you entering this? From a console or ssh?
Yes
That wasn't intended to be a yes or no question. I assume from the
answer below that it's a terminal console.
Try using "kill -HU
>> I have seen this happen before. If you have nvidia-settings installed,
>> but
>> do not have the commercial nvidia driver running, nvidia-settings makes
>> a
>> whole bunch of duplicate connections to the xserver. Once it is full,
>> you
>> cannot open new windows. (Things get very strange.)
>
>
> >>
> >> On 6/17/19 1:03 PM, Patrick Dupre wrote:
> >> >> From: "Samuel Sieb"
> >> >> Where are you entering this? From a console or ssh?
> >> > Yes
> >>
> >> That wasn't intended to be a yes or no question. I assume from the
> >> answer below that it's a terminal console.
> >>
> >> >> Try u
>>
>> On 6/17/19 1:03 PM, Patrick Dupre wrote:
>> >> From: "Samuel Sieb"
>> >> Where are you entering this? From a console or ssh?
>> > Yes
>>
>> That wasn't intended to be a yes or no question. I assume from the
>> answer below that it's a terminal console.
>>
>> >> Try using "kill -HUP" on t
>
> On 6/17/19 1:03 PM, Patrick Dupre wrote:
> >> From: "Samuel Sieb"
> >> Where are you entering this? From a console or ssh?
> > Yes
>
> That wasn't intended to be a yes or no question. I assume from the
> answer below that it's a terminal console.
>
> >> Try using "kill -HUP" on the gnome-she
On 6/17/19 1:03 PM, Patrick Dupre wrote:
From: "Samuel Sieb"
Where are you entering this? From a console or ssh?
Yes
That wasn't intended to be a yes or no question. I assume from the
answer below that it's a terminal console.
Try using "kill -HUP" on the gnome-shell process.
From a t
===
> Sent: Monday, June 17, 2019 at 7:40 AM
> From: "Samuel Sieb"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome frozen
>
> On 6/16/19 2:24 PM, Patrick Dupre wrote:
> > Since I upgraded to
On 6/16/19 2:24 PM, Patrick Dupre wrote:
Since I upgraded to fc30, if I do not use the PC for a while
the screen turns to lock (no screensaver is used).
Is this time is long, I may not be able to log in.
The screen remains frozen after I provide the password.
The only way to get access to a graph
Hello,
Since I upgraded to fc30, if I do not use the PC for a while
the screen turns to lock (no screensaver is used).
Is this time is long, I may not be able to log in.
The screen remains frozen after I provide the password.
The only way to get access to a graphics mode is to run
kill -9 -1
I th
On 24 March 2013 10:42, Frank Murphy wrote:
> On Sun, 24 Mar 2013 10:36:21 +
> Ian Malone wrote:
>
>> [15523.867808] ata3: EH in SWNCQ mode,QC:qc_active 0x7 sactive 0x7
>> [15523.867822] ata3: SWNCQ:qc_active 0x1 defer_bits 0x6
>> last_issue_tag 0x0 dhfis 0x1 dmafis 0x1 sdbfis 0x0
>> [15523.8
On Sun, 24 Mar 2013 10:36:21 +
Ian Malone wrote:
> [15523.867808] ata3: EH in SWNCQ mode,QC:qc_active 0x7 sactive 0x7
> [15523.867822] ata3: SWNCQ:qc_active 0x1 defer_bits 0x6
> last_issue_tag 0x0 dhfis 0x1 dmafis 0x1 sdbfis 0x0
> [15523.867834] ata3: ATA_REG 0x40 ERR_REG 0x0
> [15523.867840]
On 24 March 2013 03:47, Richard Vickery wrote:
> On Fri, Mar 22, 2013 at 2:55 PM, Ian Malone wrote:
>>
>> On 22 March 2013 15:05, Patrick Dupre wrote:
>> > Hello,
>> >
>> > In average, once a day my gnome session freezes. Only one option,
>> > open a text session and try to kill the gnome-sessio
On Fri, Mar 22, 2013 at 2:55 PM, Ian Malone wrote:
> On 22 March 2013 15:05, Patrick Dupre wrote:
> > Hello,
> >
> > In average, once a day my gnome session freezes. Only one option,
> > open a text session and try to kill the gnome-session!
> >
> > Any idea how to debug this?
> >
>
> Run top an
On 22 March 2013 15:05, Patrick Dupre wrote:
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
>
Run top and see what's going on. Should help answer the 'not enough
resources' que
On Fri, Mar 22, 2013 at 11:27 AM, Patrick Dupre wrote:
> On 2013-03-22 17:15, Dale Dellutri wrote:
>>
>> On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre wrote:
>>>
>>> Hello,
>>>
>>> In average, once a day my gnome session freezes. Only one option,
>>> open a text session and try to kill the gnom
On 2013-03-22 17:15, Dale Dellutri wrote:
On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre
wrote:
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
If this is a limited resource problem,
On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre wrote:
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
If this is a limited resource problem, then you'll need to run something w
On Fri, 22 Mar 2013 16:56:06 +0100
Patrick Dupre wrote:
> Frozen means, the mouse works but every thing else is frozen: all the
> displays in the top panel,
> no way to graphically interact.
> Do way to move to another workspace. Fortunately Ctl F2 works.
> It usually happens when I change of wor
On 2013-03-22 16:36, Richard Vickery wrote:
On Mar 22, 2013 8:06 AM, "Patrick Dupre"
wrote:
>
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
>
> Thank.
>
> --
>
=
On Mar 22, 2013 8:06 AM, "Patrick Dupre" wrote:
>
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
>
> Thank.
>
> --
>
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
Thank.
--
==
Patrick DUPRÉ | | email: pdu...@kegtu
47 matches
Mail list logo
