Re: System trying to start sshd twice
There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. I had this when I forgot that 4.4 installs sshd as a default and reinstalled it from /usr/ports. I just removed the /usr/local/etc/ entry, since I'm going to rerun buildworld, etc., after 4.5-RELEASE. (I'm running 4.5-PRE #2 right now) MLS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Strange problem with 3 kernel options
OK, a quick update. I tried building another machine with the same hardware (minus the realtek) and it works just fine. Its not nearly as busy as the one that failed. However, I did notice that the quota.users files on the two partitions had strange time stamps of the last access. Is it possible that the OS was unable to write to these corrupted files, and this is where everything was holding up ? Anyways, I blew away those files and will try a reboot in the early hours to see if that makes a difference-- i.e. with a freshly created quota.user file. ---Mike At 08:45 AM 1/2/02 -0500, Mike Tancsa wrote: OK, I know I will get slapped for providing such little information (to start), but this morning I had a bit of fun with upgrading a Oct19 kernel to a Dec31st kernel. Getting rid of #options DUMMYNET #options IPDIVERT#divert sockets # Disk quotas are supported when this option is enabled. #optionsQUOTA #enable disk quotas allowed me to have the machine function in a normal state. The problem state was that I was unable to login to the system in multi user mode. There *seemed* to be a lot of processes blocking on something. I dont know what as I was unable to login. I thought at first it was that syslog problem with /dev/console, but I rebooted with syslogd off and I was able to get to a login prompt briefly. After that the system became unstable with too many files open I had to reboot. I am posting this in case anyone else has seen something similar. dmesg below. Kernel config is basically GENERIC with uneeded device drivers removed. MAXUSERS is set at 256. As the box is production, I cant fiddle with it right now, but I can come back in during off hours and do whatever would be useful to try and track this down. I do have another box with quotas enabled, but its nowhere nearly as busy, particularly as I tried to bring up quota support on my mail partition which is fairly busy. (mount with soft updates enabled). Anyone see anything similar ? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: BIND and NTP (was Re: BIND 8.2.5 ?)
Hey, What is status on the NTP-deamon included? What are the reasons not to go all the way and upgrade to BIND 9? /Kristian snip alot of sites still use bind 8 for one reason or another. im guessing it will probably stay in until isc stop's maintaining 8.x in favor of 9. there is always ports.. 2c assumption -jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
From: Mike Squires [EMAIL PROTECTED] Date: Wed, 2 Jan 2002 09:09:36 -0500 (EST) Sender: [EMAIL PROTECTED] There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. I had this when I forgot that 4.4 installs sshd as a default and reinstalled it from /usr/ports. I just removed the /usr/local/etc/ entry, since I'm going to rerun buildworld, etc., after 4.5-RELEASE. (I'm running 4.5-PRE #2 right now) OK. Let me try to explain what is happening and the appropriate response based on what version of sshd you want to run. You have installed the ssh port which means you probably have 3.0.1 or 3.0.2. You are running 4.5-Prerelease, so you have 2.9 installed in the base system. If you have sshd_enable=YES in /etc/rc.conf, rc will start 2.9 from /usr/sbin. To prevent this from happening, edit your /etc/rc.conf file and comment out the sshd line. If you have /usr/local/etc/rc.d/sshd.sh, v3.0.? is being started. If V2.9 is already running, this will fail. To prevent the system from trying to start V3, pkg_delete openssh or chmod 644 /usr/local/etc/rc.d/sshd.sh. Unless you have a specific reason to run V3 of openssh, I'd really suggest that you stick to the installed, standard V2.9. It's not quite the latest and greatest, but it does get all security patches and is consistent across FreeBSD systems. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
On Tue, Jan 01, 2002 at 10:14:35AM -0600, Joe Halpin wrote: There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. This should only be the case if you installed a local copy of sshd (from ports or something). The base system doesn't have *any* startup scripts in /usr/local/etc/rc.d. Assuming you only want one copy of sshd running, you should be able to safely remove the sshd.sh script from /usr/local and set all of the startup parameters in /etc/rc.conf. --K To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
On Tue, Jan 01, 2002 at 10:51:20AM -0600, Joe Halpin wrote: Bill Moran wrote: Joe Halpin wrote: There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. Did you install an upgrade to sshd from a port or something? I don't recall doing that, but I must have. The version in /usr/src/crypto/openssh is 2.9, but pkg_info says that the installed version is 3.0.1. Installing something from ports that also exists in the base system doesn't uninstall the parts of the base system. It installs a new copy of the program in the /usr/local tree, leaving the default copy in the /usr tree. You can manually remove the ssh programs from /usr if you want to save space. Also, adding the line: NO_OPENSSH= true to /etc/make.conf will prevent future builds of your source from building the OpenSSH code and reinstalling it. --K To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
On Tue, Jan 01, 2002 at 11:13:55AM -0600, Joe Halpin wrote: supplied executables. Guess I should have also modified /etc/rc.conf at the same time. You basically have two options here. Since the port installed it's own startup script, you could have simply set sshd_enable=NO in rc.conf, and the system would skip it's own sshd boot code. Or, you could set the sshd_program and sshd_flags variables in rc.conf, and the system would start the ports version at boot time. Personally, I prefer this method for programs that are in the base system, as I think it's easier to undo the change if/when the base sshd (or whatever) moves up to the latest version. --K To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RELENG_4_4: PIIX busmastering DMA not supported
Hi! I was wondering if somebody could explain to me why busmastering DMA is not supported in my setup (RELENG_4_4): # dmesg | grep ata atapci0: Intel PIIX ATA controller port 0xfcf0-0xfcff at device 1.1 on pci0 atapci0: Busmastering DMA not supported ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 3090MB Maxtor 83240D3 [6697/15/63] at ata0-master BIOSPIO ad2: 6187MB FUJITSU MPE3064AT [13410/15/63] at ata1-master BIOSPIO # sysctl -a | grep hw\.ata hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.tags: 0 hw.ata.atapi_dma: 0 hw.atamodes: pio,---,pio,---, What confuses me is that hw.ata.ata_dma=1 but I'm still not able to set hw.atamodes to dma,---,dma,---, I thought that this controller would support DMA. I read ata(4) and could not find any hints of any flags similar to the one for wd(4) (i.e. 0x2000). I'm quite clueless now... Any idea...? Thilo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Problems compiling recent kernel
I have been having a very hard time updating to the latest -stable code. It took four days to get through a 'make world' because the compiler kept segfaulting. Now, I cannot get a new kernel to compile. I get past 'make depend', but then I get the following: # make cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/ipfilter -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/locore.s suffix or operands invalid for `shr'suffix or operands invalid for `shr'cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 I have no idea what this means. This is only the latest in a series of problems I have had with this machine in the last 4-5 weeks, so maybe the hardware is going bad. Is there anything I can do to fix the above so that I can get a kernel built? -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problems compiling recent kernel
++ 02/01/02 17:46 -0600 - Patrick L Hartling: | I have been having a very hard time updating to the latest -stable code. | It took four days to get through a 'make world' because the compiler | kept segfaulting. Now, I cannot get a new kernel to compile. I get past | 'make depend', but then I get the following: | | # make | cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls | -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes | -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi | -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/ipfilter | -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 | ../../i386/i386/locore.s | suffix or operands invalid for `shr'suffix or operands invalid for | `shr'cc: Internal compiler error: program as got fatal signal 11 | *** Error code 1 | | I have no idea what this means. This is only the latest in a series of | problems I have had with this machine in the last 4-5 weeks, so maybe the | hardware is going bad. Is there anything I can do to fix the above so | that I can get a kernel built? Sounds like hardware. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 -pete -- Pete Fritchman [petef@(databits.net|freebsd.org|csh.rit.edu)] finger [EMAIL PROTECTED] for PGP key To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers
Hey Søren, Do you have any idea what to do with the problems I am experiencing with the Intel-series chipset? Regards Kristian - Original Message - From: SXren Schmidt [EMAIL PROTECTED] To: Nils Holland [EMAIL PROTECTED] Cc: Matthew Dillon [EMAIL PROTECTED]; Mike Silbersack [EMAIL PROTECTED]; Brandon S. Allbery KF8NH [EMAIL PROTECTED]; ian j hart [EMAIL PROTECTED]; Matthew Gilbert [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 31, 2001 2:22 PM Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers It seems Nils Holland wrote: root@poison pciconf -r -b pci0:0:0 0x0:0xff Thanks! this was a kernel without the corruption fix, and it shows that you need it, the MWQ bug has been fixed in your BIOS... I have a new improved patch in the works that covers more chipset comboes, it'll go into -current shortly, and I hope to get permission to get it in 4.5, but so far the RE@ doesn't respond... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: RELENG_4_4: PIIX busmastering DMA not supported
On Wed, 2 Jan 2002, Thilo Mezger wrote: I was wondering if somebody could explain to me why busmastering DMA is not supported in my setup (RELENG_4_4): # dmesg | grep ata atapci0: Intel PIIX ATA controller port 0xfcf0-0xfcff at device 1.1 on pci0 atapci0: Busmastering DMA not supported According to the code, your controller does not claim to support DMA. The original PIIX probably didn't support it, thinking about it... Check your BIOS settings and verify that you didn't disable DMA at some point in the past. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: apropos Euro
On Tue, Jan 01, 2002 at 07:39:48PM +0100, Oliver Fromme wrote: Finally, many programs should respect the locale settings of your environment. The environment variable LC_CTYPE is responsible for declaring your character set to programs and applications that are l10n/i18n compliant. You can see all locales in the /usr/share/locale directory. For example, put the following in your shell's startup script if you use some kind of bourne shell (sh, ksh, zsh, bash): export LC_CTYPE=en_US.DIS_8859-15 For csh or tcsh, use this one: setenv LC_CTYPE en_US.DIS_8859-15 Note that the locale name was changed recently from DIS to ISO. Look at the /usr/share/locale directory for the right name. The change from DIS to ISO only happened in -CURRENT. Moreover, the '_' character was stripped from the ISO_8859 string . These changes in the locale names have not been MFC'd yet; as a consequence, the alias definition es_ES.DIS_8859-15:es_ES.ISO8859-15 must be added to /usr/X11R6/lib/X11/locale/locale.alias in order to get X11 working with the ISO8859-15 locale. Unfortunately, 4.5-RELEASE will be released with the old-fashioned locale names. I have just sent the patch for locale.alias to the x11/XFree86-4 port maintainer. Just my 0,02¤ ^- euro symbol ;-) Cheers, JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
