close() failing with ECONNRESET
I see that since FreeBSD 6.3 close() can fail with: [ECONNRESET] The underlying object was a stream socket that was shut down by the peer before all pending data was delivered. Could someone explain what this is useful for? I'm not aware of any other OS that does this. Is this really something that many programs care about? I'd think there are only very few, and those exceptions could use some other syscall before close() to find out about it. Instead now you're forcing everyone else to change their code from: if (close(fd) 0) log(..); to if (close(fd) 0 errno != ECONNRESET) log(..); or to write some wrapper to close(). ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
a NIS problem
HI Today I setup a NIS server in Freebsd6.2. Now, every client only run ypbind -broadcast to link this server the NIS server's domainname is server.nis if the client run ypbind server.nis can't link to the server. anyone can tell me how to debug it? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD hacker 101
bbs.chinaunix.net freebsdchina.org 2008-01-24 _ Best Regard Timo msn: [EMAIL PROTECTED] web: https://stand.eicp.net 发件人： william wong 发送时间： 2008-01-24 15:32:18 收件人： freebsd-hackers@freebsd.org 抄送： 主题： FreeBSD hacker 101 Hi, Are there any docments or pointers to get me started hacking around my 6.3asap? Building toochains, submitting patches etc or i just follow most of the conventions in the Linux kernel development community? regards, william ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel time sync enabled
hi, I'am running freebsd6.2 with apache now in /var/log/message has follow info. anyone can tell me what's the meaning? Jan 9 01:01:02 server1 sshd[4345]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:02 server1 sshd[4345]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4396]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4396]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4387]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4387]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:02:20 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 01:19:23 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 01:53:34 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 02:10:40 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 04:27:20 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 05:52:45 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 10:08:50 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 10:25:54 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 11:26:35 server1 sshd[90201]: error: accept: Software caused connection abort 2008-01-09 _ Best Regard Timo msn: [EMAIL PROTECTED] web: https://stand.eicp.net ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: kernel time sync enabled
thanks, I have repail it 2008-01-09 _ Best Regard Timo msn: [EMAIL PROTECTED] web: https://stand.eicp.net 发件人： Jeremy Chadwick 发送时间： 2008-01-09 19:47:03 收件人： timo 抄送： freebsd-hackers 主题： Re: kernel time sync enabled On Wed, Jan 09, 2008 at 06:51:45PM +0800, timo wrote: anyone can tell me what's the meaning? Jan 9 01:02:20 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 01:19:23 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 01:53:34 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 02:10:40 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 04:27:20 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 05:52:45 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 10:08:50 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 10:25:54 server1 ntpd[46085]: kernel time sync enabled 2001 Taken from our ntp.conf (used across all our production machines): # maxpoll 9 is used to work around PLL/FLL flipping, which # happens at exactly 1024 seconds (the default maxpoll value). # Another FreeBSD member recommended using 9 instead. # http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031512.html # server 0.north-america.pool.ntp.org maxpoll 9 iburst server 1.north-america.pool.ntp.org maxpoll 9 server 2.north-america.pool.ntp.org maxpoll 9 -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interacting with ISA PnP devices.
Ted, from my limited experience with FreeBSD ISA PnP cards (I'm fiddling around with the 3COM Etherlink III driver) I would suggest that you need to write a driver to talk to the card simply because you have to be able to retrieve the card settings. However I found the ISA PnP functionality extremly easy to use considering that I am not a FreeBSD driver guru. That said I would estimate that writing the PnP Init part of the driver shouldn't take more than 100-150 lines of C. The main problem would be adding all the functionality that your Windows driver already incorporates ... Timo On Thu, Aug 12, 1999 at 05:25:05PM -0400, tbusw...@acadia.net wrote: Hi, What is the path of least resistance for getting an unsupported ISA PnP device to the point where you can do I/O to it (inb,outb)? Do I need a driver, or is there some general purpose way for getting the device up to the point that you can use /dev/io and a user space application? (on -current) If I need to write a driver, would a device driver that just maps the device be considered useful (feasible to implement?)? This specific device is a winmodem which I believe I have enough hardware documentation to fiddle with, once I get past the ISA PnP interface. Thanks, -Ted (ISA PnP newbie) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
PNPifying the 'ep' driver
Hi all, I sent a similar mail to -current a while ago but by the number of responses I got i believe it was the wrong forum. Please bear with me while I go about it again. Problem: One of my FreeBSD boxes is loaded nearly to capacity with ISA and PCI cards. In order to make it work at all I had to disable some of the on-board peripherals (like IDE) and rely on PNP and PCI confiugration to sort out the remaining mess. While everything works fine(?) in evil Bill's comsumer OSs I have to rip out the sound card every time to make FreeBSD work. As this was not doing the MoBo or my temper any good I started to investigate why. It turns out that the problem seems to be the way that 3Com 3C509s handle PNP. Set to PNP mode, the card patiently waits for the BIOS to assign I/O and IRQ. When the ep driver does go about to query the card, it returns the cards preferred default settings, not the PNP assigned ones. Big Ouch, as the card driver suddenly waits for the Soundblaster AWE32 to trigger an interrupt so it can go about reading data from the card :-(. To the OSs creadit networking still works, albeit with a 64 sec ping roundtrip time ... Well, I dug deeper and found that the ep driver had been spared the embarrasment of being converted to the pnp framework ;-). An hours worth of hacking solved that but now I hit an impasse that I can't seem to resolve with out the card documentation. Questions: 1. I emailed 3Com support asking 'Where could I get a Technical Reference Manual for this card?'. They acknowledged that the had passed that email on internally but are obviously taking their time to answer this question. Does anyone have a contact inside 3Com that might be able to help speed up this process a bit? Or alternatively, can anyone help out with the relevant information while I wait for 3Com to come back to me? 2. From what I see so far I would have to reconfigure the card inside the driver (much like a PCMCIA card is configured on insertion). Am I breaking any unwritten rules here? I obviously want to have the changes put into the tree once everyone is satisfied that they work, so I better make sure that I don't violate any unwritten rules here. Regards, Timo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
