OpenLDAP 'container' objectClass
Hi. I'm trying to get the container structural objectClass in openldap-server-2.2.27 (from ports) enabled, but I can't find any references to 'container' in the schema files. Am I just missing something? -Kyle Mott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: discarded oversize frames
Have you found a solution to this? I am having the same problems on a machine very recently updated (cvsupped + buildworld on 4/14/2005): kernel.log:Feb 25 13:46:40 trinity kernel: rl0: discard oversize frame (ether type 3db4 flags 3 len 8381 max 1514) kernel.log:Apr 10 14:27:37 trinity kernel: rl0: discard oversize frame (ether type 5a84 flags 3 len 2614 max 1514) kernel.log:Apr 18 16:17:53 trinity kernel: rl0: discard oversize frame (ether type 1867 flags 3 len 16941 max 1514) After the message, the machine becomes completely unresponsive and I have to do a power-off, power-on reset. -Kyle David Malone wrote: On Fri, Feb 25, 2005 at 10:00:34AM -0500, Jonathan Pater wrote: fxp0: discard oversize frame (ether type 800 flags 3 len 1515 max 1514) Is this something I should be worried about, or is it indicative of something else faulty in the local network setup? This message is produced if the ethernet card receives a packet that is bigger than permitted by the MTU + the size of the ethernet header. For normal ethernet this means that packets should be = 1514 bytes. So, there are three ways to eliminate the the message: 1) Find the machine sending oversize packets and stop it. 2) Change the MTU on your interface using ifconfig, this will only work if the other machines on the network expect larget frames. 3) You could edit /usr/src/sys/net/if_ethersubr.c and remove the code that prints this error and then recompile your kernel. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Apache Signal 11
This just very recently started to happen (and I haven't upgraded Apache as of late either, or any other software for that matter). I keep getting this in my kernel.log on 2 different hosts: Mar 17 09:34:16 logsrv pid 38069 (httpd), uid 0: exited on signal 11 (core dumped) Mar 17 00:34:25 g1bs0n kernel: pid 9419 (httpd), uid 0: exited on signal 11 (core dumped) Both hosts are running 'apache+mod_ssl-1.3.33+2.8.22' plus 'php4-4.3.10', and a bunch of php modules that I don't want to list. i was able to get Apache running on g1bs0n by not starting ssl; however, Apache won't start on logsrv at all. Looking up man signal, SIGSEGV (11) is a segmentation violation. What can cause this on 2 different machines that haven't been updated in a while? I'm currently running a ports-cvsup, to verify that apache+mod_ssl either does or does not need to be updated. -Kyle Mott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't reboot after messing up my rc.conf file
mount -a vi /etc/rc.conf Running fsck is your prerogative. -Kyle Mott aklist_061666 wrote: Hi All: I was editing my rc.conf file and left off a quote mark, and now when I try to reboot I get an error and am prompted to drop into shell to fix it. The default prompt is /bin/sh, and if I hit return I get a prompt. How can I edit the file while I'm in that prompt? VI doesn't work...is there another text editor I can use to fix the file? TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP NCxxxx NIC cards
We have a DL585 with dual Gigabit Broadcom NIC's on AMD64-5.3-RELEASE-p5 (both of which are configured in use): bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2100 mem 0xf7fb-0xf7fb irq 25 at device 6.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5704 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:0e:7f:b0:b2:bf bge1: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2100 mem 0xf7fa-0xf7fa irq 24 at device 6.1 on pci2 miibus1: MII bus on bge1 brgphy1: BCM5704 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:0e:7f:b0:b2:be I'm not entirely sure which NC it is. -Kyle Mott Jerry McAllister wrote: Hi, Does anyone know anything about NIC cards offered in the HP 'Proliant' series - namely an: HP NC7761 PCI Gigabit NIC (embedded) or alternatively any of: HP NC7771 PCI-X Gigabit Server Adapter HP NC7170 Dual Port PCI-X 1000T Gigabit Server Adapter HP NC 310F PCI-X Gigabit Server Adapter HP NC320T PCI Express Gigabit Server Adapter, 10/100/1000T Unfortunately none of them show up with those designations in the supported hardware lists for either 4.11 or 5.3. Do they possibly fit in to one of the groups under a different name that you know of? One of our sites wants to buy one of these machines instead of the ones we have usually been spec-ing for them. Thanks, jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Digi PCI / XEM 16-Port
I have tried several times now to compile a GENERIC kernel on 4.10-STABLE with dgm0 (Digi Ports/16em, PCI version!) enabled, and have had no luck. Can anyone give me pointers? Right now, it's not showing up in dmesg (no errors, no warnings, nothing). The config line I have been using is below (but it's the one straight out of LINT). I've done a lot of googling and maillist searching; most of the documentation is for the ISA version, and not the PCI version. I've tried chaning 'at isa?' to 'at pci?' with no luck. My next guess would be to try 5.2.1, and then beyond that RedHat (though, I would really like to avoid using RH). device dgm0at isa? port 0x104 iomem 0xd -Kyle Mott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Rebuilding wtmp
Hi, I have several systems that report 'w' and 'who' wrong/corrupted: [EMAIL PROTECTED]:~# w USER TTY FROM LOGIN@ IDLE WHAT kyle p0 -31Dec69 - w Obviously, Dec 31st 1969 is not right: [EMAIL PROTECTED]:~# date Mon Jul 12 11:27:15 PDT 2004 I read a few manpages and did some google'ing, and couldn't find much of anything about rebuilding wtmp. I tried just moving wtmp to wtmp.old and then doing 'touch wtmp', then logging out and back in, but it still reads 31Dec69. Is there some way to fix this? Thanks all. (Note: Please CC me in any replies, I'm not a member of -questions). -Kyle Mott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Rebuilding wtmp
-Original Message- From: aardvark [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:40 PM To: Kyle Mott Cc: [EMAIL PROTECTED] Subject: Re: Rebuilding wtmp Kyle Mott disturbed my sleep to write: I read a few manpages and did some google'ing, and couldn't find much of anything about rebuilding wtmp. I tried just moving wtmp to wtmp.old and then doing 'touch wtmp', then logging out and back in, but it still reads 31Dec69. Is there some way to fix this? Thanks all. It's possible that there's some process holding open wtmp. (You could check this by adding lsof (list open files) from ports -- *very* handy to have around on general principle). If this is the case, probably the easiest way to fix things would be to rename the file, touch wtmp, then reboot. Thank's for the lsof tip, though I couldn't find anything using wtmp. I've tried rebooting with an empty wtmp plenty of times before, all to no avail. Interestingly enough, a Google for wtmp freebsd turned up this message from the FreeBSD-Security list: http://archives.neohapsis.com/archives/freebsd/2001-07/0055.html which suggests cp /dev/null /var/log/wtmp to fix things -- at least on Solaris. I tried this already, and it didn't work. On a system that I have a good, uncorrupted version of wtmp, I can do 'mv wtmp wtmp.old touch wtmp', then logout and log back in, and it reports the dates fine. I can also write a bunch of gibberish to wtmp (via /dev/random), and then logout and back in, and it still reports the dates correctly. I'm just confused. -Kyle Mott I am now blessing your keyboard... -- Saint Aardvark the Carpeted [EMAIL PROTECTED] Because the plural of Anecdote is Myth. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Rebuilding wtmp
Nevermind, I figured it out. I needed to rebuild ssh. Thanks everyone. -Kyle Mott -Original Message- From: aardvark [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:40 PM To: Kyle Mott Cc: [EMAIL PROTECTED] Subject: Re: Rebuilding wtmp Kyle Mott disturbed my sleep to write: I read a few manpages and did some google'ing, and couldn't find much of anything about rebuilding wtmp. I tried just moving wtmp to wtmp.old and then doing 'touch wtmp', then logging out and back in, but it still reads 31Dec69. Is there some way to fix this? Thanks all. It's possible that there's some process holding open wtmp. (You could check this by adding lsof (list open files) from ports -- *very* handy to have around on general principle). If this is the case, probably the easiest way to fix things would be to rename the file, touch wtmp, then reboot. Interestingly enough, a Google for wtmp freebsd turned up this message from the FreeBSD-Security list: http://archives.neohapsis.com/archives/freebsd/2001-07/0055.html which suggests cp /dev/null /var/log/wtmp to fix things -- at least on Solaris. I am now blessing your keyboard... -- Saint Aardvark the Carpeted [EMAIL PROTECTED] Because the plural of Anecdote is Myth. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
