On 26 May, Skylar Thompson wrote:
> I'm having some problems with NFS serving on a FreeBSD 5.4-RELEASE
> machine. The FreeBSD machine is the NFS/NIS server for a group of four
> Linux clusters. The network archictecture looks like this:
>
> 234/24
On 26 May, Skylar Thompson wrote:
> I'm having some problems with NFS serving on a FreeBSD 5.4-RELEASE
> machine. The FreeBSD machine is the NFS/NIS server for a group of four
> Linux clusters. The network archictecture looks like this:
>
> 234/24
Try switching to TCP NFS.
a 100MBit interface cannot keep up with a 1GBit interface in a bridge
configuration. Therefore, in the long run, at full-bore you'd expect to
drop 9 out of every 10 ethernet frames.
MTU is 1500 therefore 1K works (it fits in one frame), 2K doesn't (your
NFS transactions
Try switching to TCP NFS.
a 100MBit interface cannot keep up with a 1GBit interface in a bridge
configuration. Therefore, in the long run, at full-bore you'd expect to
drop 9 out of every 10 ethernet frames.
MTU is 1500 therefore 1K works (it fits in one frame), 2K doesn't (your
NFS transactions
On Thu, 2005-May-26 23:41:26 -0600, Scott Long wrote:
>Seems to work for me with the commented lines fixed. Btw, you by no
>doubt have noticed that it's somewhat inconvenient to do 4th programming
>by modifying the boot scripts and then praying that the reboot works.
>It's possible to do 90% of t
Hello,
Didn't get a response so i'm going to try this again. I'm trying to do a
fresh install of 5.4 on a test machine, which previously ran 5.3 just fine.
I'm doing the install via a serial terminal as this box is headless and off
of an nfs server which i've also prepared identically to 5.3. I
Hello,
Didn't get a response so i'm going to try this again. I'm trying to do a
fresh install of 5.4 on a test machine, which previously ran 5.3 just fine.
I'm doing the install via a serial terminal as this box is headless and off
of an nfs server which i've also prepared identically to 5.3. I
Hi,
Since updating our server to 5.4-STABLE, I've noticed a very strange
problem with cron.
Sometimes it just decides to stop, for no apparent reason. It stops at
different times, it doesn't seem to be affected by any particular
cronjob.
There are no messages about this in any logfile, it just stop
Phil,
On Fri, 27 May 2005, Phil Brennan wrote:
> Since updating our server to 5.4-STABLE, I've noticed a very strange
> problem with cron.
> Sometimes it just decides to stop, for no apparent reason. It stops at
> different times, it doesn't seem to be affected by any particular
> cronjob.
> There
On Tue, 10 May 2005, Marc Olzheim wrote:
On Tue, May 03, 2005 at 05:00:14PM +0200, Marc Olzheim wrote:
Is this going to be fixed before 5.4 ? It still breaks on today's
5.4-STABLE.
As this is the only issue known to me now, that I don't have a patch for
and is standing in my way of upgradin
Phil Brennan wrote:
> Since updating our server to 5.4-STABLE, I've noticed a very strange
> problem with cron.
> Sometimes it just decides to stop, for no apparent reason. It stops at
> different times, it doesn't seem to be affected by any particular
> cronjob.
> There are no messages about this
From: Phil Brennan <[EMAIL PROTECTED]>
Date: May 27, 2005 1:30 PM
Subject: Re: cron stops silently
To: Dean Strik <[EMAIL PROTECTED]>
On 5/27/05, Dean Strik <[EMAIL PROTECTED]> wrote:
> Phil Brennan wrote:
> > Since updating our server to 5.4-STABLE, I've noticed a very strange
> > problem with c
On Fri, May 27, 2005 at 12:47:28PM +0100, Robert Watson wrote:
> Hmm. I'm unable to reproduce this on local SMP hardware, although I can
> see at least one way that the race could occur. Could you try the
> attached patch and see if it helps matters? This is a slight shot in the
> dark but cl
Phil Brennan wrote:
> From: Phil Brennan <[EMAIL PROTECTED]>
> Date: May 27, 2005 1:30 PM
> Subject: Re: cron stops silently
> To: Dean Strik <[EMAIL PROTECTED]>
>
>
> On 5/27/05, Dean Strik <[EMAIL PROTECTED]> wrote:
> > Phil Brennan wrote:
> > > Since updating our server to 5.4-STABLE, I've not
On Thu, 26 May 2005, Scott Long wrote:
Is the goal to have a new major branch every 2 years?
Yes. This will allow us to pace our major development projects much
better than we have in the past.
Someone mentioned 5.X will be supported till 2007 (or at least that's the
plan). So will, in ave
On Friday 27 May 2005 08:05, Dean Strik wrote:
> I just filed PR 81555 about this. For me, it appears that cron(8) exits
> after a SIGPIPE when an LDAP-user does a crontab -e. Are you also using
> LDAP here? See also the PR (hasn't appeared on the website when I type
> this btw).
Me too
--
Kir
Hi,
I got the same problem with NAT not working at boot time after upgrading
to 5.4. I compiled a generic kernel, so it doesn't seem to be a problem
concerning the kernel. I guess some change in the rc system.
Hope we find a solution.
sincerely,
Daniel Mester
___
Francisco Reyes wrote:
On Thu, 26 May 2005, Scott Long wrote:
Is the goal to have a new major branch every 2 years?
Yes. This will allow us to pace our major development projects much
better than we have in the past.
Someone mentioned 5.X will be supported till 2007 (or at least that's
* Kirk Strauser <[EMAIL PROTECTED]> [0538 15:38]:
> On Friday 27 May 2005 08:05, Dean Strik wrote:
>
> > I just filed PR 81555 about this. For me, it appears that cron(8) exits
> > after a SIGPIPE when an LDAP-user does a crontab -e. Are you also using
> > LDAP here? See also the PR (hasn't appear
Peter Jeremy wrote:
On Thu, 2005-May-26 23:41:26 -0600, Scott Long wrote:
Seems to work for me with the commented lines fixed. Btw, you by no
doubt have noticed that it's somewhat inconvenient to do 4th programming
by modifying the boot scripts and then praying that the reboot works.
It's pos
On Fri, May 27, 2005 at 03:44:41PM +0200, Marc Olzheim wrote:
> Could you try the attached patch and see if it helps matters? This is
> a slight shot in the dark but closes at least two races in the
> transition of socket state with respect to socket buffer state.
Yes! This fixes it, on the tag=R
Hi,
We can't change nis password on your server using yppaswd : after
"Retype New Password:" server says "yppasswd: pam_chauthtok(): error in
service module".
In /var/log/messages :
nisserver kernel: pid 5196 (rpc.yppasswdd), uid 0: exited
on signal 11
nisserver yppasswd: in pam_sm_chau
I'm mounting a snapshot using mdconfig, then mount like this:
mdconfig -a -t vnode -f /home/.snap/4 -u 0
mount /dev/md0 /snapshot/home
mount (with no args) shows this:
/dev/md0 on /snapshot/home (ufs, local, read-only)
# mdconfig -l -u md0
md0 vnode 23503425 KBytes
How can I see (to veri
I am experiencing problems keeping FreeBSD 5.4 connected. I have uptimes of
5 or 6 days - sometimes 10 or 11, then, without freezing the machine
totally, it stops responding to network traffic. I get DOS attacked every
once and a while and my logs are also filled with failed auths from password
Friday, May 20, 2005, 1:15:42 PM, you wrote:
> Do these lists have a moderator or is he on vacation? Im tired of deleting
> this useless thread from my mailbox.
So you decided to add another *useless* message to the thread, as did I. :)
-ip
--
The more time and energy you put into preparing a m
25 matches
Mail list logo
