??: fxp half-duplex problemm
What if you do ifconfig fxp0 media autoselect I don't undertand. Autoselect is turned on by default. I have full-duplex then. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ??: fxp half-duplex problemm
At 06:30 PM 12/11/01 +0300, Sergey Matveychuk wrote: What if you do ifconfig fxp0 media autoselect I don't undertand. Autoselect is turned on by default. I have full-duplex then. If the switch supports full duplex why would you not want to use it ? ---Mike Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
??: ??: fxp half-duplex problemm
If the switch supports full duplex why would you not want to use it ? It became buggy in full-duplex. It send zerro packets permanently in full-duplex port. Link works but slowlier. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Dec 11 cvsup gives system that wont start ipf
After cvsup'ing last night, and build, install, world, merging /etc, I found that at bootup that ipf was not starting. The error message was very difficult to see but it looked like somewhere fopen was not able to open ipf. So as a quick fix I put my ipf -Fa -f /etc/ipf.rules into rc.local. Has anyone else seen this, or have a better fix? I looked at /etc/defaults/rc.conf and did not see any new change in syntax of the ipf related lines. Thanks, Rob. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: OpenSSH not updating
On Mon, 10 Dec 2001, Chris Faulhaber wrote: On Tue, Dec 11, 2001 at 03:02:33PM +1100, Rob B wrote: ewps :) If I ran the patch again, answering N to the -R question, would this correct my goof? Yep. Nope. patch won't ask the -R question, since the patch has not been previously applied :) -- David Taylor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
fetch through ftp-proxydoesn´t work on FreBSD 4.3-STABLE
Hi ! Is it a known issue, that fetch doesn´t work via local ftp proxy (squid) ? I updated the ports collection manually. Everything runs fine, if fetch can get something via http proto. Whenever something should be fetched via ftp proto, it does nothing at all and I get error code 999 (protocol error). In my root´s .cshrc I added: setenv FTP_PROXY localhost:3128 setenv FTP_PASSIVE_MODEYES setenv HTTP_PROXY localhost:3128 In /etc/make.conf I configured: HTTP_PROXY=localhost:3128 FTP_PROXY=localhost:3128 FTP_PASSIVE_MODE=yes In squids logfile I see the successfull fetch attempts via http, but no single line, when something should be fetched via ftp. In the process status I see, that fetch is executed as follows a) for ftp (doesn´t work) 7137 p1 S+ 0:00.01 /usr/bin/fetch -A ftp://ftp.xemacs.org/pub/xemacs/xemacs-21.1/xemacs-21.1.14.tar.gz b) for http (works) /usr/bin/fetch -A http://prdownloads.sourceforge.net/amanda/amanda-2.4.2p2.tar.gz Squids log tells me only something about the fetch using http proto ... 1008090948.039 34701 127.0.0.1 TCP_MISS/000 560886 GET http://prdownloads.sourceforge.net/amanda/amanda-2.4.2p2.tar.gz - FIRST_UP_PARENT/byfwg5.bayer-ag.com - Is there a bug in FreeBSD 4.3´s libfetch ??? Or did I mis-spell a configuration variable ??? Setting FTP_PASSIVE_MODE in .cshrc and /etc/make.conf was only a hack, wihout it didn´t work as well ... Any comments ??? Thanks Andreas /// Andreas /// To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: fetch through ftp-proxy doesnt work on FreBSD 4.3-STABLE
On Tue, Dec 11, 2001 at 06:19:26PM +0100, [EMAIL PROTECTED] wrote: Is it a known issue, that fetch doesn't work via local ftp proxy (squid) ? Squid is not ftp proxy. It can be used as ftp-over-http proxy, that is NOT the same thing. I updated the ports collection manually. Everything runs fine, if fetch can get something via http proto. Whenever something should be fetched via ftp proto, it does nothing at all and I get error code 999 (protocol error). In my root's .cshrc I added: setenv FTP_PROXY localhost:3128 setenv FTP_PASSIVE_MODEYES Delete these. You disinform fetch about type of your proxy. setenv HTTP_PROXY localhost:3128 This is enough for fetch. It will use http protocol both for http and ftp transfers. That is what squid wants. Eugene Grosbein. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
libs missing recently?
Just finished clean install of two snaps - 2000 and 2001 using x-kern-developer - both seem to be missing some important stuff: # XF86_SVGA /usr/libexec/ld-elf.so.1: Shared object libxpg4.so.2 not found Broken? =) Please reply directly if you have any info - I think my procmail is sick of mailing lists for a while. (I *don't need help fixing this.) Thanks! -Mike msg38297/pgp0.pgp Description: PGP signature
Re: syslog lose lines in log
On Mon, Dec 10, 2001 at 01:02:57PM -0600, Vlad Marchenko wrote: Need advise on my problem. I have mail application that sends a lot of lines to MAIL log: 100+ lines per second. Since we have stats based on analyzing maillog, it's important for us to have ALL lines. I noticed that under that load, syslog lose at least 30-40% of all lines. Digging the situation I found that it happens because DGRAM kind of socket used for delivering messages to syslogd by syslog(3). OK, I've installed /usr/ports/system/syslog-ng that supports STREAM unix sockets, and patched /usr/src/lib/libc/gen/syslog.c to have SOCK_STREAM type of socket when opening socket in function connectlog(): Without actually looking at the validity of the code, does the mailing application generating this noise actually use the syslog(3) in libc? -- Crist J. Clark [EMAIL PROTECTED] 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
ian j hart wrote:
ian j hart wrote:
Chad R. Larson wrote:
On Fri, Dec 07, 2001 at 01:33:15PM -0800, Brady Montz wrote:
Yeah, I'm using soft updates too. My crashes are generally the
same as Richards - no panic, just a freeze. Except my screen
doesn't go blank.
For what it's worth, I'm using soft updates on a web server that gets
steady if not heavy use. Built from RELENG_4_3, and no problems at
all.
-crl
--
Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm?
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Me 2 :(
I have a total lockup, screen is not blank (Matrox G400).
I turned off soft updates and did a boot -v and got some
console messages, so this is worth a try. Unfortunately the
messages don't make it to the logs, presumably because the
disk and/or disk subsystem is fubar'd. The one time a got
a spontaineous reboot I was out of the room making coffee
(typical).
Anyway the messages are something like
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. done
It's not always the same drive.
There were also some of my favorite UDMA ICRC errors, but
I didn't catch those. For those with long memories this is
the same box I've had UDMA problems with before (numerous
posts with UDMA ICRC in subject) but it's been well behaved
since early July. Maybe I haven't pushed it hard enough.
I also got one instance of unexpected soft update inconsisency
while fscking. Maybe this is to be expected if the drive just
dies.
What's interesting is the behavior seems to have changed. On
previous occasions the driver would keep resetting and then
drop to pio mode. Now it seems to lock after the first reset.
I'll try to confirm this behavior.
I set pio mode on all drives and I managed to complete my
torture test.
One more thing. Sometimes there's a clunk from the drive{s)
when it dies. Parking the heads?
FWIW -
VIA ATA33 controller
4x UDMA 66 drives
vinum mirror /var
vinum mirrored stripes /usr
Drat, spoke too soon.
soft updates on, dma off. Hang (in kde) followed by black
screen and reboot. This time vinum died on startup and I
had an anxious 10 minutes starting all the subdisks.
I'd better test the memory. Then I'll try booting from
the backup root in case ad0 is toast. I guess duff hardware is
looking more likely.
I noticed some UDMA errors when rebooting from single
user, which failed to sync 1 block. Of course these scroll
off screen too quick to be readable, but the head parking
noise was again apparent. APM is disabled.
--
ian j hart
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Update:
I couldn't prove the memory faulty but I did discover a useful
factlet which was missed out of the M/B handbook. Apparently
the VIA MVP3 chipset only supports 16MxN RAM when you have
more than 64Mb. This is not what I had. I updated the BIOS and
sure enough the board failed to detect all the RAM. I've
swapped it out. Maybe some update finally tickled the feature
hard enough to cause a panic.
I also did a full build, and this seems to have fixed some
weirdness with md0. Either I cvsup'd at a bad time or (more
likely) I fluffed the mergemester.
I'll thrash the bejesus out of the drives and see what happens.
--
ian j hart
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
