From: Chris Brennan <xaero@xaerolimit.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sshfs issue
Date: Thu, 28 Feb 2008 17:43:09 -0500 [thread overview]
Message-ID: <47C738FD.3050109@xaerolimit.net> (raw)
In-Reply-To: <20080228235832.55afd551@cuci>
Are you sure the switch/hub/router is failing?
With any remote connection such as smb/nfs/sshfs, if the target becomes
unavailable for some reason such as lag or a bad route from Point A to
Point B then that terminal window will hang till point B is reachable.
ionut cucu wrote:
> On Thu, 28 Feb 2008 16:51:59 -0500
> Jerry McBride <mcbrides9@comcast.net> wrote:
>
>> On Thursday 28 February 2008 04:19:22 pm ionut cucu wrote:
>>> I'm running sshfs very often and I've noticed the following issue:
>>> whenever the hub/swich(what ever is that keeping my lan together)
>>> suddenly stops working while I'm using sshfs my computer crashes,
>>> or if I;m lucky enough I get to do an umount before everything
>>> falls. Is there any way to prevent this?
>>> Also since this is a lan is there a null encryption algorithm I
>>> could use to speed things up a bit? Or lower the CPU usage?
>>> Thanks!
>> Dude... time for a new switch...
>>
> Yeah well it's a campus *(1) switch, the campus's *(2) lan, the
> campus's *(3) gateway....so on so forth till the A class IP so I can do
> nothing about it
>
> Note *(1) to *(2) are ugly words and shouldn't be used around children
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-28 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 21:19 [gentoo-user] sshfs issue ionut cucu
2008-02-28 21:51 ` Jerry McBride
2008-02-28 21:58 ` ionut cucu
2008-02-28 22:11 ` Neil Walker
2008-02-28 22:42 ` Jerry McBride
2008-02-28 22:43 ` Chris Brennan [this message]
2008-02-29 7:56 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C738FD.3050109@xaerolimit.net \
--to=xaero@xaerolimit.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox