Re: cloning a FreeBSD HDD
> On Saturday 25 March 2006 04:42, Mike Meyer wrote: > > One thing: 1m is a bit small for modern systems. Or for not-so-modern > > systems. Since nothing else is running, you might as well use all the > > memory you've got, or as big as you can get a process to be. 128m or > > more is perfectly reasonable. > > It won't go any faster.. > > In a modern system the CPU is so much faster than the disk than anything > above > about 16k would be enough. I found 64k to be optimal (e.g, max performance) on most machines Timestamp: 0x4428D30F [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: Programs not accepting input?
On Monday, 27 March 2006 at 20:30:52 -0500, Mike Meyer wrote: > In <[EMAIL PROTECTED]>, Greg 'groggy' Lehey <[EMAIL PROTECTED]> typed: >>> The focus management and the highlighting of the window manager >>> decoration are not physically connected in any way, so a bug in the >>> window manager might cause it to do the highlighting but forget to >>> give the focus to the application. >> But mouse focus and keyboard focus are the same, right? > > There isn't a "mouse focus". Mouse events are tied to window they > happen in, not the one with focus. If you use a window manager that > doesn't change the keyboard focus on mouse events, it's possible to > have mouse events happen in a window that doesn't have the focus. Ah, good to know. That changes things somewhat. Greg -- See complete headers for address and phone numbers. pgpXBFQQPhFVN.pgp Description: PGP signature
Re: Re: Programs not accepting input?
In <[EMAIL PROTECTED]>, Greg 'groggy' Lehey <[EMAIL PROTECTED]> typed: > > The focus management and the highlighting of the window manager > > decoration are not physically connected in any way, so a bug in the > > window manager might cause it to do the highlighting but forget to > > give the focus to the application. > But mouse focus and keyboard focus are the same, right? There isn't a "mouse focus". Mouse events are tied to window they happen in, not the one with focus. If you use a window manager that doesn't change the keyboard focus on mouse events, it's possible to have mouse events happen in a window that doesn't have the focus. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: Programs not accepting input?
On Monday, 27 March 2006 at 7:03:23 -0600, Sergey Babkin wrote: >> Same here. As mentioned in the original message, I can use the mouse >> to open a new window under firefox. The new window will accept >> keyboard input, the old one won't. It's almost as if it's deadlocking >> on input. >> >> Reminder: my final question was "how do I go about debugging this >> problem?". > > Does it happen with any kind of programs? No. So far I've only seen it with firefox, emacs and kklondike. > If yes, it would probably be something focus-related (and you'd be > able to see that the Focus event is not coming in). As already mentioned, this is not the case. I've seen this kind of problem too. > The focus management and the highlighting of the window manager > decoration are not physically connected in any way, so a bug in the > window manager might cause it to do the highlighting but forget to > give the focus to the application. But mouse focus and keyboard focus are the same, right? The windows respond to the mouse, but not to the keyboard. The remainder of your reply seems to build on the assumption that there is no focus. I'll leave it there in case I misunderstood and you want to refer to it. > To debug that you can add debugging printout to the WM. Or I've had > a script that sort of decoded the X protocol, so if you can get the > dump of these (maybe with ktrace), you can decode the dump and see > what happens with the focus. I'll look for it in my archives. > > If no, it might be something with the keyboard event translation to > keysyms/text. You can debug this by writing a test program that > would do it own dispatch loop - i.e. call XEvent() and then > XtDispatchEvent() (or some close names - I might not remember them > right), and print the debugging messages. So if you see that > XEvent() is getting events but then nothing comes out of dispatching > them, then the translation is broken somewhere. > > I might be able to find this kind of a program > in my archives too, I'll look around. thanks. > BTW, one place where the keyboard events might disappear is the > Input Method handling code. But I don't think that you run any Input > Methods. Not explicitly. Greg -- See complete headers for address and phone numbers. pgpKxcplWbAnS.pgp Description: PGP signature
Re: cloning a FreeBSD HDD
On Saturday 25 March 2006 04:42, Mike Meyer wrote: > One thing: 1m is a bit small for modern systems. Or for not-so-modern > systems. Since nothing else is running, you might as well use all the > memory you've got, or as big as you can get a process to be. 128m or > more is perfectly reasonable. It won't go any faster.. In a modern system the CPU is so much faster than the disk than anything above about 16k would be enough. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp07LoNZbjGc.pgp Description: PGP signature
Re: cloning a FreeBSD HDD
In <[EMAIL PROTECTED]>, Vasil Dimov <[EMAIL PROTECTED]> typed: > On Fri, Mar 24, 2006 at 06:19:13PM +0100, Dirk GOUDERS wrote: > Without reading it, I would first try this, it's quite straightforward > > * boot into single user mode (enter "boot -s" at loader prompt) > * make sure filesystems are mounted readonly (mount) > dd if=/dev/ad0 of=/dev/ad1 bs=1m > (where ad0 is your disk with data and ad1 is your new disk, make sure > you do not swap them :) Doesn't really matter in single user mode - you'll just copy the swap over. But yeah, this procedure works fine for me in the past. One thing: 1m is a bit small for modern systems. Or for not-so-modern systems. Since nothing else is running, you might as well use all the memory you've got, or as big as you can get a process to be. 128m or more is perfectly reasonable. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Direct access to hadware
In message: <[EMAIL PROTECTED]> Eder <[EMAIL PROTECTED]> writes: : I would like to know if exite some header ".h" in FreeBSD so : that I can make a direct access to hadware in machine with C. Yes. There is. However, without knowing what you want to do, it is impossible to recommend which one of the many .h files can enable this functionality. What's your hardware look like that you wish to get access to. One caveat: unless you have a driver, you can't have a interrupt. Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Direct access to hadware
Hi all, I would like to know if exite some header ".h" in FreeBSD so that I can make a direct access to hadware in machine with C. Thanks, Eder -- Linux is for people who hate Windows, BSD is for people who love UNIX" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
On Mon, Mar 27, 2006 at 10:59:16PM +0400, Maxim Konovalov wrote: > [...] > > > ~100 datagrams per second, not a lot. Perhaps they are huge. > > > > Not that I've noticed. It's syslogd, DHCP, DNS, and flow-capture > > from a variety of devices, all generally small packets. > > I know nothing about your netflow setup but it can generate a > huge amount of udp traffic. Check 'pkts' and 'lost' fields in > /var/log/flow-capture. > > > > > > How much cpu time does syslogd use? > > > > > > > > Not much. ps -ax | grep syslog gives: > > > > > > > > 4317 ?? Ss 0:01.60 /usr/sbin/syslogd -l /var/run/log -l > > > > /var/named/var/run/log > > > > > > Try to remove a log socket for named and restart syslogd. > > > > Removed the named socket and restarted. We'll see what happens. > [...] > > Can you check there is nothing from syslogd on the serial console? I changed that this morning in response to an earlier suggestion. To be sure, I just ran: logger -p local0.err "test message" and got a message in /var/log/console.log, nothing on the serial console. BTW, running syslogd with -n seems to help the problem -- not cure it, mind you, but reduces its severity. ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ "The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
[...] > > ~100 datagrams per second, not a lot. Perhaps they are huge. > > Not that I've noticed. It's syslogd, DHCP, DNS, and flow-capture > from a variety of devices, all generally small packets. I know nothing about your netflow setup but it can generate a huge amount of udp traffic. Check 'pkts' and 'lost' fields in /var/log/flow-capture. > > > > How much cpu time does syslogd use? > > > > > > Not much. ps -ax | grep syslog gives: > > > > > > 4317 ?? Ss 0:01.60 /usr/sbin/syslogd -l /var/run/log -l > > > /var/named/var/run/log > > > > Try to remove a log socket for named and restart syslogd. > > Removed the named socket and restarted. We'll see what happens. [...] Can you check there is nothing from syslogd on the serial console? -- Maxim Konovalov ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
On Mon, Mar 27, 2006 at 10:35:11PM +0400, Maxim Konovalov wrote: > [] > > > > > >ns1/etc;netstat -s | grep full > > > > > >Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory > > > > > >122066 dropped due to full socket buffers > > > > > >ns1/etc; > > > > > > > > > > > >I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it > > > > > >still happens. > > > > > > That's not enough. You need to teach syslogd to use this new value. > > > > I don't see this in syslogd(8); I presume it require source hacking? > > Yes. OK, I'm going to avoid that for the moment. I haven't touched C in five years now, I'd probably confuse it even worse. Besides, I've had centralized logging hosts with this much activity -- and far more -- previously. I can't believe that this environment is so special that it requires that sort of customization. > [...] > > > netstat -sp udp | grep 'datagrams received'; sleep 10; \ > > > netstat -sp udp | grep 'datagrams received' > > > > 158169 dropped due to full socket buffers > > 2467251 datagrams received > > sleeping... > > 158903 dropped due to full socket buffers > > 2468299 datagrams received > > ~100 datagrams per second, not a lot. Perhaps they are huge. Not that I've noticed. It's syslogd, DHCP, DNS, and flow-capture from a variety of devices, all generally small packets. > > > How much cpu time does syslogd use? > > > > Not much. ps -ax | grep syslog gives: > > > > 4317 ?? Ss 0:01.60 /usr/sbin/syslogd -l /var/run/log -l > > /var/named/var/run/log > > Try to remove a log socket for named and restart syslogd. Removed the named socket and restarted. We'll see what happens. > > Process has been running for about five minutes at that point. > > > > Another point that might be of interest: > > > > ns1/etc;rc.d/syslogd restart Stopping syslogd. Waiting for PIDS: > > 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, > > 4317, 4317, 4317, 4317, 4317, 4317, 4317 Starting syslogd. > > What's the /var filesystem type? Something like gmirror? Nope. It's a big SATA drive with a swap partition at the top and the rest vanilla UFS2: ad4: 38146MB at ata2-master SATA150 ad5: 476940MB at ata2-slave SATA150 ns1~;mount /dev/ad4s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad4s1d on /tmp (ufs, local, soft-updates) /dev/ad4s1e on /usr (ufs, local, soft-updates) /dev/ad4s1f on /home (ufs, local, soft-updates) /dev/ad5s1d on /var (ufs, local, soft-updates) devfs on /var/named/dev (devfs, local) > diff -u /etc/syslog.conf /usr/src/etc/syslog.conf? # $FreeBSD: src/etc/syslog.conf,v 1.28 2005/03/12 12:31:16 glebius Exp $ -#$Id: syslog.conf,v 1.11 2006/03/17 18:56:18 system_mwl Exp system_mwl $ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. -*.err;kern.warning;auth.notice;mail.crit;local4.none /var/log/console.log -#*.err;kern.warning;auth.notice;mail.crit;local4.none /dev/console -*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err;local0.none;local 1.none;local2.none;local3.none;local4.none;local5.none;local6.none;local7.none / var/log/messages +*.err;kern.warning;auth.notice;mail.crit /dev/console +*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/message s security.* /var/log/security auth.info;authpriv.info/var/log/auth.log mail.info /var/log/maillog lpr.info /var/log/lpd-errs ftp.info /var/log/xferlog cron.* /var/log/cron -daemon.debug /var/log/daemon.debug *.=debug /var/log/debug.log *.emerg* -local0.* /var/log/router -local1.* /var/log/switch -#local2.* /var/log/kvm -#local 2-3 can be used -local4.* /var/log/pix -local5.* /var/log/vpn -local7.* /var/log/dhcpd # uncomment this to log all writes to /dev/console to /var/log/console.log #console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work -*.*/var/log/all.log +#*.*
Re: syslogd not draining
[] > > > > >ns1/etc;netstat -s | grep full > > > > >Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory > > > > >122066 dropped due to full socket buffers > > > > >ns1/etc; > > > > > > > > > >I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it > > > > >still happens. > > > > That's not enough. You need to teach syslogd to use this new value. > > I don't see this in syslogd(8); I presume it require source hacking? Yes. [...] > > netstat -sp udp | grep 'datagrams received'; sleep 10; \ > > netstat -sp udp | grep 'datagrams received' > > 158169 dropped due to full socket buffers > 2467251 datagrams received > sleeping... > 158903 dropped due to full socket buffers > 2468299 datagrams received ~100 datagrams per second, not a lot. Perhaps they are huge. > > How much cpu time does syslogd use? > > Not much. ps -ax | grep syslog gives: > > 4317 ?? Ss 0:01.60 /usr/sbin/syslogd -l /var/run/log -l > /var/named/var/run/log Try to remove a log socket for named and restart syslogd. > Process has been running for about five minutes at that point. > > Another point that might be of interest: > > ns1/etc;rc.d/syslogd restart Stopping syslogd. Waiting for PIDS: > 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, > 4317, 4317, 4317, 4317, 4317, 4317, 4317 Starting syslogd. What's the /var filesystem type? Something like gmirror? diff -u /etc/syslog.conf /usr/src/etc/syslog.conf? -- Maxim Konovalov ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
On Mon, Mar 27, 2006 at 10:01:42PM +0400, Maxim Konovalov wrote: > On Mon, 27 Mar 2006, 12:38-0500, Michael W. Lucas wrote: > > > On Mon, Mar 27, 2006 at 06:18:50PM +0200, Borja Marcos wrote: > > > >I've got a machine running syslogd, DNS, DHCP, flow-capture, and other > > > >assorted UDP-loving programs. Occasionally, they all stop working. > > > >The machine has been up for a couple of hours now, and I see: > > > > > > > >ns1/etc;netstat -s | grep full > > > >Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory > > > >122066 dropped due to full socket buffers > > > >ns1/etc; > > > > > > > >I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it > > > >still happens. > > That's not enough. You need to teach syslogd to use this new value. I don't see this in syslogd(8); I presume it require source hacking? > > > >After some help from questions@, I'm pretty sure that the culprit is > > > >syslogd. > > > > > > > >udp4 0 0 *.67 *.* > > > >udp4 43414 0 *.514 *.* > > > >udp4 0 0 *.49661*.* > > > > > > Are you using a serial console? I had similar problems in the past > > > due to the serial port flow control. > > > > I've disabled syslog to the console, writing instead to > > /var/log/console.log. > > > > Moments after doing that, the problem reoccured. Thanks, Borja, but > > no success. :-( > > > > Any other suggestions, folks? > > What's the incoming udp datagrams rate? > > netstat -sp udp | grep 'datagrams received'; sleep 10; \ > netstat -sp udp | grep 'datagrams received' 158169 dropped due to full socket buffers 2467251 datagrams received sleeping... 158903 dropped due to full socket buffers 2468299 datagrams received > How much cpu time does syslogd use? Not much. ps -ax | grep syslog gives: 4317 ?? Ss 0:01.60 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log Process has been running for about five minutes at that point. Another point that might be of interest: ns1/etc;rc.d/syslogd restart Stopping syslogd. Waiting for PIDS: 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317, 4317 Starting syslogd. ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ "The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
On Mon, 27 Mar 2006, 12:38-0500, Michael W. Lucas wrote: > On Mon, Mar 27, 2006 at 06:18:50PM +0200, Borja Marcos wrote: > > >I've got a machine running syslogd, DNS, DHCP, flow-capture, and other > > >assorted UDP-loving programs. Occasionally, they all stop working. > > >The machine has been up for a couple of hours now, and I see: > > > > > >ns1/etc;netstat -s | grep full > > >Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory > > >122066 dropped due to full socket buffers > > >ns1/etc; > > > > > >I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it > > >still happens. That's not enough. You need to teach syslogd to use this new value. > > >After some help from questions@, I'm pretty sure that the culprit is > > >syslogd. > > > > > >udp4 0 0 *.67 *.* > > >udp4 43414 0 *.514 *.* > > >udp4 0 0 *.49661*.* > > > > Are you using a serial console? I had similar problems in the past > > due to the serial port flow control. > > I've disabled syslog to the console, writing instead to > /var/log/console.log. > > Moments after doing that, the problem reoccured. Thanks, Borja, but > no success. :-( > > Any other suggestions, folks? What's the incoming udp datagrams rate? netstat -sp udp | grep 'datagrams received'; sleep 10; \ netstat -sp udp | grep 'datagrams received' How much cpu time does syslogd use? -- Maxim Konovalov ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
On Mon, Mar 27, 2006 at 06:18:50PM +0200, Borja Marcos wrote: > >I've got a machine running syslogd, DNS, DHCP, flow-capture, and other > >assorted UDP-loving programs. Occasionally, they all stop working. > >The machine has been up for a couple of hours now, and I see: > > > >ns1/etc;netstat -s | grep full > >Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory > >122066 dropped due to full socket buffers > >ns1/etc; > > > >I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it > >still happens. > > > >After some help from questions@, I'm pretty sure that the culprit is > >syslogd. > > > >udp4 0 0 *.67 *.* > >udp4 43414 0 *.514 *.* > >udp4 0 0 *.49661*.* > > Are you using a serial console? I had similar problems in the past > due to the serial port flow control. I've disabled syslog to the console, writing instead to /var/log/console.log. Moments after doing that, the problem reoccured. Thanks, Borja, but no success. :-( Any other suggestions, folks? Thanks, ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ "The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
On Mon, Mar 27, 2006 at 06:18:50PM +0200, Borja Marcos wrote: > >I've got a machine running syslogd, DNS, DHCP, flow-capture, and other > >assorted UDP-loving programs. Occasionally, they all stop working. > >The machine has been up for a couple of hours now, and I see: > > > >ns1/etc;netstat -s | grep full > >Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory > >122066 dropped due to full socket buffers > >ns1/etc; > > > >I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it > >still happens. > > > >After some help from questions@, I'm pretty sure that the culprit is > >syslogd. > > > >udp4 0 0 *.67 *.* > >udp4 43414 0 *.514 *.* > >udp4 0 0 *.49661*.* > > Are you using a serial console? I had similar problems in the past > due to the serial port flow control. Yes, I am. So, if I disable syslogd writing to the console, it might clear this up? Thanks, ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ "The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Programs not accepting input?
On Mon, Mar 27, 2006 at 11:21:53AM +0200, Frank B. Scholl wrote: > > i followed this discussion so far and wondered what your techniques are to > have your running programs accepting input again. in my case, this phenomenon > heavily depends on the windowmanager you chose. when being on fluxbox and > having a running instance of firefox, it every once in a while refuses > keyboard input. i have had this with other gtk apps, too, for example > sylpheed. > > to circumvent the problem and getting your application back to accept further > keyboard input, i just switch workspaces back and forth and thats it, I've tried everything from switching desktops to killing fvwm2. This is how I know it's not window-manager related. As I said before, I can have two rxvts side-by-side. I focus over the left one, type, nothing appears. I focus over the right one, type, keyboard works. Focus back over the left one, nothing. Rinse, repeat. The problem happens more often with GTK apps than a plain rxvt. It's difficult to reproduce the problem, so it's nearly impossible to test. If it were more repeatable, I would have written a test client. Next time it happens, I'll try xev. But I haven't had the problem since I stopped using x11vnc. I only use the nVidia drivers and x.org. -- Rick C. Petty ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd not draining
I've got a machine running syslogd, DNS, DHCP, flow-capture, and other assorted UDP-loving programs. Occasionally, they all stop working. The machine has been up for a couple of hours now, and I see: ns1/etc;netstat -s | grep full Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory 122066 dropped due to full socket buffers ns1/etc; I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it still happens. After some help from questions@, I'm pretty sure that the culprit is syslogd. udp4 0 0 *.67 *.* udp4 43414 0 *.514 *.* udp4 0 0 *.49661*.* Are you using a serial console? I had similar problems in the past due to the serial port flow control. Borja. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
syslogd not draining
Hi, I've got a machine running syslogd, DNS, DHCP, flow-capture, and other assorted UDP-loving programs. Occasionally, they all stop working. The machine has been up for a couple of hours now, and I see: ns1/etc;netstat -s | grep full Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory 122066 dropped due to full socket buffers ns1/etc; I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it still happens. After some help from questions@, I'm pretty sure that the culprit is syslogd. udp4 0 0 *.67 *.* udp4 43414 0 *.514 *.* udp4 0 0 *.49661*.* Things run perfectly for a while, and then we suddenly stop answering UDP requests. We continue not answering UDP requests until I restart syslogd. syslogd -d didn't give anything interesting. I'm now running syslogd -n, to see if that helps. I'm also restarting syslogd every fifteen minutes, to ensure that the problem can last no longer than 14 minutes. :-) Anyone interested in why syslogd is not draining the queue? Thanks, ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ "The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Programs not accepting input?
Greg 'groggy' Lehey wrote: Same here. As mentioned in the original message, I can use the mouse to open a new window under firefox. The new window will accept keyboard input, the old one won't. It's almost as if it's deadlocking on input. Just a "me too". I used to get this with mozilla just as you described for Firefox but haven't had it in a while (fingers crossed). This is using standard Xorg server, single head display, simple window manager (fvwm2). Some time ago I switched to the NVidia driver over the Xorg one, but I really don't know that this is related. Just that I switched some time ago and that I haven't had the lockup in a while. For all I know, I unconsciously stopped doing whatever it was that triggered the lockup :-( --Alex ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Programs not accepting input?
hello, i followed this discussion so far and wondered what your techniques are to have your running programs accepting input again. in my case, this phenomenon heavily depends on the windowmanager you chose. when being on fluxbox and having a running instance of firefox, it every once in a while refuses keyboard input. i have had this with other gtk apps, too, for example sylpheed. to circumvent the problem and getting your application back to accept further keyboard input, i just switch workspaces back and forth and thats it, no matter on what windowmanager i am working. i never have desktops running, mostly isolated gtk apps, but from subjective experience i can tell that people running full blown gnome desktops, dont have such problems. as well as it does not seem to happen with qt apps for me. obviously, some windowmanagers dont deliver input correctly or some gtk apps have a problem with receiving a certain kind of message type. frank ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
