Re: SMP on FreeBSD 6.x and 7.0: Worth doing?
It's Tue, Dec 25, 2007 at 12:00 . I'm in a small dim room with doors labeled "Dungeon" and "Forbidden". There is noise, the door marked Dungeon flies open and [EMAIL PROTECTED] SHOUTS: > Date: Mon, 24 Dec 2007 08:49:36 -0700 > From: Brett Glass <[EMAIL PROTECTED]> > Subject: Re: SMP on FreeBSD 6.x and 7.0: Worth doing? > To: Scott Long <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > At 07:14 AM 12/24/2007, Scott Long wrote: > >Brett, > >There could be several problems here: > >1. WITNESS, INVARIANTS, malloc debugging. Are any of these > >turned on for you? I don't recall if malloc debugging got > >turned off yet for the 7.0 snapshots. > I nuked debugging when I recompiled the kernel with SCHED_ULE. > >2. Disk subsystem. What kind of disk controller are you using? > >Not all drivers work well in FreeBSD. Are linux and freebsd > >using identical hardware? > They were. The drives are SATA. That still doesn't tell us if the drives are identical in throughput. Unless the drives are the same model/manufacturer, you should go to the manufacturers web-site for both drives, and look for the technical specs. THen you need to look for the speed of data transfer from the platter to the internal memory. I've seen [ in the past ] drives with lower revolutions per minute out-perform faster rotating drives because the slower drive had a better head design and could transfer data much faster. If this task is not up to you perhaps you could post the make/model number of the drives on both systems. Without knowing the sub-system capability you could be misleading yourself with other tests. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with 'periodic' in 4.11 p-24
On or about Thu, Sep 13, 2007 at 06:25 , while attempting a Zarathustra emulation Luke Hollins thus spake: > Can you post your crontab? Maybe one line has the username twice . Boy - that was the hint that helped me find the problem. How I did this I do not know, but the /etc/crontab was duplicated in /var/cron/tabs/root. That was why the 'root: not found' message occured as the normal cron doesn't use that. I still don't know how I did this - particularly after admining FreeBSD systems since 1995. Maybe I did it in my sleep. But thanks for the comment as that put me on the correct track. Bill > > Bill Vermillion wrote: > > I just updated a 4.11 machine to patch level 24. Somehow I had > > overlooked that machine earlier as it's so stable and only > > is handling web pages, secondary dns and secondary mail. > > > > I've checked everthing I can think of but now all the scripts > > that are run from the root crontab - with the user of 'root' as > > shipped in the distrubution now give me error messages. > > > > The messages are from the atrun daemon. > > > > Here is the message I'm getting just as I bounced it to this > > account. > > > > Theone difference I see in this is that the Subject line > > when viewed in mutt on the original machine has > > root?/usr/libexec/atrun. > > > > -- > > Message-Id: <[EMAIL PROTECTED]> > > From: [EMAIL PROTECTED] (Cron Daemon) > > To: [EMAIL PROTECTED] > > Subject: Cron <[EMAIL PROTECTED]> root /usr/libexec/atrun > > X-Cron-Env: > > X-Cron-Env: > > X-Cron-Env: > > X-Cron-Env: <[EMAIL PROTECTED]> > > X-Cron-Env: > > X-Cron-Env: > > X-UIDL: EO^"!?>h"!Y(@"!+&N"! > > > > root: not found > > > > -- > > > > I've checked everywhere I can think of. I've even added > > the MAILTO line in the crontab with an FQDN address. That didn't > > help either. > > > > It must be something simple I've overlooked or else I'd have seen > > reports of this before. > > > > The cvsup is only for the RELEASE - so nothing is there that > > would be added after the last security update to that last year. > > > > I'm sorry this is so late in time frame of 4.11 - but as I said - > > for some reason this is one server I inadvertantly overlooked. > > Normally the OS gets updated the day any security changes are made. > > > > Thanks > > > > Bill > > > > > -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with 'periodic' in 4.11 p-24
I just updated a 4.11 machine to patch level 24. Somehow I had overlooked that machine earlier as it's so stable and only is handling web pages, secondary dns and secondary mail. I've checked everthing I can think of but now all the scripts that are run from the root crontab - with the user of 'root' as shipped in the distrubution now give me error messages. The messages are from the atrun daemon. Here is the message I'm getting just as I bounced it to this account. Theone difference I see in this is that the Subject line when viewed in mutt on the original machine has root?/usr/libexec/atrun. -- Message-Id: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: Cron <[EMAIL PROTECTED]> root /usr/libexec/atrun X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: <[EMAIL PROTECTED]> X-Cron-Env: X-Cron-Env: X-UIDL: EO^"!?>h"!Y(@"!+&N"! root: not found -- I've checked everywhere I can think of. I've even added the MAILTO line in the crontab with an FQDN address. That didn't help either. It must be something simple I've overlooked or else I'd have seen reports of this before. The cvsup is only for the RELEASE - so nothing is there that would be added after the last security update to that last year. I'm sorry this is so late in time frame of 4.11 - but as I said - for some reason this is one server I inadvertantly overlooked. Normally the OS gets updated the day any security changes are made. Thanks Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld errors on 6.2p6
On Sun, Jul 29, 2007 at 12:00 [EMAIL PROTECTED] saw "Error reading FAT table? Try SKINNY table?" And promptly said: > Date: Sat, 28 Jul 2007 22:58:45 -0400 > From: Bill Vermillion <[EMAIL PROTECTED]> > Subject: buildworld errors on 6.2p6 > To: freebsd-stable@freebsd.org > I just DL'ed the latest sources for 6.2 p6. I've compiled > and during the buildworld I get this error. I picked up > the nohup.out at the library area. If you need more info let me > know. > I built 6.2p6 on another machine a week or so ago and had no > problems. I removed all of /usr/obj just in case and tried again > and got the identical errors. I ensure that the times on my > machine were correct. > Where should I start to look for the problem - if you can tell from > this. If you need more info just let me know what you need. > Bill Drat. Re-read the UPDATING again and found that I had missed the part about env -i. It's fixed and running. Sorry for the excess noise. I'll try to do better next time. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld errors on 6.2p6
e /usr/src/lib/libmagic/../../contrib/file/Magdir/zilog /usr/src/lib/libmagic/../../contrib/file/Magdir/sgi /usr/src/lib/libmagic/../../contrib/file/Magdir/sequent /usr/src/lib/libmagic/../../contrib/file/Magdir/blit /usr/src/lib/libmagic/../../contrib/file/Magdir/impulse /usr/src/lib/libmagic/../../contrib/file/Magdir/island /usr/src/lib/libmagic/../../contrib/file/Magdir/maple /usr/src/lib/libmagic/../../contrib/file/Magdir/os9 /usr/src/lib/libmagic/../../contrib/file/Magdir/pkgadd /usr/src/lib/libmagic/../../contrib/file/Magdir/xo65 /usr/src/lib/libmagic/../../contrib/file/Magdir/virtutech /usr/src/lib/libmagic/../../contrib/file/Magdir/uuencode /usr/src/lib/libmagic/../../contrib/file/Magdir/amanda /usr/src/lib/libmagic/../../contrib/file/Magdir/audio /usr/src/lib/libmagic/../../contrib/file/Magdir/bsdi /usr/src/lib/libmagic/../../contrib/file/Magdir/fcs /usr/src/lib/libmagic/../../contrib/file/Magdir/intel /usr/src/lib/libmagic/../../contrib/file/Magdir/netbsd /usr/src/lib/libmagic/../../contrib/file/Magdir/riff /usr/src/lib/libmagic/../../contrib/file/Magdir/console /usr/src/lib/libmagic/../../contrib/file/Magdir/lecter /usr/src/lib/libmagic/../../contrib/file/Magdir/visx /usr/src/lib/libmagic/../../contrib/file/Magdir/varied.script /usr/src/lib/libmagic/../../contrib/file/Magdir/ti-8x /usr/src/lib/libmagic/../../contrib/file/Magdir/c-lang /usr/src/lib/libmagic/../../contrib/file/Magdir/digital /usr/src/lib/libmagic/../../contrib/file/Magdir/dolby /usr/src/lib/libmagic/../../contrib/file/Magdir/grace /usr/src/lib/libmagic/../../contrib/file/Magdir/ibm370 /usr/src/lib/libmagic/../../contrib/file/Magdir/images /usr/src/lib/libmagic/../../contrib/file/Magdir/tuxedo /usr/src/lib/libmagic/../../contrib/file/Magdir/timezone /usr/src/lib/libmagic/../../contrib/file/Magdir/project /usr/src/lib/libmagic/../../contrib/file/Magdir/cisco /usr/src/lib/libmagic/../../contrib/file/Magdir/mach /usr/src/lib/libmagic/../../contrib/file/Magdir/mkid /usr/src/lib/libmagic/../../contrib/file/Magdir/pgp /usr/src/lib/libmagic/../../contrib/file/Magdir/terminfo /usr/src/lib/libmagic/../../contrib/file/Magdir/apple /usr/src/lib/libmagic/../../contrib/file/Magdir/applix /usr/src/lib/libmagic/../../contrib/file/Magdir/interleaf /usr/src/lib/libmagic/../../contrib/file/Magdir/lisp /usr/src/lib/libmagic/../../contrib/file/Magdir/printer /usr/src/lib/libmagic/../../contrib/file/Magdir/spec /usr/src/lib/libmagic/../../contrib/file/Magdir/sniffer /usr/src/lib/libmagic/../../contrib/file/Magdir/revision /usr/src/lib/libmagic/../../contrib/file/Magdir/amigaos /usr/src/lib/libmagic/../../contrib/file/Magdir/database /usr/src/lib/libmagic/../../contrib/file/Magdir/gringotts /usr/src/lib/libmagic/../../contrib/file/Magdir/pbm /usr/src/lib/libmagic/../../contrib/file/Magdir/plus5 /usr/src/lib/libmagic/../../contrib/file/Magdir/vms /usr/src/lib/libmagic/../../contrib/file/Magdir/python /usr/src/lib/libmagic/../../contrib/file/Magdir/chord /usr/src/lib/libmagic/../../contrib/file/Magdir/ctags /usr/src/lib/libmagic/../../contrib/file/Magdir/human68k /usr/src/lib/libmagic/../../contrib/file/Magdir/pdp /usr/src/lib/libmagic/../../contrib/file/Magdir/sharc /usr/src/lib/libmagic/../../contrib/file/Magdir/pulsar /usr/src/lib/libmagic/../../contrib/file/Magdir/apl /usr/src/lib/libmagic/../../contrib/file/Magdir/communications /usr/src/lib/libmagic/../../contrib/file/Magdir/ncr /usr/src/lib/libmagic/../../contrib/file/Magdir/alpha /usr/src/lib/libmagic/../../contrib/file/Magdir/asterix /usr/src/lib/libmagic/../../contrib/file/Magdir/blender /usr/src/lib/libmagic/../../contrib/file/Magdir/sendmail /usr/src/lib/libmagic/../../contrib/file/Magdir/alliant /usr/src/lib/libmagic/../../contrib/file/Magdir/cddb /usr/src/lib/libmagic/../../contrib/file/Magdir/elf /usr/src/lib/libmagic/../../contrib/file/Magdir/epoc /usr/src/lib/libmagic/../../contrib/file/Magdir/ispell /usr/src/lib/libmagic/../../contrib/file/Magdir/lex /usr/src/lib/libmagic/../../contrib/file/Magdir/mips > magic cc -DHAVE_CONFIG_H -DCOMPILE_ONLY -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -o mkmagic /usr/src/lib/libmagic/../../contrib/file/apprentice.c /usr/src/lib/libmagic/../../contrib/file/funcs.c /usr/src/lib/libmagic/../../contrib/file/magic.c /usr/src/lib/libmagic/../../contrib/file/print.c /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lc *** Error code 1 Stop in /usr/src/lib/libmagic. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. 1247.63 real 1080.79 user 156.11 sys - End forwarded message - -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BPF question
After replacing Richard Tector with a small shell script on Sun, Jul 15, 2007 at 17:56 , the following appeared on stdout: > Bill Vermillion wrote: > >I have been setting the bpf parameter in the kernel configuration > >file to 10 [I forget which program needed that]. Prior to > >that I had usually run with about 4. I also saw that on > >a 4.11 installation I had it set at 40 for 'nessus'. > >My config file had this line. > > > >device bpf 10 > > > >I just updated the system from 6.2-p5 to 6.2-p6, and I got > >a syntax error on that line. > > > >Removing the '10' and leaving the line as: > > > >device bpf > > > >got rid of the syntax error. > > > >I haven't seen, or maybe I just missed it, and information that > >we don't use a numerical parameter anymore. > > > >So has this been changed, or is there a problem in the p6 > >implementation/installation? I suspect it has been changed but I > >have not noticed it. > > > >Thanks. > > > >BIll > With 5.x and upwards, you no longer need to specify the number of > devices required in the kernel configuration. New device nodes are > created/destroyed on the fly by devfs. > Regards, > Richard Thanks. I never went to the 5.x series, just directly from the 4.11 to 6.1 for my servers. I just thought it was strange that 6.2.p5 had no problems with that line, but 6.2.p6 gave a syntax error. Must be code cleanup. I'll make sure it's not in any further kernel configs. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BPF question
I have been setting the bpf parameter in the kernel configuration file to 10 [I forget which program needed that]. Prior to that I had usually run with about 4. I also saw that on a 4.11 installation I had it set at 40 for 'nessus'. My config file had this line. device bpf 10 I just updated the system from 6.2-p5 to 6.2-p6, and I got a syntax error on that line. Removing the '10' and leaving the line as: device bpf got rid of the syntax error. I haven't seen, or maybe I just missed it, and information that we don't use a numerical parameter anymore. So has this been changed, or is there a problem in the p6 implementation/installation? I suspect it has been changed but I have not noticed it. Thanks. BIll -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Native SATA vs. PATA-emulation - differnce?
The door open and in walked trouble - disguised as our our old nemesis [EMAIL PROTECTED], who uttered, at Fri, May 18, 2007 at 15:09 : > Date: Fri, 18 May 2007 11:04:35 +0200 > From: "Patrick M. Hausen" <[EMAIL PROTECTED]> > Subject: Native SATA vs. PATA-emulation - difference? > To: freebsd-stable@freebsd.org ... > Hi, all! > I have a Tyan barebone on my desk that is based on the > ServerWorks HT1000 chipset. It features 4 SATA connectors > and 4 hot plug drive bays. > > I installed FreeBSD on the system with the BIOS settings as > set by the manufacturer. This includes setting the "SATA mode" > to "P-ATA emulation". > > The devices are probed by FreeBSD like this: > > server# dmesg | grep ata > atapci0: port > 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem > 0xff3fe000-0xff3f irq 11 at device 14.0 on pci1 > ata2: on atapci0 > ata3: on atapci0 > atapci1: port > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f irq 11 > at device 14.1 on pci1 > ata4: on atapci1 > ata5: on atapci1 > atapci2: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0 > ata0: on atapci2 > ata1: on atapci2 > acd0: CDROM at ata0-slave UDMA33 > ad4: DMA limited to UDMA33, device found non-ATA66 cable *** That's why you are only getting UDMA33. Change the cable if it's not correct. You might also try changing from P-ATA emulation if that's possible. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Update on buildworld failing with NO_SHARED
Michael Proto said Obscurity in the face of adversity is no dice and while we were trying to figure that out on Mon, Jan 29, 2007 at 14:59 he continued with: > Bill Vermillion wrote: > > OK. > > So I tried using the variable documented in > > /usr/share/examples/etc/make.conf of NO_DYNAMIC_ROOT. > > I rebuilt the world and kernel [I did not remove the /usr/obj/src > > directory this time - maybe that's it] - but all the files > > in /bin and /sbin are still "dynamically linked (users shared libs, > > stripped) when I run 'file' on them. > > Is this strange, or is it just me. > > Bill > > According to the make.conf(5) manpage and the examples/etc/make.conf > file (at least on my 6.2 box), the knob is NO_DYNAMICROOT, not > NO_DYNAMIC_ROOT. I just checked and I see that. I'd swear it was NO_DYNAMIC_ROOT awhile back. But I just checked on a 6.1 and the ..examples/etc/make.conf does also show that I screwed up - as that was dated on Dec 17, while the one on my 6.2 shows a date of today, about an hour ago, when I installed it all. I feel so _ _ _ _ _ _ / ___|| |_ _ _ __| (_) __| | | | | | \___ \| __| | | |/ _` | |/ _` | | | | | ___) | |_| |_| | (_| | | (_| | |_| |_| |/ \__|\__,_|\__,_|_|\__,_| (_) (_) Thanks. I'll try not to be so dense next time, but don't hold me to that. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Update on buildworld failing with NO_SHARED
OK. So I tried using the variable documented in /usr/share/examples/etc/make.conf of NO_DYNAMIC_ROOT. I rebuilt the world and kernel [I did not remove the /usr/obj/src directory this time - maybe that's it] - but all the files in /bin and /sbin are still "dynamically linked (users shared libs, stripped) when I run 'file' on them. Is this strange, or is it just me. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 buildworld fails with NO_SHARED
Deep in the forest in the dark of night on Sat, Jan 27, 2007 at 19:23 with a cackle and an evil grin Scot Hetzel cast another eye of newt into the brew and chanted: > On 1/27/07, Bill Vermillion <[EMAIL PROTECTED]> wrote: > >No real problem there, but that brings up another question. > >If - as documented in make.conf(5) - I put use the variable > >NO_DYNAMIC_ROOT it says "set this is you do not want to link > >/bin and /sbin dynamically". > > > >Would that be the way to build statics in /bin and /sbin > >instead of NO_SHARED. > > > I forgot about that option. Using NO_DYNAMIC_ROOT would be the proper > way to build /bin and /sbin statically, and still have the rest > compied dynamically. > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only > slightly bruised. Thanks for confirming that - the NO_DYNAMIC_ROOT not 'no electonrs were harmed :-) Now - I wonder what should be done with the failures encountered when NO_SHARED is used. I suspect it should be cleaned up, if for no reason than to keep messages/queries such as mine from shwoing up. Thanks again. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 buildworld fails with NO_SHARED
Even though on Fri, Jan 26, 2007 at 11:15 Dan Nelson
realized that everything he says should be taken 'cum grano salis',
he unhesitatingly continued with this missive:
Took me awhile to get some time to try this again - wjv
> In the last episode (Jan 26), Bill Vermillion said:
> > I had wanted to build static binaries in /bin and /sbin - so
> > I set NO_SHARED. The man pages says "... this can be bad. If set
> > every utility that uses bsd.prog.mk will be linked statically."
> > Here is the tail end of the output of make buildworld as I mailed
> > it to me from the machine I was bringing up as we start to replace
> > all the 4.11 servers.
> > > ===> usr.sbin/gstat (all)
> > > cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall
> > > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> > > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> > > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -c
> > > /usr/src/usr.sbin/gstat/gstat.c
> > > cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall
> > > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> > > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> > > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter
> > > -static -o gstat gstat.o -lgeom -ldevstat -lbsdxml -lcurses -ledit
> > > /usr/obj/usr/src/tmp/usr/lib/libgeom.a(geom_xml2tree.o)(.text+0x1c): In
> > > function `StartElement':
> > > : undefined reference to `sbuf_new'
> > > /usr/obj/usr/src/tmp/usr/lib/libdevstat.a(devstat.o)(.text+0x1538): In
> > > function `readkmem':
> > > : undefined reference to `kvm_read'
> > > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x3938): In
> > > function `term_deletechars':
> > > : undefined reference to `tgoto'
> Looks like there are some missing/misordered library dependencies.
> Moving -lcurses after -ledit, and adding -lkvm and -lsbuf fixes it.
> The main thing you lose by statically linking is dlopen(), so nsswitch
> and pam modules from ports won't work. Modules built into libc.a or
> libpam.a (NIS and pam_unix for example) will work. Also, if you're on
> -current you can tell cached to do NSS lookups on behalf of static
> binaries.
>
> Index: Makefile
> ===
> RCS file: /home/ncvs/src/usr.sbin/gstat/Makefile,v
> retrieving revision 1.6.2.1
> diff -u -r1.6.2.1 Makefile
> --- Makefile 10 Jun 2006 15:40:10 - 1.6.2.1
> +++ Makefile 26 Jan 2007 17:00:38 -
> @@ -3,7 +3,7 @@
> PROG=gstat
> MAN= gstat.8
> WARNS?= 5
> -DPADD= ${LIBGEOM} ${LIBDEVSTAT} ${LIBBSDXML} ${LIBCURSES} ${LIBEDIT}
> -LDADD= -lgeom -ldevstat -lbsdxml -lcurses -ledit
> +DPADD= ${LIBGEOM} ${LIBDEVSTAT} ${LIBBSDXML} ${LIBEDIT} ${LIBCURSES}
> +LDADD= -lgeom -ldevstat -lbsdxml -ledit -lcurses -lkvm -lsbuf
>
> .include
> --
> Dan Nelson
> [EMAIL PROTECTED]
That fixed the errors as above. However now I get errors further
down. But first - should this not be fixed in the Makefile.
make.conf(5) says in part using the NO_SHARED ".. can be bad. ..."
I would think the above info about breaking the ports of nsswitch
and the PAM modules wouldn't work might be listed as >some< of the
possibilities instead of 'can be bad'.
The other respondant to this post mentioned that the statically
built pieces of /bin and /sbin are in rescue. I see those are
all in one large file that is linked to all the possible names.
No real problem there, but that brings up another question.
If - as documented in make.conf(5) - I put use the variable
NO_DYNAMIC_ROOT it says "set this is you do not want to link
/bin and /sbin dynamically".
Would that be the way to build statics in /bin and /sbin
instead of NO_SHARED.
And now onto the current thing I see.
I removed all of /usr/obj/src to be sure I started clean.
I had the variable NO_SHARED in /etc/make.conf. The compile
passed the place where it failed before as your fix to the make
file seem to cure that.
Now this is what I see when NO_SHARED is used. This is just
the tail end of the nohup output.
-
cc -O2 -fno-strict-aliasing -pipe -I/usr/src/usr.sbin/pkg_install/info/../lib
-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type
-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wformat=2
-W
6.2 buildworld fails with NO_SHARED
ib/libedit.a(editline.o)(.text+0x3938): In function > `term_deletechars': > : undefined reference to `tgoto' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x3c56): In function > `term_echotc': > : undefined reference to `tgetstr' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x3dbc): In function > `term_echotc': > : undefined reference to `tgoto' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4bd9): In function > `term_set': > : undefined reference to `tgetent' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4bf7): In function > `term_set': > : undefined reference to `tgetflag' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4c0e): In function > `term_set': > : undefined reference to `tgetflag' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4c20): In function > `term_set': > : undefined reference to `tgetflag' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4c32): In function > `term_set': > : undefined reference to `tgetflag' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4c44): In function > `term_set': > : undefined reference to `tgetflag' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4c56): more > undefined references to `tgetflag' follow > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4c68): In function > `term_set': > : undefined reference to `tgetnum' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4c7a): In function > `term_set': > : undefined reference to `tgetnum' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x4cb6): In function > `term_set': > : undefined reference to `tgetstr' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x509f): In function > `term_move_to_char': > : undefined reference to `tgoto' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x5258): In function > `term_move_to_line': > : undefined reference to `tgoto' > /usr/obj/usr/src/tmp/usr/lib/libedit.a(editline.o)(.text+0x5381): In function > `term_insertwrite': > : undefined reference to `tgoto' > *** Error code 1 > > Stop in /usr/src/usr.sbin/gstat. > *** Error code 1 > > Stop in /usr/src/usr.sbin. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. - End forwarded message - -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Possibility for FreeBSD 4.11 Extended Support
It's Sat, Dec 23, 2006 at 12:00 . I'm in a small dim room with doors labeled "Dungeon" and "Forbidden". There is noise, the door marked Dungeon flies open and [EMAIL PROTECTED] SHOUTS: > Message: 5 > Date: Fri, 22 Dec 2006 13:43:54 + > From: Pete French <[EMAIL PROTECTED]> > Subject: Re: Possibility for FreeBSD 4.11 Extended Support > To: freebsd-stable@freebsd.org, [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > > Because everybody knows that odd numbered releases aren't stable. > I've been 20 years in electronics & comouting and thats the first > time I have ever heard anyone say that! Steer clear of '.0' releases > is well known, but suspecting something just because of the odd or > evenness of it's numbering scheme seems like pure superstition. > Especually since we are Unix people, and the two of the > 'biggies' in history are Version 7, System 5 ;-) And as system V progressed it got funkier and I moved the servers at an ISP I was part of back in the mid-90s from a 1/2 dozen or so SGI machine to FreeBSD and I felt I was back home again - as it was so similar to the System III based/derived systems I learned on. My first pass at Sys V was on and AT&T 3B2-310, and so many things were far slower than what came before, and some of their programs were so poor in execution it was a pain. I once did a simple benchmark and on an old Z80 based system I was getting times in under 10 seconds in the C test and under 1 minute in the BASIC version. On the 3B2 the program seemed to hang in BASIC. I ran it again and then broke out and looked at the variables. I was aghast when I mentally computed that the program would take an hour to run. The C version ran in a bit under 5 minutes. I will say that the 5.3 things got a bit better but not long after that most of the smaller and the ones that seemed to have decent support disappeared and left us with only a handful of SysV companies. And then there is the classic 1.0 release of NeXTStep. It was pretty stable, considerning the last release before 1.0 was 0.99. Jobs got a lot of press on that one :-) > -pete. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A place for configuration files
On Thu, Mar 23, 2006 at 12:00 , the murky waters churned and seethed, the dark weeds parted and the water took on the sinister, shifting visage we recognize as [EMAIL PROTECTED] The great maw opened, and the following was heard: > Message: 1 > Date: Thu, 23 Mar 2006 02:06:07 +0100 > From: Andrzej Cuber <[EMAIL PROTECTED]> > Subject: a place for configuration files > To: freebsd-stable@freebsd.org > Hello Everyone, > for the last 5 years I was using Red Hat and Fedora Core > Linuxes. With the beginning of the current year I installed > FreeBSD Release 6 on one of my servers. It took me about a week > to setup the system but I am very happy with it now. > I build most of the stuff from the sources using ports. > What I found strange is that the configuration files of > different services are located in two different places. Most > configuration which was installed from the CD is located at > /etc but everything what I built from sources is located at > /usr/local/etc. Maybe this is the way it use to be on Unix based > systems. > In RedHat and Fedora distributions all configuration files > are located at /etc. I am very new to FreeBSD but I found it > difficult. After installing desired package I have to add it to > /etc/rc.conf in order to start it as a service and then I have > to look for configuration folder in /usr/local/etc. > Is there any reason why the configuration files are placed in > those different locations? > -- > pozdrawiam / best regards > Andrzej Cuber > +48 504 271-977 Once you get more familiar with BSD you will begin to appreciate the way it is done on BSD. One really nice thing is that by separating the OS and the user added 'local' programs, you can actually remake the / file system, reinstall the OS, and not lose any of you local applications or data. As another reply indicated rebuiling from sources will also let you reinstall the base OS, and the only thing you would have to do to make sure no drek is left over is to list the base directories by time created to find any old pieces and remove if needed. Another way that BSD differs it to have several file systems to start with while many recent Linux installations [which I've been called in to look at] seem to use the old MS approach of everything in one FS. With over 20 years of Unix experiences so far [on many platforms and at least 6 different CPU bases] I find the multiple FS'es, with each handling only certain functions, makes a recover in case of the rare crashes, much easier, and much faster. And faster means quicker client uptime. As I tell the customers when I get them back up in a hurry, "if you are down you aren't making money and if you aren't making money you can't pay me". They appreciate that approach, and I've changed some commercial OSes to use the FreeBSD approach to great success. Particularly when the data segments accumulated by the customer become quite huge. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new FreeBSD-webpage
On or about Thu, Oct 06, 2005 at 12:01 , while attempting a Zarathustra emulation [EMAIL PROTECTED] thus spake: > Message: 12 > From: Peter Jeremy <[EMAIL PROTECTED]> > Subject: Re: new FreeBSD-webpage > It's definitely a totally different look. At this stage, I'd say > that I prefer the old site - but that's a very personal opinion and > is at least partially based on familiarity. I'm disappointed that > the daemon has gone from the top banner. > I'd suggest that the most important feature that is missing is a > website map. The website looks nothing like it used to and many of my > commonly referenced links are no longer on the home page. Finding my > way around is going to be very time consuming until I learn my way > around it. > On the positive side, I'm glad that it's still usable with a text > browser. On the downside, I notice it now uses cookies. Well if you like the old site just try this: http://www.freebsd.org/old Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slow internet browsing
The door open and in walked trouble - disguised as our our old
nemesis [EMAIL PROTECTED], who uttered, at Thu,
Sep 15, 2005 at 12:00 :
> Date: Wed, 14 Sep 2005 10:43:06 -0400
> From: Bob Johnson <[EMAIL PROTECTED]>
> Subject: Re: Slow internet browsing.
> To: Sandro Noel <[EMAIL PROTECTED]>
> On 9/13/05, Sandro Noel <[EMAIL PROTECTED]> wrote:
> > thank you all for the ULTRA fast reply,
> > i had an entry in the resolv.conf that did not belong there.
> > problem solved.
> > something is bothering me...
> > the entry stated that it was the ip of my gateway 10.0.5.1
> > wich is the same address that the DHCP server gives out.
> > why is it causing problems ?
> Many (most?) small firewall/router/nat boxes list themselves as the
> DNS server when they do DHCP, and they try to proxy the DNS service.
> Some of them don't seem to do it right when you are using a DNS server
> on your internal network (and perhaps other situations), and you end
> up with long delays like you describe. If that's what is going on,
> the problem will reappear every time you boot the system and get a new
> DHCP lease (and perhaps every time the lease is renewed), because the
> dhcp client will rewrite /etc/resolv.conf.
> In 5.4R I think you can edit /etc/dhclient.conf and add some
> statements that put the correct entry in regardless of of what the
> DHCP server tells it. E.g. something like
>
>interface "ep0" {
>prepend domain-name-servers 192.168.1.2;
>}
>
> would always use 192.168.1.2 as the primary DNS server for interface
> ep0 regardless of what the DHCP server says to use. See the
> dhclient.conf man page for more details.
>
> FreeBSD is in the process of adopting a new dhcp client, but I think
> this still applies to 5.4R.
> And yes, this question really belonged on -questions, not -stable, but
> it's not really a big deal, I guess. When in doubt, use -questions.
He could also run chflags schg on the /etc/resolv.conf
to keep it from being re-written.
Bill
--
Bill Vermillion - bv @ wjv . com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dangerous situation with shutdown process
I know you'll find this hard to believe, but on Sat, Jul 16, 2005 at 10:52 ,
David Magda actually admitted to saying:
>
> On Jul 15, 2005, at 11:08, Bill Vermillion wrote:
> >If you only do huge copies and immediate shutdowns rarely, then
> >maybe it's just a good idea to remember how softupdates work, and
> >then fsck, then shutdown.
> This may sound simplistic, but what about a triple sync(8)? ("sync;
> sync; sync")
Actually I saw that documented a very very long time ago in
an Intel Unix manual. And Intel got out of Unix in the mid to late
1980s. I don't recall if that was the one that was sold to Kodak -
the picture people - which then was sold to Interactive ?? - and
eventually wound up at Sun. There were so many Unix variants
in those days you had to have a chart to keep up with them. Each
HW manufacturer had their own version and name, and at that time
the only time you could call your OS Unix was if you compiled
it directly from the AT&T tapes with no changes on a Vax [if I
recall the scenario correctly].
But that was a long time ago.
Bill
--
Bill Vermillion - bv @ wjv . com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dangerous situation with shutdown process
At Sat, Jul 16, 2005 at 16:29 , our malformed and occasionally flatulent friend Matthias Buelow spewed forth this fount of brain juice: > Bill Vermillion wrote: > >You can fsck a mounted file system and fsck will run in read-only > >mode. That way you can check for problems, and if there is > >something wrong you can shutdown and restart. FreeBSD will NOT > >run fsck in anything other than READ ONLY when the file system is > >mounted > I thought fsck on a live (read-write) filesystem almost always > brings up errors (although only of a certain kind, like dangling > inodes) unless the fs has been completely quiescent for a while. > A quick check seems to confirm this: > ** /dev/ad4s3a (NO WRITE) > ** Last Mounted on / > ** Root file system > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > UNREF FILE I=94257 OWNER=mkb MODE=100600 > SIZE=2397 MTIME=Jul 16 16:25 2005 > CLEAR? no The 'no' was supplied by the system, was it not. First line sas NO WRITE. > >And in the old days when drives were smaller and slower and > >perfomance needed to be maximized, from about Verision III through > >System V you could run fsck -S from cron!! > >The -S flag was interesting in that it would actually re-write > >the freelist IF AND ONLY IF there was no corruption on the drive. > I'm amazed that this worked.. considering that the fsck would have > to be atomic then (i.e., basically halt all filesystem i/o while > it's running). We'd run it from cron as noted. And this was done overnight - in systems where users were there only in the daytime. It did make a difference in keeping perfomance up longer than without it. Without that you'd basically have to backup the fs, remake the fs, and then reload to get back the originally installed performance. But as I noted this was for the S51 file system. It was really slow. On my first Sys V.3 system, I made one file system with the old S51/Xenix layout, and everthing else was an FFS that was slightly modified from the the original BSD systems. That was probably about 1990. The performance on the S51 ON THE SAME DRIVE - was no better than 30% as fast as the FSS and most of the time it was only 10% as fast. Once all the old customers moved to newer OS versions the old fsck -S [note that it is capital S and not 's' - and you'll have to find a Sys V manual to document the differentce - and I don't have one handy at the moment]. And small businesses were very very reluctant to upgrade unless they were forced too. I did some Y2K patching on OSes that had been installed in the late 1980s. And about the latest anyone would be using a system there would be about 9PM - when the owner stayed late. With current systems, in particular net connected systems with email, you could not hope to find a quiescent system. However the S flag was rewrite the freelist ONLY if the rest of the fsck gave no errors. If there were problems, such as the unrefferenced file you showed in your example, the freelist would not be re-written. That's why it was OK to run it in cron. Anyone who had not worked with Unix systems of 10-25 years ago can't begin to appreciate how good things are today. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dangerous situation with shutdown process
Somewhere around Fri, Jul 15, 2005 at 22:13 , the world stopped and listened as [EMAIL PROTECTED] graced us with this profound tidbit of wisdom that would fulfill the enjoyment of future generations: > Date: Fri, 15 Jul 2005 18:22:14 +0200 > From: Matthias Buelow <[EMAIL PROTECTED]> > Subject: Re: dangerous situation with shutdown process > To: Bill Vermillion <[EMAIL PROTECTED]> > Cc: freebsd-stable@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > Bill Vermillion wrote: > >Copying very large files and then shutting down I hope is not a > >normal procecure for you. softupdates sometimes do take a long > >time when you are removing/copying very large files. > >Others have suggested different time-outs but you'd have to figure > >out the largest size you may every encounter and set things for > >that, which is not going to help for everyday operation. > >I've watched the amount of disk space increase slowly by performing > >'df' and it can take a long time - up to a minute on some extremely > >large partitions I was cleaning. > >One way to force everything to be written I've found [by > >observation only] is to perform an fsck on that file system. > >If you only do huge copies and immediate shutdowns rarely, then > >maybe it's just a good idea to remember how softupdates work, and > >then fsck, then shutdown. > >I'm always against changing default operations from typical > >operations to extremes. > Sorry folks, have I somehow dropped into a parallel universe, > or is there some serious misunderstanding going on? > To the OP: There is no "sync" process that is being killed by > shutdown. The kernel writes out all dirty buffers as part of its > shutdown procedure. I was under the impression that there was a problem, that's why I wrote my reply. > Bill, as I get it from what you wrote, correct me if I'm wrong, > you assume that: > 1. unmount doesn't wait for all dirty data being committed > to disk before somehow removing the filesystem, That's what the OP seemed to indicate. > 2. fsck on a live filesystem will somehow speed things up. Actually an fsck on a live filesystem will force the softupdates to complete more quickly - that is from observation - and when I've deleted extremly large directories - usually /usr/src and /usr/obj. It only speeds up flushing the blocks to disk. > For 1., this is surely not the case, the same as with shutdown, > the kernel of course writes (drive errors notwithstanding) > all modified buffers and updates all on-disk structures before > marking the fs clean, and > for 2., you should never fsck a mounted filesystem. Besides, > it is completely unnecessary. You can fsck a mounted file system and fsck will run in read-only mode. That way you can check for problems, and if there is something wrong you can shutdown and restart. FreeBSD will NOT run fsck in anything other than READ ONLY when the file system is mounted And in the old days when drives were smaller and slower and perfomance needed to be maximized, from about Verision III through System V you could run fsck -S from cron!! The -S flag was interesting in that it would actually re-write the freelist IF AND ONLY IF there was no corruption on the drive. Since blocks on those systems were used in the revers order they were released, running fsck -S sorted the freelist in ascending order and thus helped to elminate fragmentation. This was particularly important on the S51 file systems - as it was before the SysV's adoptedf variants of the FFS system that came from BSD. > If the OP has encountered any data corruption, this is due to > an unclean shutdown because of disk errors or a kernel bug, > and not because of "timeouts" that are too short or something > like that. It would have been nice to see his actual errors. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dangerous situation with shutdown process
On Thu, Jul 14, 2005 at 22:31 , [EMAIL PROTECTED] moved his mouse, rebooted for the change to take effect, and then said: > Message: 13 > Date: Thu, 14 Jul 2005 20:38:15 +0200 > From: Anatoliy Dmytriyev <[EMAIL PROTECTED]> > Subject: dangerous situation with shutdown process > To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8; format=flowed > Hello, everybody! > I have found unusual and dangerous situation with shutdown process: > I did a copy of 200 GB data on the 870 GB partition (softupdates is > enabled) by cp command. > It took a lot of time when I did umount for this partition > exactly after cp, but procedure finished correctly. > In case, if I did ???shutdown ???h(r)???, also exactly after cp, > the shutdown procedure waited for ???sync??? (umounting of the > file system) but sync process was terminated by timeout, and > fsck checked and did correction of the file system after boot. > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > How can I fix it on my system? Copying very large files and then shutting down I hope is not a normal procecure for you. softupdates sometimes do take a long time when you are removing/copying very large files. Others have suggested different time-outs but you'd have to figure out the largest size you may every encounter and set things for that, which is not going to help for everyday operation. I've watched the amount of disk space increase slowly by performing 'df' and it can take a long time - up to a minute on some extremely large partitions I was cleaning. One way to force everything to be written I've found [by observation only] is to perform an fsck on that file system. If you only do huge copies and immediate shutdowns rarely, then maybe it's just a good idea to remember how softupdates work, and then fsck, then shutdown. I'm always against changing default operations from typical operations to extremes. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Build errors on 4.11 in docs with pdf and/or html
I had gotten busy and had not done a new buildworld since January. I had a failure in buildworld, and the next day [I do nightly cvsup's], I did a make clean and got the same problem. So I did the logical thing, I removed the entire /usr/src and /usr/obj and re-cvsuped. I again got errors. Here is that error. [everthing deleted except the final section] -- >>> stage 4: building everything.. -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec GROFF_BIN_PATH=/usr/obj/usr/src/i386/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/i386/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/i386/usr/share/tmac DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 all ===> share/info ===> include ===> include/arpa ===> include/protocols ===> include/rpc ===> include/rpcsvc ===> lib ===> lib/csu/i386-elf ===> lib/libcom_err gzip -cn /usr/src/lib/libcom_err/../../contrib/com_err/com_err.3 > com_err.3.gz ===> lib/libcom_err/doc make: don't know how to make com_err.pdf. Stop *** Error code 2 Stop in /usr/src/lib/libcom_err. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. 846.18 real 540.36 user 207.16 sys I remember at one time I had a problem building docs with the PDF option turned on in make.conf. So I checked and I had FORMATS=pdf html in /etc/make.conf. Ah ha! So I changed that to be FORMATS=html and rebuild again. This is the error of that output - again just stage 4 onward. -- >>> stage 4: building everything.. -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec GROFF_BIN_PATH=/usr/obj/usr/src/i386/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/i386/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/i386/usr/share/tmac DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 all ===> share/info ===> include ===> include/arpa ===> include/protocols ===> include/rpc ===> include/rpcsvc ===> lib ===> lib/csu/i386-elf ===> lib/libcom_err gzip -cn /usr/src/lib/libcom_err/../../contrib/com_err/com_err.3 > com_err.3.gz ===> lib/libcom_err/doc makeinfo --no-split -I /usr/src/lib/libcom_err/doc -I /usr/src/lib/libcom_err/doc /usr/src/lib/libcom_err/doc/com_err.texinfo -o com_err.info /usr/src/lib/libcom_err/doc/com_err.texinfo:377: warning: unlikely character ( in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:377: warning: unlikely character ) in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:384: warning: unlikely character ( in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:384: warning: unlikely character ) in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:577: warning: unlikely character ( in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:577: warning: unlikely character ) in @var. info2html com_err.info info2html:No such file or directory *** Error code 1 Stop in /usr/src/lib/libcom_err/doc. *** Error code 1 Stop in /usr/src/lib/libcom_err. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. 854.38 real 534.98 user 203.54 sys Hm. It won't build with FOMMATS=html either. I've used that line in my /etc/make.conf for a long time. I do not recall I've ever had this problem before. I commented the FORMATS line out completey in /etc/make.conf and now everything builds correctly. I wish I had built more often but that's how this year has been so far. So the last build I did where everything worked in the past was on January 29 at 21:22 EST. Is there something else I may have changed that caused this, or has the behaviour changed in the past 4 months. Bill -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very large directory
> > From: "Phillip Salzman" <[EMAIL PROTECTED]> > Subject: Very large directory > I have a pair of servers that act as SMTP/AV gateways. It > seems that even though we've told the AV software not to store > messages, it is anyway. > > They've been running for a little while now - and recently we've > noticed a lot of disk space disappearing. Shortly after that, a > simple du into our /var/spool returned a not so nice error: > du: fts_read: Cannot allocate memory > No matter what command I run on that directory, I just don't > seem to have enough available resources to show the files let > alone delete them (echo *, ls, find, rm -rf, etc.) Even echo * sorts the output, and the sorting consumes a large amount of resources. Try and ls with a "-f" option. To prove it to yourself take any directory and perform echo * and then do the same with ls -f I first noticed this years ago when on an old SysV I had a directory that took 5 minutes to display and the ls -f was quite fast. > End of freebsd-stable Digest, Vol 95, Issue 8 -- Bill Vermillion - bv @ wjv . com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: good address will not resolve
> Message: 14 > Date: Tue, 07 Oct 2003 15:01:54 -0400 > From: Mike Tancsa <[EMAIL PROTECTED]> > Subject: Re: good address will not resolve in freebsd (_ in host > names) > No, but like I said, more and more people are starting to use > it. What is the big deal about _ vs - ? I am all for following > convention, but sometimes it leads to the Judean Popular > People's front vs the People's popular Front of Judea type > stuff Also, as someone else pointed out, I think the RFC > has changed since then. I can't find an RFC that says the host name has changed. I remeber first setting up DNS systems in the early-mid'90's when and underscore was permitted, but it was noted that it would stop being supported in the future. The RFC the other person refered to shows that almost anything is permitted on the internal names - but it never specifically addresses host names, as it done in RFC1034 I told the people at that site they would have to change, but they didn't bother to do that until things started breaking. It appears that MS is the culprit. The refernce in what I read point to an alternate character set and points to RFC2181 - but that does not appear to be correct. It's part of the W2K DNS and you can configure it four any one of four choices. Strict ANSI - RFC 1123, Non-RFC ANSI - adds underscore, Multibyte (UTF8) - MS naming standard, or Any - where any character can be used. The notes say that in >strictly private networks< MS suggests that the Unicode standard works well. The article also says you have to decide to enforce MS standards or have dual support. Since MS machines aren't running on most of the internet backbone and virtually all are non-MS, changing things at this stage of the game would surely create a lot of non-findable systems. I'm not going to change any of my name servers. I have enough problem with one of the European registrars refusing to accept a client registration as my servers don't meet THEIR standards. But that is .it - and it was only one - so I'm not about to change things that work. A question here - will the registrars permit registering a name with an underscore. > End of freebsd-stable Digest, Vol 29, Issue 3 > * Bill -- Bill Vermillion - bv @ wjv . com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing sendmail
On Wed, Sep 04, 2002 at 14:20 , Men gasped, women fainted, and small children were reduced to tears as stable-digest confessed to all: > Date: Wed, 4 Sep 2002 13:00:52 -0700 > From: Gregory Neil Shapiro <[EMAIL PROTECTED]> > Subject: Re: Removing sendmail > > >> This will of course break your system.. No more periodic reports > >> (daily security reports), no more cron mail, no more user mail, etc. > haering_linux> Not if you install a different MTA like Postfix instead. > He was removing /usr/bin/mail and mailx. That really would would break things wouldn't it. Why is it that so often people just start wholesale deleting things without checking appropriate places. apropos mail should point out to the observant eye several things to check and reach the desired results without breaking things. Reading docs pointed out /usr/sbin/sendmail is a link to /usr/sbin/mailwrapper. The /etc/mail/mailer.conf describes how to use this so that you tell the systemexactly what programs to run when you call sendmail. Take a look at that and it should fix the problems. IOW using the name 'sendmail' can invoke other programs instead of the real sendmail. On top of that if you really don't want sendmail at all, then in /etc/make.conf put in the NO_SENDMAIL=NO directive. Man make.conf will clue you in on that. The system really is quite configurable with the tools built in without having to rip out directories wholesale and then wonder what you have to put back to make it work again. Use the docs Luke. Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Trouble with some ports
I'm running a recent 4.5 Stable on this machine and 4.6-PRERELEASE on another and I'm having problems compiling ImageMagick which depends on bison. So I tried configuring bison on both machines with the same failure. I shipped the output of the first failure earlier this week to [EMAIL PROTECTED] and have heard nothing - but that may be normal. I get errors of not found for CFLAGS, CPPFLAGS, CPP, LDFLAGS, build_alias, host_alias, and target_alias, all repeated several times. I also get an error that the newly created file is older than the distributed files and I'm using ntpdate and the system is never more than 1 second off of the real world time. I'm not sure if this is the correct list but I've not had problems compiling these before. I found these problems when I was using portupgrade for the first time. It may really be user error, or most highly probably a user erro, but at the moment I'm not sure where to look. I've never had ports fail like this before. I cvsup the ports tree every night so all of that should be current. Any help and/or pointers will be really appreciated. Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: DNS weirdnewss
> weirdness with DNS > Date: Mon, 30 Jul 2001 12:06:35 -0400 (EDT) > From: Matt Heckaman <[EMAIL PROTECTED]> > Subject: weirdness with DNS > > - -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I started seeing this a long time ago, but since it doesn't break anything > (well, not really) I never got around to writing this email about it. I > have a machine running 4.3-STABLE as of April 21 2001. When I do a DNS > lookup on a host that does not exist, it postfixes my domain onto the > lookup instead of saying Unknown host... At first, I thought there was a > wildcard DNS entry for lucida.ca, but there isn't. This does not occur > from any other machines on the LAN, all of which use the same nameservers. The only time I recall seeing this is when I had a missing "." somewhere in the file. Get 'nslint' from the ports and run that against your DNS to see if you don't spot a problem. Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
