On Mon, 3 Jul 2006, Kostik Belousov wrote:
On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote:
Kostik Belousov writes:
Since nobody except you experience that problems (at least, only you
notified
about the problem existence)
Did you miss the part of:
User Freebsd writes:
Dan Nelson [EMAIL PROTECTED] wrote:
In the last episode (Jul 02), Robert Watson said:
On Sun, 2 Jul 2006, Fabian Keil wrote:
The ssh man page offers:
|~B Send a BREAK to the remote system (only useful for SSH
|protocol version 2 and if the peer supports it).
I am
Fabian Keil [EMAIL PROTECTED] wrote:
Robert Watson [EMAIL PROTECTED] wrote:
It sounds like your serial console server may not know how to map
SSH break signals into remote serial break signals. Try
ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES:
# Solaris implements a new
On Mon, Jul 03, 2006 at 10:06:52AM +0100, Robert Watson wrote:
On Mon, 3 Jul 2006, Kostik Belousov wrote:
On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote:
Kostik Belousov writes:
Since nobody except you experience that problems (at least, only you
notified
about the
On Mon, Jul 03, 2006 at 10:06:52AM +0100, Robert Watson wrote:
It sounds like there is also an NFS client race condition or other bug of
some sort.
It may not be related, directly, but one thing that I noticed,
while trying to sort out my own recently commissioned NFS setup,
is that the -r1024
So it would appear that you cured the NFS problems inherent with FBSD-6
by replacing FBSD with Fedora Linux. Nice to know that NFSd works in Linux.
But won't help those on the FBSD list fix their FBSD-6 boxen. :/
First NFS is designed to make machines of different OSs interact properly.
If a
On Mon, 3 Jul 2006, Francisco Reyes wrote:
Kostik Belousov writes:
I think that then 6.2 and 6.3 is not for you either. Problems
cannot be fixed until enough information is given.
I am trying.. but so far only other users who are having the same problem are
commenting on this and other
Michel Talon wrote:
[ ...a long email snipped... ]
My only conclusion is that these NFS stories are very
tricky. The only moment everything worked fine was when we were running
Solaris on the server.
I can't speak to the earlier part about NFS with Linux, but at least I very
much agree with
On Jun 30, 2006, at 8:08 PM, Dan Charrois wrote:
In any case, the server is used heavily all year except July, so
this is my time of year to take things apart, update software,
etc. And so I'm wondering - what is the recommended version of
FreeBSD I should be running if stability is of
At 9:13 PM -0400 7/1/06, Francisco Reyes wrote:
John Hay writes:
I only started to see the lockd problems when upgrading
the server side to FreeBSD 6.x and later. I had various
FreeBSD clients, between 4.x and 7-current and the lockd
problem only showed up when upgrading the server from
5.x to
Garance A Drosihn wrote:
At 9:13 PM -0400 7/1/06, Francisco Reyes wrote:
John Hay writes:
I only started to see the lockd problems when upgrading
the server side to FreeBSD 6.x and later. I had various
FreeBSD clients, between 4.x and 7-current and the lockd
problem only showed up when
On Fri, Jun 30, 2006, Robert Watson wrote:
Thanks for testing the patch -- it looks like there's a more pressing
logical problem in this code! Could you try the following simpler patch:
http://www.watson.org/~robert/freebsd/netperf/ip_ctloutput.diff
The IP option code seems not to know
User Freebsd wrote:
On Sat, 1 Jul 2006, Francisco Reyes wrote:
John Hay writes:
I only started to see the lockd problems when upgrading the server side
to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x
and 7-current and the lockd problem only showed up when upgrading the
On Tue, 4 Jul 2006, Stanislaw Halik wrote:
On Fri, Jun 30, 2006, Robert Watson wrote:
Thanks for testing the patch -- it looks like there's a more pressing
logical problem in this code! Could you try the following simpler patch:
14 matches
Mail list logo
