On Sun, 12 Feb 2006 20:46:08 -0800 (PST) "Kjetil S. Matheussen" <kjetil@xxxxxxxxxxxxxxxxxx> wrote: > Das_Watchdog > ============ > > ABOUT > ----- > Das_Watchdog is a program heavily and shamefully inspired by the > rt_watchdog program made by Florian Schmidt: > http://tapas.affenbande.org/?page_id=38 Hehe, why shamefully? This is open source, baby. So i'm glad there's some alternative to my messy code ;) And btw: the two programs are still a bit different. rt_watchdog is a daemon. I have wondered about how to make it known to the user that it has kicked in. The only solution i found was to write into the logs. Opening an xwindow is an interesting solution. Does linux maybe even have a standardized way for this kinda stuff? > However, this one has some improvements: > > 1. It works with 2.4 kernels as well as 2.6. (well, at least I think it > works with 2.6...) > 2. Instead of permanently setting all realtime processes to run > non-realtime, das_watchdog only sets them temporary. > 3. When the watchdog kicks in, an X window should pop up that tells you > whats happening. (just close it after reading the message). > > > INSTALLING > ---------- > make > cp das_watchdog /usr/local/sbin/ > echo '/usr/local/sbin/das_watchdog & >/dev/null' >>/etc/rc.local This assumes an initscript style that's not used on all linux systems. > reboot Also i wonder: Is it safe to simply use a static int as "event counter"? Might this not fail on SMP boxes? I think i make a similar mistake by using a volatile int (not as a counter, just as a exit state indicator) instead. Any gurus care to comment? Flo -- Palimm Palimm! http://tapas.affenbande.org