Merry Christmas!
I'd just like to say Merry Christmas to all the people of FreeBSD. Have a great one. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
4.5-PRERELEASE smbfs resolving issues
Hi, I've got some smalltime issues with smbfs resolving. Here: --- asd$ nslookup fileserver Server: dns.asd Address: 192.168.100.100 Name:fileserver.asd Address: 192.168.100.101 asd# echo 192.168.100.101 asdasd /etc/hosts asd# mount_smbfs //guest@fileserver/mp3-i /mnt Password: asd# mount | grep mnt //GUEST@FILESERVER/MP3-I on /mnt (smbfs) asd# umount /mnt [That works] asd# mount_smbfs //guest@asdasd/mp3-i /mnt mount_smbfs: can't get server address: syserr = Operation timed out [Won't resolve with /etc/hosts] asd# mount_smbfs [EMAIL PROTECTED]/mp3-i /mnt mount_smbfs: server name '192.168.100.101' too long [An IP address with one less character will work] asd# mount_smbfs /guest@fileserver/mp3-i /mnt mount_smbfs: no server name specified [Only one / before the username yields wrong error message] --- Is that worth a PR ? Best Regards, Yonatan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.5-PRERELEASE Major Stalling
This diff fixed it, for anyone curious, I don't know why a cvsup didnt get
it:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket2.c.diff?r1=1.
78r2=1.79f=h
--IS
- Original Message -
From: ISPrime Support [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 25, 2001 2:53 AM
Subject: 4.5-PRERELEASE Major Stalling
I work at an ISP which hosts zfreehost.com (a pretty large freehost,
pushing
about 300 megabit).
The zfreehost network has a few FBSD servers (all 4.4-STABLE except one
4.5-PRERELEASE) running a custom in-house webserver, using a FBSD NFS
Storage backend.
Anyway, I upgraded one of the servers to 4.5-PRERELEASE just to test it
out
for us, and I noticed there are MAJOR stalls in 4.5. After about 5
minutes
of running, all of the webserver processes (8 processes) are sitting in
state sbwait, doing nothing. in a truss, it like it stalls on the read()
immediately after accept() from the client socket (http). We run httpready
accept filtering, so when we do a read() it should never ever stall since
it
wouldn't have accept()'d if there wasnt data to read(), or if it was ready
to close(), anyway -- I consider this to be a pretty major regression.
At
the way this is running, we wont be able to run 4.5 on any of the
production
servers, so I hope this can get fixed.
Here is what I see from top:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
266 nobody 2 0 992K 664K sbwait 0:01 0.63% 0.63% pimpd
267 nobody 2 0 992K 664K sbwait 0:01 0.10% 0.10% pimpd
264 nobody 2 0 992K 664K sbwait 0:01 0.05% 0.05% pimpd
86 root 10 0 208K80K nfsidl 0:00 0.05% 0.05% nfsiod
123 root 28 0 2348K 1944K RUN 0:01 0.00% 0.00% sshd
85 root 10 0 208K80K nfsidl 0:01 0.00% 0.00% nfsiod
269 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
262 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
268 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
263 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
265 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
This is what I see from ps auwx:
nobody 262 0.0 0.1 992 664 ?? Is2:47AM 0:00.37 pimpd
nobody 263 0.0 0.1 992 664 ?? I 2:47AM 0:00.25 pimpd
nobody 264 0.0 0.1 992 664 ?? I 2:47AM 0:01.19 pimpd
nobody 265 0.0 0.1 992 664 ?? I 2:47AM 0:00.13 pimpd
nobody 266 0.0 0.1 992 664 ?? I 2:47AM 0:01.74 pimpd
nobody 267 0.0 0.1 992 664 ?? I 2:47AM 0:01.95 pimpd
nobody 268 0.0 0.1 992 664 ?? I 2:47AM 0:00.30 pimpd
nobody 269 0.0 0.1 992 664 ?? I 2:47AM 0:01.96 pimpd
I did not enable fxp bundling.
Here is sysctl -a:
kern.ostype: FreeBSD
kern.osrelease: 4.5-PRERELEASE
kern.osrevision: 199506
kern.version: FreeBSD 4.5-PRERELEASE #0: Tue Dec 25 02:13:41 EST 2001
root@zf3:/usr/src/sys/compile/ZFREE
kern.maxvnodes: 68412
kern.maxproc: 4116
kern.maxfiles: 8232
kern.argmax: 65536
kern.securelevel: -1
kern.hostname: zfreeVA3.isprime.com
kern.hostid: 0
kern.clockrate: { hz = 100, tick = 1, tickadj = 5, profhz = 1024,
stathz
= 128 }
kern.posix1version: 199309
kern.ngroups: 16
kern.job_control: 1
kern.saved_ids: 0
kern.boottime: { sec = 1009265636, usec = 169977 } Tue Dec 25 02:33:56
2001
kern.domainname:
kern.osreldate: 45
kern.bootfile: /kernel
kern.maxfilesperproc: 7408
kern.maxprocperuid: 3704
kern.dumpdev:
kern.ipc.maxsockbuf: 2097152
kern.ipc.sockbuf_waste_factor: 8
kern.ipc.somaxconn: 10240
kern.ipc.max_linkhdr: 16
kern.ipc.max_protohdr: 40
kern.ipc.max_hdr: 56
kern.ipc.max_datalen: 156
kern.ipc.nmbclusters: 65536
kern.ipc.semmap: 30
kern.ipc.semmni: 10
kern.ipc.semmns: 60
kern.ipc.semmnu: 30
kern.ipc.semmsl: 60
kern.ipc.semopm: 100
kern.ipc.semume: 10
kern.ipc.semusz: 92
kern.ipc.semvmx: 32767
kern.ipc.semaem: 16384
kern.ipc.shmmax: 40960
kern.ipc.shmmin: 1
kern.ipc.shmmni: 192
kern.ipc.shmseg: 128
kern.ipc.shmall: 8192
kern.ipc.shm_use_phys: 0
kern.ipc.mbuf_wait: 32
kern.ipc.mbtypes: 3589 3759 76 0 0 0 0 0 0 0 0 0 0 0 0 0
kern.ipc.nmbufs: 262144
kern.ipc.maxsockets: 65536
kern.dummy: 0
kern.ps_strings: 3217031152
kern.usrstack: 3217031168
kern.logsigexit: 1
kern.cam.da.retry_count: 4
kern.cam.da.default_timeout: 60
kern.fallback_elf_brand: -1
kern.init_path: /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall
kern.module_path: /;/boot/;/modules/
kern.acct_suspend: 2
kern.acct_resume: 4
kern.acct_chkfreq: 15
kern.cp_time: 511 0 2075 2732 147211
kern.timecounter.method: 0
kern.timecounter.hardware: TSC
kern.openfiles: 52
kern.kq_calloutmax: 4096
kern.ps_arg_cache_limit: 256
kern.ps_argsopen: 1
kern.fast_vfork: 1
kern.randompid: 0
kern.maxusers: 256
kern.ps_showallprocs: 1
kern.shutdown.poweroff_delay: 5000
Re: mount_smbfs error
Thanks, problem disappeared. but why prints /dev/net/nsmb*? -- David Xu Dimitry Andric wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2001-12-25 at 06:28:49 David Xu wrote: DX smbfs: can't get handle to requester (no /dev/net/nsmb* device) The problem is that the required /dev/nsmb0 device is not created during make world. See this PR for more info: http://www.freebsd.org/cgi/query-pr.cgi?pr=33068 It seems the fix for this didn't get committed yet, so please work around this for now by manually creating it. Just run: mknod /dev/nsmb0 c 144 0 as root, and you should be able to use mount_smbfs. Cheers, - -- Dimitry Andric [EMAIL PROTECTED] PGP Key: http://www.xs4all.nl/~dim/dim.asc Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3 Lbh ner abj va ivbyngvba bs gur QZPN -BEGIN PGP SIGNATURE- Version: PGP 6.5i Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBPCgfSLBeowouIJajEQKUnQCZAcqBoGq9/W1C5KUnp74NMps5K9YAniA2 rL73dp6TswFOOo51rPZdBdsd =svAD -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: mount_smbfs error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2001-12-25 at 09:49:50 David Xu wrote: DX Thanks, problem disappeared. DX but why prints /dev/net/nsmb*? That is indeed confusing, and I already reported it in the PR too. Please be patient: the fix for this is pending, as you can read in the PR followups. Cheers, - -- Dimitry Andric [EMAIL PROTECTED] PGP Key: http://www.xs4all.nl/~dim/dim.asc Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3 Lbh ner abj va ivbyngvba bs gur QZPN -BEGIN PGP SIGNATURE- Version: PGP 6.5i Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBPCgzerBeowouIJajEQK9jwCg3k6p4A2ikN5K0SwjOLSr75s6Jm0AoIaw DgRI0V2+RQrOhDAN6vqmZ7pV =zebT -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.5 PRERELEASE - Call for testing
H I have never had this problem at all, and keep all my mp3's and vids on the samba server. The box I play Mp3's on is behind a switch and a hub. My Samba box is an old 166Mhz with 65M of memory to compensate a bit for its less than blinding speed processor. The box is gets fairly busy as well with firewalling (OMG!), X11, and Apache / MRTG on a cable modem (call me crazy!). Another possibility is you do not have a Samba problem, but a network problem with auto-negotiate. Some older 10/100 cards and switch combinations step all over each other. You should lock down one end to a specific speed and if 100Mbs, try full duplex. Another thing to consider... if you are running 100, make sure its Cat5 cable and not a left over hunk of Cat3 confusing the card into negotiation. The only other thing I recall having problems was using tcpwrappers trying to fire multiple copies of the dameons, but that resulted in complete lack of response and many messages about too many copies running. I did notice, and the doc's point this out, you need to make a choice between login's and plain ole shares. When I tried to do both, it was extremely erractic. Since I wanted some disk space privacy, I opted for login's with links from my user space to a common area with the Mp3's to emulate a share. The only problem with login's it is separate file that is not automatically synched with passwd changes and becomes a two step process. The only other possible difference is I do not run printers via Samba, and instead let netbios figure it out. Good luck... hope this helps... someone, somewhere, someday g Keith - Original Message - From: Peter Ong [EMAIL PROTECTED] To: Robert Watson [EMAIL PROTECTED]; Nevermind [EMAIL PROTECTED] Cc: Murray Stokely [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, December 23, 2001 5:13 PM Subject: Re: 4.5 PRERELEASE - Call for testing I apologize if I'm off. But it seems you guys are talking about improving FBSD 4.5 networking performance. I am currently using FreeBSD 4.4 Release. It works great, but there is that one problem Samba. I like Samba because it's functional. I don't know if it's Samba's fault, or if it's BSD's fault, but it behaves very erratically. Sometimes it's fast, sometimes it's slow. When I used RH7.1, I installed Samba there as well. Samba worked fine, but also with the same behavior. But it was somewhat more reliable on RH than FreeBSD. I don't know if it's Samba itself or the OS, although I'm inclined to say it is Samba. If so, disregard this message. When I used RH/Samba, I put all of my MP3 music there. I'd listen to it on Winamp from my Win98 laptop. It worked fine... no skips. But when I put it on FreeBSD, the first minute or so is skip free, but as it passes that time limit it starts skipping... I mean, it blanks out as if it's readying the cache faster than it's being transfered over the network. My network is 10/100Mbits switched. The difference is now only the operating system. The box is a P3/450/128MB. It had RH, then it moved to FreeBSD. Now, I'm having that problem. Videos are even worse. I have some *.mov, and Real movie files, that I must first download, and then I watch. I can't watch it over the wire. This is just my two cents. Maybe 5 cents. Thanks. - Original Message - From: Robert Watson [EMAIL PROTECTED] To: Nevermind [EMAIL PROTECTED] Cc: Murray Stokely [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, December 23, 2001 10:53 AM Subject: Re: 4.5 PRERELEASE - Call for testing On Sun, 23 Dec 2001, Nevermind wrote: Hello, Murray Stokely! On Fri, Dec 21, 2001 at 04:30:37PM -0800, you wrote: There were some problems with the network performance of FreeBSD 4.4 that were never discovered during the release candidates phase, so I'd like to take a more pro-active role in getting users to test the system in more demanding environments. A complete list of changes is available in the 4.5-PRERELEASE release notes, available at : http://people.freebsd.org/~bmah/relnotes/ Could you, please, include in Relnotes that Java will be included in 4.5? I have't seen that support actually appear in ports/packages-land as yet, but I greatly look forward to that happening. It would probably be appropriate to wait until the details have been committed before documenting it. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Mounting a Linux HDD Extended partition.
Hello, Peter Ong! On Mon, Dec 24, 2001 at 01:29:34PM -0800, you wrote: Why do your messages arrive as attachments? Because his messages are PGP-signed. -- NEVE-RIPE To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: libfetch.so.2 should be included in src/lib/compat/compat4x.*
NIIMI Satoshi [EMAIL PROTECTED] writes: Without libfetch.so.2, upcoming 4.5-RELEASE will lose backward compatibility with previous 4.x releases. The only libfetch consumers (that I know of) are fetch(1) and the pkg tools. Old binaries will still work on an upgraded system (which will still have libfetch.so.2) but not on a fresh install (which will lack libfetch.so.2), but both upgraded and freshly installed systems will have up-to-date versions of fetch(1) and the pkg tools. Moreover, libfetch.so.3 is backward compatible, so a symlink should be sufficient to support old binaries. The reason for the bump is that new binaries will not work with an old library. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NTPD dumps core in 4.5-PRERELEASE
Hi Keltia, According to Martin Blapp: I see something similar here. Nsrexec, a networker client which gets started in rc.d segfaults since 1-2 month here. Ask Matt for a 6.0 client. He recompiled one two months ago and it has stopped segfaulting for me on CURRENT. drwxr-xr-x 2 root wheel 512 Dec 3 11:20 nwclient-6.0.2 Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.5 PRERELEASE - Call for testing
i would like to get my notebook,which hangs on boot (pcic), to run again with freebsd. was there any recent changes or any hints how i could get around that problem? (the problem was posted with KAPOK in the subject). -- -- Best regards / Mit freundlichen Gruessen, Karl M. Joch To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Networker (Was: Re: NTPD dumps core in 4.5-PRERELEASE)
According to Martin Blapp: drwxr-xr-x 2 root wheel 512 Dec 3 11:20 nwclient-6.0.2 Weird. Various 5.1/5.5 clients (compiled on -STABLE by Matt) were very unstable (segfault on startup and non working afterwards) and moving to -STABLE-compiled 6.02 fixed it. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: libfetch.so.2 should be included in src/lib/compat/compat4x.*
Hello, Dag-Erling Smorgrav! On Tue, Dec 25, 2001 at 08:21:23PM +0100, you wrote: NIIMI Satoshi [EMAIL PROTECTED] writes: Without libfetch.so.2, upcoming 4.5-RELEASE will lose backward compatibility with previous 4.x releases. The only libfetch consumers (that I know of) are fetch(1) and the pkg tools. Old binaries will still work on an upgraded system (which will still have libfetch.so.2) but not on a fresh install (which will lack libfetch.so.2), but both upgraded and freshly installed systems will have up-to-date versions of fetch(1) and the pkg tools. Almost every http/ftp-accessing software (on C/C++), we wrote here uses libfetch, I suppose your reasons for not adding libfetch.so.2 to compat4x is not very good. We will need to rebuild and/or make symlink on every machine running libfetch. I think it is not right. Moreover, libfetch.so.3 is backward compatible, so a symlink should be sufficient to support old binaries. The reason for the bump is that new binaries will not work with an old library. Yes, it works for now. But if I need sell software to somebody, who runs 4.5-RELEASE he/she will say me: What the hell is going on? Your ... program says it cannot find some library. I've searched all my harddrive and have not found libfetch.so.2 And, please note, he/she didn't know anything about symlinks, he/she is just enduser. -- NEVE-RIPE To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.5-PRERELEASE Major Stalling
Probably because v1.79 of uipc_socket2.c hasn't been MFC'd yet. Since
this is a big issue for this particular person, could this be looked into?
--
Matthew Emmerton || [EMAIL PROTECTED]
GSI Computer Services || http://www.gsicomp.on.ca
On Tue, 25 Dec 2001, ISPrime Support wrote:
This diff fixed it, for anyone curious, I don't know why a cvsup didnt get
it:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket2.c.diff?r1=1.
78r2=1.79f=h
--IS
- Original Message -
From: ISPrime Support [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 25, 2001 2:53 AM
Subject: 4.5-PRERELEASE Major Stalling
I work at an ISP which hosts zfreehost.com (a pretty large freehost,
pushing
about 300 megabit).
The zfreehost network has a few FBSD servers (all 4.4-STABLE except one
4.5-PRERELEASE) running a custom in-house webserver, using a FBSD NFS
Storage backend.
Anyway, I upgraded one of the servers to 4.5-PRERELEASE just to test it
out
for us, and I noticed there are MAJOR stalls in 4.5. After about 5
minutes
of running, all of the webserver processes (8 processes) are sitting in
state sbwait, doing nothing. in a truss, it like it stalls on the read()
immediately after accept() from the client socket (http). We run httpready
accept filtering, so when we do a read() it should never ever stall since
it
wouldn't have accept()'d if there wasnt data to read(), or if it was ready
to close(), anyway -- I consider this to be a pretty major regression.
At
the way this is running, we wont be able to run 4.5 on any of the
production
servers, so I hope this can get fixed.
Here is what I see from top:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
266 nobody 2 0 992K 664K sbwait 0:01 0.63% 0.63% pimpd
267 nobody 2 0 992K 664K sbwait 0:01 0.10% 0.10% pimpd
264 nobody 2 0 992K 664K sbwait 0:01 0.05% 0.05% pimpd
86 root 10 0 208K80K nfsidl 0:00 0.05% 0.05% nfsiod
123 root 28 0 2348K 1944K RUN 0:01 0.00% 0.00% sshd
85 root 10 0 208K80K nfsidl 0:01 0.00% 0.00% nfsiod
269 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
262 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
268 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
263 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
265 nobody 2 0 992K 664K sbwait 0:00 0.00% 0.00% pimpd
This is what I see from ps auwx:
nobody 262 0.0 0.1 992 664 ?? Is2:47AM 0:00.37 pimpd
nobody 263 0.0 0.1 992 664 ?? I 2:47AM 0:00.25 pimpd
nobody 264 0.0 0.1 992 664 ?? I 2:47AM 0:01.19 pimpd
nobody 265 0.0 0.1 992 664 ?? I 2:47AM 0:00.13 pimpd
nobody 266 0.0 0.1 992 664 ?? I 2:47AM 0:01.74 pimpd
nobody 267 0.0 0.1 992 664 ?? I 2:47AM 0:01.95 pimpd
nobody 268 0.0 0.1 992 664 ?? I 2:47AM 0:00.30 pimpd
nobody 269 0.0 0.1 992 664 ?? I 2:47AM 0:01.96 pimpd
I did not enable fxp bundling.
Here is sysctl -a:
kern.ostype: FreeBSD
kern.osrelease: 4.5-PRERELEASE
kern.osrevision: 199506
kern.version: FreeBSD 4.5-PRERELEASE #0: Tue Dec 25 02:13:41 EST 2001
root@zf3:/usr/src/sys/compile/ZFREE
kern.maxvnodes: 68412
kern.maxproc: 4116
kern.maxfiles: 8232
kern.argmax: 65536
kern.securelevel: -1
kern.hostname: zfreeVA3.isprime.com
kern.hostid: 0
kern.clockrate: { hz = 100, tick = 1, tickadj = 5, profhz = 1024,
stathz
= 128 }
kern.posix1version: 199309
kern.ngroups: 16
kern.job_control: 1
kern.saved_ids: 0
kern.boottime: { sec = 1009265636, usec = 169977 } Tue Dec 25 02:33:56
2001
kern.domainname:
kern.osreldate: 45
kern.bootfile: /kernel
kern.maxfilesperproc: 7408
kern.maxprocperuid: 3704
kern.dumpdev:
kern.ipc.maxsockbuf: 2097152
kern.ipc.sockbuf_waste_factor: 8
kern.ipc.somaxconn: 10240
kern.ipc.max_linkhdr: 16
kern.ipc.max_protohdr: 40
kern.ipc.max_hdr: 56
kern.ipc.max_datalen: 156
kern.ipc.nmbclusters: 65536
kern.ipc.semmap: 30
kern.ipc.semmni: 10
kern.ipc.semmns: 60
kern.ipc.semmnu: 30
kern.ipc.semmsl: 60
kern.ipc.semopm: 100
kern.ipc.semume: 10
kern.ipc.semusz: 92
kern.ipc.semvmx: 32767
kern.ipc.semaem: 16384
kern.ipc.shmmax: 40960
kern.ipc.shmmin: 1
kern.ipc.shmmni: 192
kern.ipc.shmseg: 128
kern.ipc.shmall: 8192
kern.ipc.shm_use_phys: 0
kern.ipc.mbuf_wait: 32
kern.ipc.mbtypes: 3589 3759 76 0 0 0 0 0 0 0 0 0 0 0 0 0
kern.ipc.nmbufs: 262144
kern.ipc.maxsockets: 65536
kern.dummy: 0
kern.ps_strings: 3217031152
kern.usrstack: 3217031168
kern.logsigexit: 1
kern.cam.da.retry_count: 4
kern.cam.da.default_timeout: 60
kern.fallback_elf_brand: -1
kern.init_path: /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall
Re: libfetch.so.2 should be included in src/lib/compat/compat4x.*
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: The only libfetch consumers (that I know of) are fetch(1) and the pkg tools. Old binaries will still work on an upgraded system (which will still have libfetch.so.2) but not on a fresh install (which will lack libfetch.so.2), but both upgraded and freshly installed systems will have up-to-date versions of fetch(1) and the pkg tools. Because fetch(3) is very reasonable (I thank you, DES), I wrote some programs that use libfetch and the programs have some non-experienced users. When the guys will deploy new 4.5-RELEASE systems, they will confuse and contact me because the programs does not work even with compat libraries. I don't want such a waste of time. Moreover, libfetch.so.3 is backward compatible, so a symlink should be sufficient to support old binaries. The reason for the bump is that new binaries will not work with an old library. If symbolic link is sufficient, src/lib/compat/compat4x.i386/Makefile or sysinstall should create one. Please do not expect users to do by hand. -- NIIMI Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.5-PRERELEASE smbfs resolving issues
On Tue, 25 Dec 2001, Yonatan Bokovza wrote: asd# mount_smbfs //guest@asdasd/mp3-i /mnt mount_smbfs: can't get server address: syserr = Operation timed out [Won't resolve with /etc/hosts] asd# mount_smbfs [EMAIL PROTECTED]/mp3-i /mnt mount_smbfs: server name '192.168.100.101' too long ... In the //user@server/share parameter, the server is supposed to be the NetBIOS name of the server, not a hostname or an IP. You should probably use the -I parameter to specify the IP or hostname of the server. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NTPD dumps core in 4.5-PRERELEASE
Ollivier Robert wrote: According to James Housley: 12/22 5am EST. 1 CVSup 12/23 5am EST. The laptop is dumps core on startup only with 12/22 12/23. I don't believe this was doing this before 4.1.0. If I re-run with the exact same parameters after the boot is finished all is well. Attached is the dmesg.boot and some debug information from the core file. This is reproduceable with every reboot on this one machine. When you boot this machine, do you have access to the IP addresses of all your ntp.conf servers/peers ? Actually one of the peers is not accessable, and hasn't been for a while. But if that is causing a seg. fault, I would consider that a programming error. Jim -- /\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ - [EMAIL PROTECTED] http://www.FreeBSD.org The Power to Serve [EMAIL PROTECTED] http://www.TheHousleys.net [EMAIL PROTECTED] http://www.SimTel.Net - It's always a long day, 86400 doesn't fit into a short. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
