poor NFS performance in CURRENT

Hi :) I upgraded two boxes to FreeBSD-5.2-BETA a week ago and I noticed that NFS performance is very slow compared to 4.x-RELEASE. Before, NFS transfers were between 10 and 12 MB/s and now I don't go past 7 MB/s. My exports/mount settings did not change and the hardware is obviously the same. M

ntpd and kvm_getprocs

default ignore #---# Thanks. -- Antoine Jacoutot [EMAIL PROTECTED] http://www.lphp.org PGP/GnuPG key: http://www.lphp.org/ressources/ajacoutot.asc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/fre

Re: Re: rpc.lockd core dumped

> I can only say that I had a core dump under current on sparc, but the core > file was unusable. Can you compile rcp.lockd with -g in CFLAGS and LDFLAGS > and try to find out with gdb where it aborts? > > harti Hi :) I investigate a little more this nfs locking issue. I recompile my system with

Re: upgraded to CURRENT = system is dead

On Tuesday 18 November 2003 00:17, Garance A Drosihn wrote: > Users need to specify a single target of 'installkernel', > with no blanks between the two words. Antoine, was that > just a typo, or did you really do 'make install kernel'? I was a typo :) -- Anto

Re: upgraded to CURRENT = system is dead

Selon Michael Collette <[EMAIL PROTECTED]>: > I just ran into this very same thing today on a brand new installation. Upon > > reboot I can't even get to a shell. Was rather hoping someone had some more > > information about this. > > Running the installation on an IBM xSeries 305 with a P4.

Re: upgraded to CURRENT = system is dead

Selon Aron Håkanson <[EMAIL PROTECTED]>: > If you are looking for a fast and temporary solution, just to finish the > installworld process, you can export the following value to the > LD_LIBRARY_PATH variable: "$LD_LIBRARY_PATH:/lib:/usr/lib" Hey :) Thanks a lot... I'll try that. Antoine

Re: upgraded to CURRENT = system is dead

Selon Dylan Wylie <[EMAIL PROTECTED]>: > The idea is that you need to build a new kernel with the new sources before > you install > world. > You built your kernel before building the sources, so your kernel is based on > old source. > > Quoting from another message: > > make buildworld > > make

Re: upgraded to CURRENT = system is dead

Selon long <[EMAIL PROTECTED]>: > reboot > make world > single user mode, make installworld > reboot > > and it's up and running... no more sig12 or anything like that... Yes, but no ! I don't have any sig12 error... I have: /libexec/ld-elf.so.1: Shared object "libedit.so.4" not found And I can'

upgraded to CURRENT = system is dead

me my box isn't dead... By the way, I compiled CURRENT with dynamic root. Thanks in advance. -- Antoine Jacoutot [EMAIL PROTECTED] http://www.lphp.org PGP/GnuPG key: http://www.lphp.org/ressources/ajacoutot.asc ___ [EMAIL PROTECTED] mailing lis

Re: rpc.lockd core dumped

> Check to make sure that rpc.statd is running. There was an old bug that > rpc.lockd would dump core if it couldn't find a statd. Ho, it is running :) Actually, all my homedir are mounted with NFS, so rpc.lockd get used a lot. That is why it is an important concern to me. I couldn't find any rep

Re: rpc.lockd core dumped

I will rpc.lockd with -ggdb as you said and see if it is repeatable. Unfortunately, I'm not home right now, so I'll do this in 3 o 4 days. Regards. Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: rpc.lockd core dumped

On Saturday 08 November 2003 12:26, Harti Brandt wrote: > I can only say that I had a core dump under current on sparc, but the core > file was unusable. Can you compile rcp.lockd with -g in CFLAGS and LDFLAGS > and try to find out with gdb where it aborts? Allright, as soon as I get home in 4/5 d

rpc.lockd core dumped

more information but I didn't see where to find more debuging options for rpc.lockd. 5.1-CURRENT #0: Tue Nov 4 01:44:35 CET 2003 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/KERNSRV01 i386 Thanks in advance. -- Antoine Jacoutot [EMAIL PROTECTED] http://www.lphp.org PGP/GnuPG key: http://ww

Re: NFS client mount options in CURRENT/5.1-

Scott W wrote: mount -tnfs -orw,rsize=8196,wsize=8196,bg,hard,intr,async sol:/export /mnt nfs: -o rsize=: option not supported Try "-r 8196 -w 8196" and have a look at man mount_nfs. Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/m

Re: if_tun failed to register

On Wednesday 05 November 2003 23:25, Brian Lynn wrote: > will be run at startup if you have any ifconfig_tun* lines in rc.conf. > You can see if ifconfig is the culprit by booting single-user and doing > ifconfig tun0 (it is only the first attempt that gives the error message > in question). If so

Re: if_tun failed to register

On Wednesday 05 November 2003 23:07, Michael Nottebrock wrote: > FWIW, tun _is_ in the kernel if you compile it in, but gets loaded a second > time. The module which gets loaded isn't actually used. Hum, strange... :) Do you know if the lastest -CURRENT fixes that ? Antoine _

Re: if_tun failed to register

On Wednesday 05 November 2003 22:47, Brooks Davis wrote: > > Thanks, I'm happy I'm not the only one seeing this :) > > It looks like ppp does not get compiled in the kernel either... :( > > ppp(4) is in GENERIC. You just have to create the devices like: No ! Although tun and ppp are in GENERIC, t

Re: if_tun failed to register

On Wednesday 05 November 2003 18:37, you wrote: > It's been there for quite a while, I see that behaviour in 5.1-RELEASE, > too. Thanks, I'm happy I'm not the only one seeing this :) It looks like ppp does not get compiled in the kernel either... :( Antoine __

Re: if_tun failed to register

Matteo Riondato wrote: Well, it did not change anything :( What is really strange is that "tun" is compiled in the kernel, but the module is started anyway ??? I had the same problem last year and solved it by removing device tun from the kernel configuration file. Yes, I though about it. But s

Re: if_tun failed to register

Max Laier wrote: > AJ> > AJ> module_register: module if_tun already exists! > AJ> Module if_tun failed to register: 17 > AJ> can't re-use a leaf (if_tun_debug)! > AJ> > AJ> Is there a kernel option I m

if_tun failed to register

ot;device tun" in my kernel config file. Thanks in advance. -- Antoine Jacoutot [EMAIL PROTECTED] http://www.lphp.org PGP/GnuPG key: http://www.lphp.org/ressources/ajacoutot.asc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org

Re: OpenLDAP/nss_ldap/pam_ldap

On Wednesday 29 October 2003 00:42, you wrote: > I just checked the FreeBSD site and do not see any release 5.2 It is not release yet :) > Once i can hurl this obsticle, i think FreeBSD might be a viable > solution for me. Well, let be it then... I'm running -CURRENT with dynamic root and it wor

Re: OpenLDAP/nss_ldap/pam_ldap

On Tuesday 28 October 2003 23:52, Steve Lee wrote: > I have gotten FreeBSD 5.1 to authenticate user remotely > ssh ing to the box. They can log in, but when they log > in, the system shows their userid instead of the username > when you do a ps. this tells me something might be > wrong with nss_

Re: Upgrading to FreeBSD 5.1

Kris Kennaway wrote: On Mon, Sep 15, 2003 at 03:13:30PM -0400, Didier Rwitura wrote: I am trying to upgrade my sysstem from 4.8-RELEASE-p4 to 5.1 and i getting this error message when I run "make -j4 buildworld" I had the same problem. Making without the "-j4" option works however. Antoine __

pam_mkhomedir

exist. I know I need pam_mkhomedir for this but I can't find it under 5.1. If I remember, pam_mkhomedir was in the contrib section under 4.x. Any idea why it is not part of FreeBSD anymore ? Or do you know any other way of auto-creating users homedir ? Thanks in advance, Regards. - -- An

Re: Palm syncing over USB on FreeBSD, any hopes?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 29 July 2003 19:24, Rajappa Iyer wrote: > ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 2 > ucom0: init failed, STALLED > device_probe_and_attach: ucom0 attach returned 6 Try this: http://www.lphp.org/popups/articleswindow.php?id=13