Can't locate ExtUtils/MakeMaker.pm
-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include' ccversion='', gccversion='3.4.6 [FreeBSD] 20060305', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='cc', ldflags =' -Wl,-E -L/usr/local/lib' libpth=/usr/lib /usr/local/lib libs=-lgdbm -lm -lcrypt -lutil perllibs=-lm -lcrypt -lutil libc=, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' -Wl,-R/usr/local/lib/perl5/5.8.8/mach/CORE' cccdlflags='-DPIC -fPIC', lddlflags='-shared -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: MYMALLOC PERL_MALLOC_WRAP USE_64_BIT_INT USE_LARGE_FILES USE_PERLIO Locally applied patches: defined-or Built under freebsd Compiled at Nov 10 2007 18:50:19 @INC: /usr/local/lib/perl5/5.8.8/BSDPAN /usr/local/lib/perl5/site_perl/5.8.8/mach /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8 . -- Noah Garrett Wallach Juniper Networks Consulting Engineer1194 North Mathilda Avenue Professional Services Sunnyvale CA 94089 tel: +1-415-823-6624 fax: +1-415-431-7726 - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
port knocking
Hi there, doorman is core dumping and not working properly. could somebody please recommend a good port knocker? Cheers, Noah -- Noah Garrett Wallach Juniper Networks Consulting Engineer1194 North Mathilda Avenue Professional Services Sunnyvale CA 94089 [EMAIL PROTECTED] tel: +1-408-936-7363 fax: +1-415-431-7726 - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Attempts to run 'fsck' fail can't stat device
My server lost power earlier today and now it doesnt boot. Any clues what I can do to recover from the following errors: s nip Server 'hostname' fails to mount /dev/da0s1g (/usr). Attempts to run 'fsck' fail (can't stat device /dev/da0s1g) snip --- cheers, Noah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: named not starting during boot
Wojciech Puchar wrote: named is not starting when I reboot a FreeBSD 6.2 server and I cant figure out why. there are no error mesasges in /var/log/messages during the boot process. even when I manually start there are no error messages. # grep named /etc/rc.conf named_enable=YES # pkg_info | grep bind bind9-9.3.4 Completely new version of the BIND DNS suite with updated why you are installing bind from ports - there is bind9 in base system. and it's controlled with named_enable. because there are security exploits and keeping upto date version is important to me. http://www.isc.org/index.pl?/sw/bind/bind-security.php have you configured right version in right (/etc/namedb) directory? I will check that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: named not starting during boot
Hi there, I dont have a user name named. I have a user named bind. so bind is what I am going with. named_enable=YES named_uid=bind named_program=/usr/local/sbin/named named_flags=-c /etc/namedb/named.conf named_chrootdir=/var/named cheers, Noah Derek Ragona wrote: In the newer versions of bind you need to add to /etc/rc.conf: named_uid=username you want to run named as. -Derek At 07:24 PM 2/26/2007, Noah Garrett Wallach wrote: Hi there, named is not starting when I reboot a FreeBSD 6.2 server and I cant figure out why. there are no error mesasges in /var/log/messages during the boot process. even when I manually start there are no error messages. # grep named /etc/rc.conf named_enable=YES # pkg_info | grep bind bind9-9.3.4 Completely new version of the BIND DNS suite with updated D # grep BIND messages Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3 Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3 Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c /etc/namedb/named.conf # /etc/rc.d/named stop # /etc/rc.d/named start # grep BIND messages Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3 Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3 Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:23:46 access2 named[1005]: starting BIND 9.3.4 -c /etc/namedb/named.conf any clues please? Cheers, Noah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
named not starting during boot
Hi there, named is not starting when I reboot a FreeBSD 6.2 server and I cant figure out why. there are no error mesasges in /var/log/messages during the boot process. even when I manually start there are no error messages. # grep named /etc/rc.conf named_enable=YES # pkg_info | grep bind bind9-9.3.4 Completely new version of the BIND DNS suite with updated D # grep BIND messages Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3 Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3 Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c /etc/namedb/named.conf # /etc/rc.d/named stop # /etc/rc.d/named start # grep BIND messages Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3 Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3 Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c /etc/namedb/named.conf Feb 26 17:23:46 access2 named[1005]: starting BIND 9.3.4 -c /etc/namedb/named.conf any clues please? Cheers, Noah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: named not starting during boot
Kevin, those were manual restarts. cheers, Noah Kevin Kinsey wrote: Noah Garrett Wallach wrote: Hi there, named is not starting when I reboot a FreeBSD 6.2 server and I cant figure out why. there are no error mesasges in /var/log/messages during the boot process. even when I manually start there are no error messages. Have you tried with -fg ? There are a lot of really quick restarts in that log snippet around 5:20 snip any clues please? Not really, most of the time I think I'm completely clueless ;-) Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade perl and openwebmail
On Wed, 15 Dec 2004, Lapo Nustrini wrote: If you have just gone from a 5.8.1 version of Perl to the current 5.8.5, you are probably running into the following: (From the Openwebmail README file at http://www.openwebmail.org/openwebmail/doc/readme.txt ) If you are using FreeBSD and your perl is compiled from port, then please note that the SUID support is disabled by default since the port for perl 5.8.1 or later You need to do 'make -DENABLE_SUIDPERL' in making port Lapo thanks - I am rebuilding perl now. is there something I can add to the /etc/make.conf file to make enabled SUID support everytime I rebuild perl? cheers, Noah On Dec 15, 2004, at 2:50 PM, Noah Garrett Wallach wrote: FreeBSD-4.9 perl-5.8.5 openwebmail-2.41 just portupgraded perl now I am having difficulties reinitializing openwebmail.pl any clues on this? --- snip --- # /usr/local/www/cgi-bin/openwebmail/openwebmail-tool.pl --init Args must match #! line at /dev/fd/9 line 1. speedy_backend[44225]: perl_parse error speedy[44223]: Cannot spawn backend process --- snip - Noah ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade perl and openwebmail
On Wed, 15 Dec 2004, Lapo Nustrini wrote: If you have just gone from a 5.8.1 version of Perl to the current 5.8.5, you are probably running into the following: (From the Openwebmail README file at http://www.openwebmail.org/openwebmail/doc/readme.txt ) If you are using FreeBSD and your perl is compiled from port, then please note that the SUID support is disabled by default since the port for perl 5.8.1 or later You need to do 'make -DENABLE_SUIDPERL' in making port Lapo also is this make switch suppesed to be provided when building perl or when building openwebmail - which port please? cheers, Noah On Dec 15, 2004, at 2:50 PM, Noah Garrett Wallach wrote: FreeBSD-4.9 perl-5.8.5 openwebmail-2.41 just portupgraded perl now I am having difficulties reinitializing openwebmail.pl any clues on this? --- snip --- # /usr/local/www/cgi-bin/openwebmail/openwebmail-tool.pl --init Args must match #! line at /dev/fd/9 line 1. speedy_backend[44225]: perl_parse error speedy[44223]: Cannot spawn backend process --- snip - Noah ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade perl and openwebmail
FreeBSD-4.9 perl-5.8.5 openwebmail-2.41 just portupgraded perl now I am having difficulties reinitializing openwebmail.pl any clues on this? --- snip --- # /usr/local/www/cgi-bin/openwebmail/openwebmail-tool.pl --init Args must match #! line at /dev/fd/9 line 1. speedy_backend[44225]: perl_parse error speedy[44223]: Cannot spawn backend process --- snip - Noah ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
perl and openwebmail - cant locate vars.pm
FreeBSD 4.9 okay i am attempting to install perl-5.8.2 from the /usr/ports I am seeing the following thing happen I suid'ed /usr/bin/suidperl with 4555 did a use.perl port and also what should my /etc/make.conf file look like - is this okay? --- snip --- # -- use.perl generated deltas -- # # Created: Tue Jul 15 22:09:26 2003 # Setting to use base perl from ports: PERL_VER=5.8.2 PERL_VERSION=5.8.2 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo snip --- output from speedyCGI files. Can't locate vars.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8. 0/mach /usr/local/lib/perl5/site_perl/5.8.0 /usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl/5.005 /usr/local/lib/perl5/site_perl /usr/local/ lib/perl5/5.8.0/BSDPAN /usr/local/lib/perl5/5.8.0/mach /usr/local/lib/perl5/5.8. 0) at /dev/fd/10 line 19. BEGIN failed--compilation aborted at /dev/fd/10 line 19. speedy_backend[20770]: perl_parse error speedy[20768]: Cannot spawn backend process ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iostat - define Kilobits per transfer
I currently have an IDE drive that has the capacity to do 128KB/t and a SCSI drive 64KB/t. Are these stats in fact showing me that there is a limitation with the SCSI drive? Are my file transfering capaibilities less with the SCSI drive? I suppose what do I need to look for in the spcifications when choosing new drives so this does not happen again? FreeBSD's SCSI layer has a cap of 64k per transaction (apparently because ancient ISA adapters could not do more than 64k), and the ATA layer has a cap of 128k. You won't see a difference using regular disks. A 20MB/sec transfer rate comes out to ~300 64K transactions/sec, which most systems should be able to handle with no problems. so what exactly does KB per transaction mean? what happens if I am handling 300 concurrent users with 160Kbit encoded audio streams - could I in fact do this on this machine? or will I be limited by the 64KB/t issue? - Noah -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: iostat - define Kilobits per transfer
On Wed, 22 Jan 2003, Dax Eckenberg wrote: so what exactly does KB per transaction mean? what happens if I am handling 300 concurrent users with 160Kbit encoded audio streams - could I in fact do this on this machine? or will I be limited by the 64KB/t issue? 300 x 160Kbit = approx. 46Mbit/sec. A new-ish SCSI drive should be able to easily pump out in excess of 200 Mbit/sec. Your bottleneck will be your ethernet adapter long before your local storage. Unless your app is designed very poorly. okay things are getting clearer over here. what exactly does KB per transaction mean? I dont understand what this describes? - Noah To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Back up hard drive?
does anybody out there have a decent script to backup between hard drive. also what about a script to back up to back up to a tape drive as well. if you have pointers to cool programs that does this well?. thanks in advance, Noah To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
timezone issue
timezone issue. all the documentation I have seen out there appears to be getting the timezone set correctly. I have it set to PST. It is 2 hours off from the actual time. can somebody explain how to fix this? I have NTPD running as well. Thanks in advance. - Noah To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
4.7-STABLE kernel build
Hi, okay I just built a 4.7-STABLE kernel. but I am not able to boot when using the GENERIC config file. I am kinda new at troubleshooting this type of stuff so a clue is welcome. after installation and reboot I only get so far - to the following line: amr0: AMI MegaRAID mem 0xf000-0xf7ff irq 3 at device 0.0 on pci4 the next line should be (from the 4.6-STABLE old kernel) amr0: PERC 3/DC Firmware 1.72, BIOS 3.27, 128MB RAM what is creating this issue? I think this MegaRAID card is supported - so I am not sure why loading stalls here. - noah To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7-STABLE kernel build
On Fri, 10 Jan 2003, Noah Garrett Wallach wrote: Hi, okay I just built a 4.7-STABLE kernel. but I am not able to boot when using the GENERIC config file. I am kinda new at troubleshooting this type of stuff so a clue is welcome. after installation and reboot I only get so far - to the following line: amr0: AMI MegaRAID mem 0xf000-0xf7ff irq 3 at device 0.0 on pci4 okay I removed the MegaRAID support from the kernel configuration file and rebuilt the kernel. things work fine now. but I am wondering why there is still a hang on kernel boot for when the RAID card is defined. commented: # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device iir # Intel Integrated RAID #device mly # Mylex AcceleRAID/eXtremeRAID #device ciss# Compaq SmartRAID 5* series # RAID controllers #device aac # Adaptec FSA RAID, Dell PERC2/PERC3 #device aacp# SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade the next line should be (from the 4.6-STABLE old kernel) amr0: PERC 3/DC Firmware 1.72, BIOS 3.27, 128MB RAM what is creating this issue? I think this MegaRAID card is supported - so I am not sure why loading stalls here. - noah To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Drive Failure
I dont know what this option means - does this matter? -B Install the `boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table. Sounds like just what you said you wanted. Hi Jerry, What does without affecting the embedded slice table mean? What si the embedded slice table? And should I make sure that I dont affect it - or should I affect it? also is there anyway to see that, after replacing the MBR on the new drive with boot0cfg, that it is properly bootable? - noah By the way, I notice that you have quit CC-ing the questions list. You should keep that in so it gets in archives and so I don't become the sole counselor - which you don't want, for sure! jerry - Noah jerry *** Working on device /dev/ad2 *** parameters extracted from in-core disklabel are: cylinders=148945 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=148945 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 150136497 (73308 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 464/ head 15/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
[no subject]
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
talk
talk does not appear to be working on my machine mesg = y but still I am not even able to talk to myself. what can I do here? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
troubleshoot: Bad file descriptors
I am wanting to know how to troubleshoot the Bad File Descriptors that are creeping in when I am ls and find files. How can I stop this from happening? I dont see any open bugs at this time? Is my drive possibly bad? snip find: /usr/ports/korean.old/hanterm/files: Bad file descriptor find: /usr/ports/korean.old/gaim: Bad file descriptor find: /usr/ports/korean.old/kde3-i18n: Bad file descriptor find: /usr/ports/korean.old/ghostscript-gnu-korfont: Bad file descriptor find: /usr/ports/korean.old/openoffice: Bad file descriptor find: /usr/ports/java.old/linux-blackdown-jdk12/files: Bad file descriptor find: /usr/ports/java.old/linux-sun-jdk13: Bad file descriptor find: /usr/ports/java.old/linux-sun-jdk14: Bad file descriptor find: /usr/ports/java.old/java-checkstyle: Bad file descriptor find: /usr/ports/java.old/jakarta-log4j: Bad file descriptor find: /usr/ports/java.old/jakarta-commons-collections: Bad file descriptor find: /usr/ports/java.old/jakarta-commons-lang: Bad file descriptor find: /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/lib/auto: Bad file descriptor find: /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/build: Bad file descriptor snip To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: troubleshoot: Bad file descriptors
Hi, It was also mentioned that there might be a bug with find. is this the case? I cannot seem to find anything with a gnats search. Figured I would at least ask to end this possibility --- snip --- FreeBSD blah.com 4.7-STABLE FreeBSD 4.7-STABLE #0: Thu Nov 7 16:18:33 PST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LOCAL i386 --- snip --- On Mon, 11 Nov 2002, Noah Garrett Wallach wrote: --- more to the story --- did fsck in single user mode. even rebuilt the OS and kernel and installed it all. What else can I do? - Noah --- more to the story --- On Mon, 11 Nov 2002, Noah Garrett Wallach wrote: I am wanting to know how to troubleshoot the Bad File Descriptors that are creeping in when I am ls and find files. How can I stop this from happening? I dont see any open bugs at this time? Is my drive possibly bad? snip find: /usr/ports/korean.old/hanterm/files: Bad file descriptor find: /usr/ports/korean.old/gaim: Bad file descriptor find: /usr/ports/korean.old/kde3-i18n: Bad file descriptor find: /usr/ports/korean.old/ghostscript-gnu-korfont: Bad file descriptor find: /usr/ports/korean.old/openoffice: Bad file descriptor find: /usr/ports/java.old/linux-blackdown-jdk12/files: Bad file descriptor find: /usr/ports/java.old/linux-sun-jdk13: Bad file descriptor find: /usr/ports/java.old/linux-sun-jdk14: Bad file descriptor find: /usr/ports/java.old/java-checkstyle: Bad file descriptor find: /usr/ports/java.old/jakarta-log4j: Bad file descriptor find: /usr/ports/java.old/jakarta-commons-collections: Bad file descriptor find: /usr/ports/java.old/jakarta-commons-lang: Bad file descriptor find: /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/lib/auto: Bad file descriptor find: /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/build: Bad file descriptor snip To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
