RE: Problems with -CURRENT
Howdy, I thought it was just me that had the problem, but it appears to be the recent dirpref commit. I managed to get a working system by booting to single user, fsck'ing all partitions, then using tunefs to specify the number of files per directory to be greater than zero. I also specified the -A flag to update all superblock entries, as subsequent fsck's errored with first superblock different to first alternate. In summary: fsck all partitions tunefs -A -s all partitions, where n > 0 Hope this helps. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Matthew Schlegel > Sent: Saturday, 14 April 2001 4:05 > To: [EMAIL PROTECTED] > Subject: Problems with -CURRENT > > > I have been working on doing an update to the latest -CURRENT > (last cvsup for > this upgrade attempt was this morning at about 9:30 PDT) for the last > couple days from : > FreeBSD msops.crossgain.com 5.0-CURRENT FreeBSD 5.0-CURRENT > #0: Wed Jun 28 13:23:44 PDT 2000 > > Right now I can boot into single user mode just fine, but the > moment any > process requests an inode on my / partition, I get a kernel > panic (page > fault). Right now the world consistantly falls apart in > ffs_valloc, but I'm > not sure how to further track it down at this point. > > I am able to get inodes on another partition that was created > using the newfs > from the new world, so I'm wondering if there may have been > some filesystem > change between June of last year and now that could be > causing the problems. > I would appreciate it if someone could point me in the right > direction with > this so I can get moved over. > > > Stack trace with pointers resolved: > ffs_valloc(0, 8180, 21, vcp_create_desc 8) > ufs_makeinode > ufs_create > ufs_vnoperate > vn_open > open > > The config I am using is attached to this email as well. > > -- > Matthew Schlegel > Give yourself a raise.. Every month: > http://www.ezinfocenter.com/290234.10/FREE > > Encryption Keys: > Type KeyID Created Fingerprint > PGP DSS 0x30AFD26D 1998-08-20 FC89 1E36 353E BDAA FF81 > DD30 A7B0 3942 30AF D26D > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS export to netgroup with duplicate hosts
:on BSD, and we can do more finetuning than on Solaris itself. Also :mountd and export seems to support more features than in Solaris, :according to the manpage. : :Could this export restriction change in future with nfsv4, when nfs :does get stateful (I've heard about that the stateless behaviour will :go away with nfsdv4) ... ? I do not know much about the internals of :nfsv4 ... : :Martin I don't know anything about NFSv4 myself, but if it's stateful I suppose it would be possible. Still unlikely, though, since UNIX by definition makes enough of a distinction between file handles and directory paths that directory-path-based perms would be difficult. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: miibus/fxp intel etherexpress broken
Darren Henderson writes:
>
> I had a functional install of -current which was created back on Jan 11th of
> this year.
>
> I cvsup'd yesterday (4/12. I had also tried this on 4/4) fixxed what I
> needed too from UPDATING and RELNOTES, built and installed world and a new
> kernel.
>
> fxp now fails.
>
> ata1: at 0x170 irq 15 on atapci0
<...>
> fxp0: port 0x5400-0x541f mem
>0x6000-0x600f,0x6010-0x60100fff irq 15 at device 11.0 on pci0
> fxp0: could not map interrupt
> device_probe_and_attach: fxp0 attach returned 6
> isa0: unexpected small tag 14
This has nothing to do with fxp. The problem is that irq15 is shared
between ata1 and fxp0 & the ata driver doesn't want to share
interrupts because some older boards will somehow barf when
sharing irqs between ata and other devices.
Try this patch (I haven't tested it myself)
Index: dev/ata/ata-pci.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-pci.c,v
retrieving revision 1.3
diff -u -r1.3 ata-pci.c
--- dev/ata/ata-pci.c 2001/03/19 13:31:58 1.3
+++ dev/ata/ata-pci.c 2001/04/13 18:32:21
@@ -508,7 +508,7 @@
return BUS_ALLOC_RESOURCE(device_get_parent(dev), child,
SYS_RES_IRQ, rid,
- irq, irq, 1, flags & ~RF_SHAREABLE);
+ irq, irq, 1, flags);
#endif
}
else {
Drew
--
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Problems with -CURRENT
On 13-Apr-01 Matthew Schlegel wrote: > I have been working on doing an update to the latest -CURRENT (last cvsup for > this upgrade attempt was this morning at about 9:30 PDT) for the last > couple days from : > FreeBSD msops.crossgain.com 5.0-CURRENT FreeBSD 5.0-CURRENT >#0: Wed Jun 28 13:23:44 PDT 2000 > > Right now I can boot into single user mode just fine, but the moment any > process requests an inode on my / partition, I get a kernel panic (page > fault). Right now the world consistantly falls apart in ffs_valloc, but I'm > not sure how to further track it down at this point. > > I am able to get inodes on another partition that was created using the newfs > from the new world, so I'm wondering if there may have been some filesystem > change between June of last year and now that could be causing the problems. > I would appreciate it if someone could point me in the right direction with > this so I can get moved over. Rebuild and install fsck and fsck your filesystems. This is the dirpref stuff most likely biting you. Warner, we should probably add a warning about the dirpref changes to UPDATING since if you fsck a filesystem with the old fsck and new kernel and you overwrite your superblock with the alternate you hose the filesystem resuling in these panics. :( > Stack trace with pointers resolved: > ffs_valloc(0, 8180, 21, vcp_create_desc 8) > ufs_makeinode > ufs_create > ufs_vnoperate > vn_open > open > > The config I am using is attached to this email as well. > > -- > Matthew Schlegel > Give yourself a raise.. Every month: > http://www.ezinfocenter.com/290234.10/FREE > > Encryption Keys: > Type KeyID Created Fingerprint > PGP DSS 0x30AFD26D 1998-08-20 FC89 1E36 353E BDAA FF81 DD30 A7B0 3942 > 30AF D26D -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with -CURRENT
I have been working on doing an update to the latest -CURRENT (last cvsup for this upgrade attempt was this morning at about 9:30 PDT) for the last couple days from : FreeBSD msops.crossgain.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Jun 28 13:23:44 PDT 2000 Right now I can boot into single user mode just fine, but the moment any process requests an inode on my / partition, I get a kernel panic (page fault). Right now the world consistantly falls apart in ffs_valloc, but I'm not sure how to further track it down at this point. I am able to get inodes on another partition that was created using the newfs from the new world, so I'm wondering if there may have been some filesystem change between June of last year and now that could be causing the problems. I would appreciate it if someone could point me in the right direction with this so I can get moved over. Stack trace with pointers resolved: ffs_valloc(0, 8180, 21, vcp_create_desc 8) ufs_makeinode ufs_create ufs_vnoperate vn_open open The config I am using is attached to this email as well. -- Matthew Schlegel Give yourself a raise.. Every month: http://www.ezinfocenter.com/290234.10/FREE Encryption Keys: Type KeyID Created Fingerprint PGP DSS 0x30AFD26D 1998-08-20 FC89 1E36 353E BDAA FF81 DD30 A7B0 3942 30AF D26D # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.306 2001/03/16 11:52:25 sos Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident MSOPS maxusers32 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options MATH_EMULATE#Support for x87 emulation options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options DEVFS #Device Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev options DDB # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family #device ncr
Re: readline.h 1.12 incompatible with gdb.291/gdb/top.c 1.2, I think
On Fri, Apr 13, 2001 at 06:40:42PM +0400, Andrey A. Chernov wrote: > Yes. Backward-compatible prototypes was enabled very recently > to help old applications. I didn't expect it break gdb compilation again I need to update my box to test. It will probably be 2-3 hours and it will be fixed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ISO image available?
> Do you have a script that will pull in the latest snapshot and write an > ISO image? This would be a nice addition to the supplied documentation. No, since I don't do release engineering that way, but someone else should certainly feel free to do this. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
miibus/fxp intel etherexpress broken
I had a functional install of -current which was created back on Jan 11th of this year. I cvsup'd yesterday (4/12. I had also tried this on 4/4) fixxed what I needed too from UPDATING and RELNOTES, built and installed world and a new kernel. fxp now fails. Searching back I saw that fxp now requires miibus and that is in there but I don't see anything else that has changed. Is there something else I need to tweak to get this to work again? Kernel config and dmesg output below... MOXIE config - # machine i386 cpu I586_CPU ident MOXIE maxusers32 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev options DIAGNOSTIC # firewall options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 device random device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # SCSI Controllers device adv # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc device atkbd device psm device vga # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc # Floating point support - do not disable. device npx # Serial (COM) ports device sio # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer # PCI Ethernet NICs. device miibus device fxp # Intel EtherExpress PRO/100B (82557, 82558) device ep # Pseudo devices - the number indicates how many units to allocated. device loop# Network loopback device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf #Berkeley packet filter dmesg - Rebooting... Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Apr 13 09:33:04 EDT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOXIE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166194014 Hz CPU: Pentium/P55C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping = 4 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 61964288 (60512K bytes) Preloaded elf kernel "kernel" at 0xc034b000. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0xfff0-0x at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170
Re: readline.h 1.12 incompatible with gdb.291/gdb/top.c 1.2, I think
On Fri, Apr 13, 2001 at 18:40:42 +0400, Andrey A. Chernov wrote: > On Fri, Apr 13, 2001 at 07:27:53 -0700, David Wolfskill wrote: > > Yes. Backward-compatible prototypes was enabled very recently > to help old applications. I didn't expect it break gdb compilation again > :-( > > David, please remove offending prototype from top.c I mean David O'Brien -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: readline.h 1.12 incompatible with gdb.291/gdb/top.c 1.2, I think
On Fri, Apr 13, 2001 at 07:27:53 -0700, David Wolfskill wrote: Yes. Backward-compatible prototypes was enabled very recently to help old applications. I didn't expect it break gdb compilation again :-( David, please remove offending prototype from top.c > Others have mentioned that world appears broken on -current; happened > to me as well, and it appears that r1.12 of libreadline/readline.h has > exposed a definition of filename_completion_function() that conflicts > with the one in gdb.291/gdb/top.c: > > src/contrib/libreadline/readline.h 2001/04/12 17:18:46 1.12: > 419: extern char *filename_completion_function __P((const char *, int)); > > src/contrib/gdb.291/gdb/top.c 1999/08/20 02:58:161.2: > 1540: extern char *filename_completion_function PARAMS ((char *, int)); > > > Tail end of failing part of "make buildworld": > > cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb >-I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include >-Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config >-DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb >-I/usr/obj/usr/src/i386/usr/include/readline -DNO_MMALLOC >-I/usr/obj/usr/src/i386/usr/include -c >/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c > /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In function >`filename_completer': > /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:1540: >conflicting types for `filename_completion_function' > /usr/obj/usr/src/i386/usr/include/readline/readline.h:419: previous declaration of >`filename_completion_function' > /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:1540: >warning: extern declaration of `filename_completion_function' doesn't match global one > /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In function >`init_main': > /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:3467: >warning: assignment from incompatible pointer type > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/binutils/gdb. > *** Error code 1 > > > Recent CVSups done: > > CVSup started from cvsup14.freebsd.org at Thu Apr 12 03:47:00 PDT 2001 > CVSup ended from cvsup14.freebsd.org at Thu Apr 12 03:53:13 PDT 2001 > CVSup started from cvsup14.freebsd.org at Fri Apr 13 03:47:01 PDT 2001 > CVSup ended from cvsup14.freebsd.org at Fri Apr 13 03:52:01 PDT 2001 > > (and I haven't seen any other activity involving src/contrib since). > > Hope this is useful, > david > -- > David H. Wolfskill[EMAIL PROTECTED] > As a computing professional, I believe it would be unethical for me to > advise, recommend, or support the use (save possibly for personal > amusement) of any product that is or depends on any Microsoft product. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
readline.h 1.12 incompatible with gdb.291/gdb/top.c 1.2, I think
Others have mentioned that world appears broken on -current; happened to me as well, and it appears that r1.12 of libreadline/readline.h has exposed a definition of filename_completion_function() that conflicts with the one in gdb.291/gdb/top.c: src/contrib/libreadline/readline.h 2001/04/12 17:18:46 1.12: 419: extern char *filename_completion_function __P((const char *, int)); src/contrib/gdb.291/gdb/top.c 1999/08/20 02:58:161.2: 1540: extern char *filename_completion_function PARAMS ((char *, int)); Tail end of failing part of "make buildworld": cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In function `filename_completer': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:1540: conflicting types for `filename_completion_function' /usr/obj/usr/src/i386/usr/include/readline/readline.h:419: previous declaration of `filename_completion_function' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:1540: warning: extern declaration of `filename_completion_function' doesn't match global one /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In function `init_main': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:3467: warning: assignment from incompatible pointer type *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/gdb. *** Error code 1 Recent CVSups done: CVSup started from cvsup14.freebsd.org at Thu Apr 12 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Thu Apr 12 03:53:13 PDT 2001 CVSup started from cvsup14.freebsd.org at Fri Apr 13 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Fri Apr 13 03:52:01 PDT 2001 (and I haven't seen any other activity involving src/contrib since). Hope this is useful, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SOMAXCONN -- not tunable?
< said: > Actually, the correct fix is most likely to redefine it to -1. :) POSIX.1-200x draft 5 has this to say: Implementations shall support values of backlog up to SOMAXCONN, defined in If listen( ) is called with a backlog argument value that is less than 0, the function behaves as if it had been called with a backlog argument value of 0. A backlog argument of 0 may allow the socket to accept connections, in which case the length of the listen queue may be set to an implementation-defined minimum value. So, SOMAXCONN is supposed to be a minimum maximum. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SOMAXCONN -- not tunable?
On Fri, 13 Apr 2001, Alfred Perlstein wrote: > * Bruce Evans <[EMAIL PROTECTED]> [010412 22:25] wrote: > > Changing the actual limit using either the sysctl or an option breaks > > SOMAXCONN. I think the correct fix is to never define it change > > whatever uses it to use sysconf(_SC_SOMAXCONN). Similarly for all > > other manifest constants that aren't actually constant. > > Actually, the correct fix is most likely to redefine it to -1. :) > > Either that or remove it from the namespace. Or just leave it alone, > afaik listen called with a backlog larger than the sysctl limit > just truncates it down to that limit. Or change it to a large positive value, maybe INT_MAX, and prevent the sysctl from increasing it above this. This would be reduced to the actual limit in the same way as -1 is modified to that limit, but might seem to be less preposterous to applications that look too closely at the value. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SOMAXCONN -- not tunable?
* Bruce Evans <[EMAIL PROTECTED]> [010412 22:25] wrote:
> On Thu, 12 Apr 2001, Jonathan Lemon wrote:
>
> > In article [EMAIL PROTECTED]>
>you write:
> > >Here are patches to make SOMAXCONN tunable from the config files.
> > >
> > >Right now, it's not possible to override SOMAXCONN.
> >
> > sysctl -w kern.ipc.somxconn=1024
> >
> > SOMAXCONN is just a compile time default, and yes it is not
> > currently tunable at config time. Does it really have to be?
>
> Of course it doesn't have to be tunable at config time.
>
> > Just stick it in /etc/sysctl.conf, and it gets set before most
> > things are started in the system.
>
> Changing the actual limit using either the sysctl or an option breaks
> SOMAXCONN. I think the correct fix is to never define it change
> whatever uses it to use sysconf(_SC_SOMAXCONN). Similarly for all
> other manifest constants that aren't actually constant.
Actually, the correct fix is most likely to redefine it to -1. :)
Either that or remove it from the namespace. Or just leave it alone,
afaik listen called with a backlog larger than the sysctl limit
just truncates it down to that limit.
What do you think?
/usr/src % grep -r SOMAXCON *
contrib/perl5/ext/Socket/Socket.pm: SOMAXCONN
contrib/perl5/ext/Socket/Socket.pm:sub SOMAXCONN();
contrib/perl5/ext/Socket/Socket.xs: if (strEQ(name, "SOMAXCONN"))
contrib/perl5/ext/Socket/Socket.xs:#ifdef SOMAXCONN
contrib/perl5/ext/Socket/Socket.xs: return SOMAXCONN;
contrib/perl5/lib/Exporter.pm:use Socket qw(!/^[AP]F_/ !SOMAXCONN !SOL_SOCKE
T);
contrib/perl5/pod/perlipc.pod:listen(Server,SOMAXCONN)
|| die "listen: $!";
contrib/perl5/pod/perlipc.pod:listen(Server,SOMAXCONN)
|| die "listen: $!";
contrib/perl5/pod/perlipc.pod:listen(Server,SOMAXCONN)
|| die "listen: $!";
contrib/perl5/pod/perlipc.pod:is SOMAXCONN.
contrib/perl5/pod/perlipc.pod: Listen=> SOM
AXCONN,
contrib/perl5/t/lib/ph.t:SOCK_RAW SOCK_RDM SOCK_SEQPACKET SOCK_STREAM SOL_SO
CKET SOMAXCONN
contrib/sendmail/libmilter/libmilter.h:#if SOMAXCONN > 20
contrib/sendmail/libmilter/libmilter.h:# define MI_SOMAXCONNSOMAXCONN
contrib/sendmail/libmilter/libmilter.h:#else /* SOMAXCONN */
contrib/sendmail/libmilter/libmilter.h:# define MI_SOMAXCONN20
contrib/sendmail/libmilter/libmilter.h:#endif /* SOMAXCONN */
contrib/sendmail/libmilter/main.c:static int backlog= MI_SOMAXCONN;
crypto/heimdal/kadmin/kadm_conn.c: if (listen (s, SOMAXCONN) < 0) {
crypto/heimdal/kdc/connect.c:if(type == SOCK_STREAM && listen(d->s, SOMAXCON
N) < 0){
crypto/heimdal/lib/kadm5/ipropd_master.c:if (listen(fd, SOMAXCONN) < 0)
crypto/heimdal/lib/roken/mini_inetd.c: if (listen (fds[i], SOMAXCONN) < 0)
crypto/heimdal/lib/roken/roken-common.h:#ifndef SOMAXCONN
crypto/heimdal/lib/roken/roken-common.h:#define SOMAXCONN 5
crypto/kerberosIV/ChangeLog:* appl/kx/kx.h: Remove SOMAXCONN and add KX_PORT
crypto/kerberosIV/ChangeLog:fallback definitions for SOMAXCONN, STDIN_FILENO
, and
crypto/kerberosIV/appl/kx/common.c: && listen (s[i].fd, SOMAXCONN) < 0)
crypto/kerberosIV/appl/kx/kxd.c:if (listen (sock, SOMAXCONN) < 0) {
crypto/kerberosIV/kadmin/admin_server.c:if (listen(admin_fd, SOMAXCONN) < 0)
crypto/kerberosIV/lib/roken/mini_inetd.c: if(listen(s, SOMAXCONN) < 0){
crypto/kerberosIV/lib/roken/mini_inetd.c: if(listen(s, SOMAXCONN) < 0){
crypto/kerberosIV/lib/roken/roken-common.h:#ifndef SOMAXCONN
crypto/kerberosIV/lib/roken/roken-common.h:#define SOMAXCONN 5
crypto/kerberosIV/server/kerberos.c:listen(sock, SOMAXCONN);
crypto/kerberosIV/slave/kpropd.c:ret = listen(s, SOMAXCONN);
crypto/openssl/crypto/bio/b_sock.c:#define MAX_LISTEN SOMAXCONN
lib/libc/net/getaddrinfo.3: if (listen(s[nsock], SOMAXCONN) < 0) {
lib/libc/rpc/rpc_soc.c: _listen(fd, SOMAXCONN);
lib/libc/rpc/svc_generic.c: _listen(fd, SOMAXCONN);
sbin/mountd/mountd.c: listen(tcpsock, SOMAXCONN);
sbin/mountd/mountd.c: listen(tcp6sock, SOMAXCONN);
sys/conf/options:SOMAXCONN opt_inet.h
sys/kern/uipc_socket.c:static int somaxconn = SOMAXCONN;
sys/kern/uipc_socket.c:SYSCTL_INT(_kern_ipc, KIPC_SOMAXCONN, somaxconn, CTLFLAG_
RW,
sys/sys/socket.h:#ifndefSOMAXCONN
sys/sys/socket.h:#defineSOMAXCONN 128
sys/sys/sysctl.h:#defineKIPC_SOMAXCONN 3 /* int: max leng
th of connection q */
usr.sbin/rpcbind/rpcbind.c: listen(fd, SOMAXCONN);
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
http://www.egr.unlv.edu/~slumos/on-netbsd.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Buildworld failure. [Re: make release Börked...]
My buildworld today also fails at gdb. cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In function `filename_completer': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:1540: conflicting types for `filename_completion_function' /usr/obj/usr/src/i386/usr/include/readline/readline.h:419: previous declaration of `filename_completion_function' /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:1540: warning: extern declaration of `filename_completion_function' doesn't match global one /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c: In function `init_main': /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/top.c:3467: warning: assignment from incompatible pointer type *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/gdb. > In <63985.987146712@critter> > [EMAIL PROTECTED] (Poul-Henning Kamp) wrote: ===> gnu/usr.bin/binutils/gdb PHK> install -c -s -o root -g wheel -m 555 gdb /syv/release/usr/libexec/elf PHK> install: gdb: No such file or directory PHK> *** Error code 71 PHK> Stop in /syv/src/gnu/usr.bin/binutils/gdb. PHK> *** Error code 1 PHK> : I think you also failed the buildworld. -- NAKAJI Hiroyuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release Börked...
===> gnu/usr.bin/binutils/gdb install -c -s -o root -g wheel -m 555 gdb /syv/release/usr/libexec/elf install: gdb: No such file or directory *** Error code 71 Stop in /syv/src/gnu/usr.bin/binutils/gdb. *** Error code 1 : -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
