Re: finding unmatched quotes in shell scripts
Lyndon Nerenberg wrote: | I've tried a number of syntax-colouring editors, to no avail. The quotes | (single, double, and back) *are* balanced, according to everything I've | thrown the script at. That's why I'm more interested in something that | can actually parse Bourne shell syntax (quiet Terry - I *know* what | you're going to say) and dump out what it thinks the parse tree looks | like. The problem isn't with the quotes being unbalanced, it's something | else that's making the shell ignore one (or more) of those quotes. Surely the simple thing is to put an exit statement in the middle of the script and see which half has the problem? Move the exit statement forwards or backwards in a binary search until the problem leaps out and hits you in the face. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NFS exports under 4.7-RELEASE
I think you are trying to export the same filesystem to the same list of addresses twice, so you get an error saying it is already exported. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NFS exports under 4.7-RELEASE
On Sat, 2002-11-16 at 21:46, Brian Reichert wrote: I hope I'm completely misunderstanding the docs for exports(5) and kin, but here goes: The short form: I have two filesystems I want to export. They're both listed in /etc/exports. The first will be exported just fine, the second yields complaints from mountd about the device being busy. Changing the order of the entries in /etc/exports yields the same symptoms; first one works, second one doesn't. # cat /etc/exports /pub-alldirs -webnfs /annex -alldirs -webnfs Only one filesystem can be WebNFS exported on a computer (that is how webnfs works). Remove -webnfs from one. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: active vn-devices
Ruslan Ermilov wrote, On 11/15/02 09:42: How can I list active (i.e. configured with vnconfig) /dev/vn* devices? No way. Tricky way. Try to configure each vn device - with NO file name requesting NEGATIVE size. If you got EBUSY, the device is configured. If you got EDOM, the device is free. You can also try attach an EACCESS or EPERM unaccesible file. Dan -- Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206 root of FIONet, KolejNET, webmaster of www.freebsd.cz AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Qs about snoop TCP
Dear All I want to know what is Snoop TCP , and Is it implemented on FreeBSD or Not ? After I want to know if There is any Performance Enhancing Proxy on the NET _ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Subscribe
FreeBSD/x86-64 mailing list To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NFS exports under 4.7-RELEASE
On Sun, Nov 17, 2002 at 12:39:07PM +0100, Mattias Pantzare wrote: Only one filesystem can be WebNFS exported on a computer (that is how webnfs works). Remove -webnfs from one. Jeez - I had no idea that was a factor. You're right; removing '-webnfs' from the /annex entry allows both filesystems to be mounted. Now, I have to go read up on webnfs to find out what webnfs really is... Thanks for the pointer. This blows the semantics that I've come to expect from exports(5), though. I may file a PR to have that document tweaked. Thanks again for your help... -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Arp and Route Commands
Hello, I'm new to the list and was hoping maybe someone could help me. These commands work in Linux (and in this order), but not in FreeBSD/Mac OS X as the arp and route commands are different: arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1 arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1 route add -net 10.10.10.0 netmask 255.255.255.0 dev eth1 route add default gw 10.10.10.0 dev eth1 anyone know how i would change these commands to work with the FreeBSD versions of arp and route? Thanks! Karl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Memory corruption in -STABLE on P4/2GHz
Hi there, I'm observing very strange memory corruption problems with 2GHz P4 system running 4.7 (security branch as of today). Under the load (make -j20 buildworld) the compiler or make(1) often die with signal 11. I found in mailing lists that there is similarly looking problem with -current, any chances that -stable is affected as well? Adding `options DISABLE_PSE', as suggested, reduced the likelyhood of the problem, but didn't eliminate it completely (-j20 fails with sig11 from time to time, but much less frequently than without the said option. Any ideas? -Maxim Copyright (c) 1992-2002 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 4.7-RELEASE-p2 #0: Sun Nov 17 05:12:06 PST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/INSTALL Timecounter i8254 frequency 1193182 Hz CPU: Pentium 4 (1990.24-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,b28,ACC real memory = 503250944 (491456K bytes) config en apm0 config q avail memory = 484413440 (473060K bytes) Preloaded elf kernel kernel at 0xc050d000. Preloaded userconfig_script /boot/kernel.conf at 0xc050d09c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 5 entries at 0xc00fdec0 apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: PCI to PCI bridge (vendor=1106 device=b091) at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: S3 model 8d04 graphics accelerator at 0.0 irq 11 ohci0: NEC uPD 9210 USB controller mem 0xec10-0xec100fff irq 11 at device 8.0 on pci0 usb0: OHCI version 1.0 usb0: NEC uPD 9210 USB controller on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: NEC uPD 9210 USB controller mem 0xec101000-0xec101fff irq 5 at device 8.1 on pci0 usb1: OHCI version 1.0 usb1: NEC uPD 9210 USB controller on ohci1 usb1: USB revision 1.0 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: USB controller at 8.2 irq 10 rl0: RealTek 8139 10/100BaseTX port 0xd000-0xd0ff mem 0xec103000-0xec1030ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:4c:77:20:ce miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=1106 device=3147) at device 17.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 8233 ATA133 controller port 0xd400-0xd40f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: unknown card (vendor=0x1106, dev=0x3059) at 17.5 irq 10 orm0: Option ROM at iomem 0xc-0xcbfff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ad0: DMA limited to UDMA33, non-ATA66 cable or device ad0: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata0-master UDMA33 acd0: CDROM HL-DT-ST CD-ROM GCR-8520B at ata1-slave PIO4 Mounting root from ufs:/dev/ad0s2a pid 70813 (make), uid 0: exited on signal 11 (core dumped)
Re: Memory corruption in -STABLE on P4/2GHz
On Sun, Nov 17, 2002 at 23:16:54 +0200, Maxim Sobolev wrote: Hi there, I'm observing very strange memory corruption problems with 2GHz P4 system running 4.7 (security branch as of today). Under the load (make -j20 buildworld) the compiler or make(1) often die with signal 11. I found in mailing lists that there is similarly looking problem with -current, any chances that -stable is affected as well? Adding `options DISABLE_PSE', as suggested, reduced the likelyhood of the problem, but didn't eliminate it completely (-j20 fails with sig11 from time to time, but much less frequently than without the said option. Any ideas? I had similar problems which only disappeared after changing to a non-debug kernel, i.e. without -g. Since then I never had the sig11s (but I ususally build world with -j8, not -j20). Also I didn't try DISABLE_PSE. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Shrinking /(s)bin: A Proposal
Lamont Granquist wrote: RedHat systems have only two statically linked binaries in their systems and it is one of the things that I viscerally hate about RedHat. You have to look on another system or lookup on the net which shell to use instead of /sbin/init and then play around with a massively minimal set of things you can do to the filesystem in order to fix your system. I hate that. I particularly hate that because whenever it comes up I just did something stupid enough to nuke my libc and I'm not a happy camper. I want to just boot into single user and fix the system. Also, the lack of 'mv' being statically linked is what caused me to learn so much about how to recover from libc being nuked on RedHat boxes. Its good to have any common utilities people might think of to use to update libc to be statically linked. Of course I can see where on early-90s era systems, or on embedded systems, you'd want to go with the smallest /[s]bin you can get in which case the buildworld option makes perfect sense. I have no use for this option though. I'm happy to gleefully burn through the 20MB of disk space. 20MB of disk space is cheap these days -- 99% of FreeBSD users will never notice that it is gone... Have you been actually reading this? peter@daintree[2:55pm]/-101 cd /rescue peter@daintree[2:55pm]/rescue-102 file rescue rescue: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.0, statically linked, stripped Note: Static linked. peter@daintree[2:55pm]/rescue-103 file sh sh: symbolic link to rescue peter@daintree[2:55pm]/rescue-104 file cp cp: symbolic link to rescue peter@daintree[2:55pm]/rescue-105 file init init: symbolic link to rescue Adding things like mv etc to this is *trivial*. If you get hosed, and have to drop into single user, we'll arrange it so that $PATH has got /rescue at the beginning. Since adding things like mv to the static linked crunched binary is trivial, you'd actually be seeing an improvement over the bloat case. On Fri, 15 Nov 2002, Peter Wemm wrote: Robert Watson wrote: On Thu, 14 Nov 2002, Doug Rabson wrote: : I'm open to patches for building /[s]bin as dynamic. If you have : time and can coordinate with [EMAIL PROTECTED] to build the patch, I : would appreciate it. % make NOSHARED=NO buildworld No patches necessary. We do this all the time at work, and it works fabulously. I do this for disk based systems that have / and /usr on the same file system too. To do it right for split root/usr installations requires a few patches though. The rtld and the libs required for /[s]bin need to move to / an d compat symlinks created from /usr. A suitable crunchgen'ed binary for /recover would be useful too. I had some local patches that did a subset of this -- moved ld.so to /lib , as well as installing shared libraries to /lib instead of /usr/lib for th e base system. I seem to recall I also had to tweak some defaults in ld.so or rtld or the like, though. I agree that the right path to support full y dynamic systems properly is to adopt the approach taken by NetBSD: provid e a decent /recover with crunchgen, etc. I do use fully dynamic stuff for some local test boxes, makes upgrading libc code for development purposes much easier, as well as supporting dlsym() for /sbin, which is very usefu l in my environment. For what its worth: peter@daintree[4:55pm]/rescue-222# ls -sh@dumpfs@ ipmon@ mount_portalfs@ rm@ [@ dumpon@ ipnat@ mount_std@ rmdir@ adjkerntz@ echo@ kenv@ mount_udf@ route@ atacontrol@ ed@ kill@ mount_umapfs@ routed@ badsect@expr@ kldconfig@ mount_unionfs@ rtsol@ camcontrol@ fdisk@ kldload@mv@ savecore@ cat@fdisk_pc98@ kldstat@natd@ setfacl@ ccdconfig@ fsck@ kldunload@ newfs@ sh@ chio@ fsck_ffs@ ldconfig@ newfs_msdos@shutdown@ chmod@ fsck_msdosfs@ ln@ nfsiod@ slattach@ clri@ fsdb@ ls@ nos-tun@sleep@ comcontrol@ fsirand@mca@pax@spppcontrol @ conscontrol@gbde@ md5@ping@ startslip@ cp@ getfacl@mdconfig@ ping6@ stty@ date@ gpt@mdmfs@ ps@ swapon@ dd@ growfs@ mkdir@ pwd@sync@ devd@ hostname@ mknod@ quotacheck@ sysctl@ devfs@ ifconfig@ mount@ raidctl@test@ df@ init@ mount_cd9660@ rcorder@tunefs@ dhclient@ ip6fw@
Re: Memory corruption in -STABLE on P4/2GHz
I had similar problems. Terry Lambert reports that there is a bug in the P4. DISABLE_PSE and the other work-arounds mentioned didn't help. The work-around that worked for me was to use: options MAXFILES=5 Try that and see if it helps. - Robert Withrow, R.W. Withrow Associates, Swampscott MA, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in -STABLE on P4/2GHz
On Sun, Nov 17, 2002 at 11:16:54PM +0200, Maxim Sobolev wrote: Hi there, I'm observing very strange memory corruption problems with 2GHz P4 system running 4.7 (security branch as of today). Under the load (make -j20 buildworld) the compiler or make(1) often die with signal 11. I found in mailing lists that there is similarly looking problem with -current, any chances that -stable is affected as well? I'm seeing similar errors on -current on my AMD K6-2 machine: CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 384M bytes Write Allocate 15-16M bytes: Enable I am seeing make or /usr/libexec/cc1 intermittently coredump with SIG 11 or SIG 10 errors when trying to do a buildworld. I wasn't sure if it was because I had flaky hardware or not. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
uma issues with ctor/dtor/uminit/fini
Shouldn't the allocator functions take an additional argument WAIT/NOWAIT? Shouldn't the allocator functions also return success/failure that should be propogated back up to the caller in case they fail? Shall I take a shot at this or can you Jeff? I'm not sure I'm comfortable adding an error case to uma_zalloc, but who knows... -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NFS exports under 4.7-RELEASE
Brian Reichert wrote: Now, I have to go read up on webnfs to find out what webnfs really is... RFC2054, RFC2055, RFC2755 (not implemented by FreeBSD). Abstract, RFC2054: This document describes a lightweight binding mechanism that allows NFS clients to obtain service from WebNFS-enabled servers with a minimum of protocol overhead. In removing this overhead, WebNFS clients see benefits in faster response to requests, easy transit of packet filter firewalls and TCP-based proxies, and better server scalability. ...basically: mount-less NFS server by IP address, one per IP address. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NFS exports under 4.7-RELEASE
On Sun, Nov 17, 2002 at 05:36:16PM -0800, Terry Lambert wrote: Brian Reichert wrote: Now, I have to go read up on webnfs to find out what webnfs really is... RFC2054, RFC2055, RFC2755 (not implemented by FreeBSD). Abstract, RFC2054: Gee, you beat me to it, by a mile. Thanks for the pointer... ...basically: mount-less NFS server by IP address, one per IP address. One server per IP address make sense, but only one filesystem exported thusly doesn't. But, I _still_ haven't read the RFCs in question, so hopefully I'll see... -- Terry -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NFS exports under 4.7-RELEASE
Brian Reichert wrote: ...basically: mount-less NFS server by IP address, one per IP address. One server per IP address make sense, but only one filesystem exported thusly doesn't. But, I _still_ haven't read the RFCs in question, so hopefully I'll see... No mount protocol = no way to differentiate mount instances, other than by IP. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: finding unmatched quotes in shell scripts
Lyndon Nerenberg wrote: I've tried a number of syntax-colouring editors, to no avail. The quotes (single, double, and back) *are* balanced, according to everything I've thrown the script at. In addition to the other excellent suggestions, I'd suggest using the syntax highlighting editor, and start deleting quotes here and there. You might find that the de-highlighting happens in places that you don't expect. Also, it might help you to break the program down into smaller functions. That usually makes it easier to locate the errors. Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Golden Stream - Äîïîëíåíèå!
Êîìó íàäîåë - ïðîøó ïðîñòèòü! Òåì, êòî çàèíòåðåñîâàëñÿ GS - ïèøèòå íà [EMAIL PROTECTED] èëè íà ëþáîé èç ðàíåå óêàçàííûõ àäðåñîâ, êðîìå yahoo - åãî óæå íåò. Ñ óâàæåíèåì. Ðàññûëêà ïðîèçâåäåíà â ñîîòâåòñòâèè ñ ÷.4 ñò.29 Êîíñòèòóöèè ÐÔ, ÿâëÿåòñÿ ðàçîâîé, è íå íàâÿçûâàåò ïëàòíûõ óñëóã. Âàø ýëåêòðîííûé àäðåñ ïîëó÷åí èç îòêðûòûõ èñòî÷íèêîâ. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Arp and Route Commands
On Sunday 17 November 2002 13:53, Karl Timmermann wrote: I'm new to the list and was hoping maybe someone could help me. These commands work in Linux (and in this order), but not in FreeBSD/Mac OS X as the arp and route commands are different: arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1 arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1 route add -net 10.10.10.0 netmask 255.255.255.0 dev eth1 route add default gw 10.10.10.0 dev eth1 anyone know how i would change these commands to work with the FreeBSD versions of arp and route? man arp man route ask on -questions and because I'm feeling helpful: arp -s 10.10.10.1 00:00:ca:13:4b:54 arp -s 10.10.10.2 00:00:ca:13:4b:54 route add -net 10.10.10.0 -netmask 255.255.255.0 -interface fxp0 route add default 10.10.10.1 -interface fxp0 FreeBSD's arp doesn't allow you to specify an interface. Adding the same host to the arp table twice is pointless and would probably produce an error, so I changed the addresses. Replace fxp0 with the name of the interface in question. With a netmask of 255.255.255.0, 10.10.10.0 is a network address and can't (or at least shouldn't) be used as a router or client address (changed in the example above). I'm forced to wonder why you would want to run this sequence of commands and if there isn't a better way to achieve the desired result. Please reply off-list if you feel so inclined. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in -STABLE on P4/2GHz
On Sun, Nov 17, 2002 at 07:54:48PM -0500, Craig Rodrigues wrote: On Sun, Nov 17, 2002 at 11:16:54PM +0200, Maxim Sobolev wrote: Hi there, I'm observing very strange memory corruption problems with 2GHz P4 system running 4.7 (security branch as of today). Under the load (make -j20 buildworld) the compiler or make(1) often die with signal 11. I found in mailing lists that there is similarly looking problem with -current, any chances that -stable is affected as well? I'm seeing similar errors on -current on my AMD K6-2 machine: CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 384M bytes Write Allocate 15-16M bytes: Enable I am seeing make or /usr/libexec/cc1 intermittently coredump with SIG 11 or SIG 10 errors when trying to do a buildworld. I wasn't sure if it was because I had flaky hardware or not. It is likely that those aren't related. Mine K6-2/500, which I had while back, was also causing SIG 11, due to overheating. Another possible reason is memory - you should check that you have PC100, not PC66 installed, because K6-2/400 runs with 100MHz FSB. In this case, the possible overheating is eliminated by keeping the case fully opened but it doesn't help much. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Portmap on just the loopback?
Is there a specific reason why one can not bind portmap to only the loopback interface? Portmap has the -h flag, but it automatically inserts 127.0.0.1 to the list if you specify the -h flag. This prevent one from saying 'portmap -h 127.0.0.1' because it takes the command line arg's, adds 127.0.0.1 to the list, loops while there are arguments, and so tries to bind to 127.0.0.1 twice. It errors with 'cannot bind udp: Address already in use', and exits. I fixed it on a box, and it's happily portmapping along with no problems that I can see nor any I can imagine but I have been wrong before. Yes there are tcp_wrappers, et al, and yes, it's RPC not LPC, but it there a specific reason for this behavior? Just curious... -- [EMAIL PROTECTED] 39:FF:7C:52:66:9D:B9:A3 EA:67:3C:7F:D1:B6:30:36 A good sysadmin always carries around a few feet of fiber. If he ever gets lost, he simply drops the fiber on the ground, waits ten minutes, then asks the backhoe operator for directions. -- Bill Bradford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
