Re: lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

2008-01-21 Thread Trond Myklebust
On Mon, 2008-01-21 at 00:03 +0100, Hans-Peter Jansen wrote: > Hi, > > after installation of 2.6.24-rc8 on a local server, the syslog gets spammed > with "lockd: cannot monitor " > > grep 'lockd: cannot monitor' /var/log/messages | wc -l > 136026 > > in 20 minutes! I restarted the offending

Re: lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

2008-01-21 Thread Hans-Peter Jansen
Am Montag, 21. Januar 2008 schrieb Hans-Peter Jansen: > Hi, > > after installation of 2.6.24-rc8 on a local server, the syslog gets > spammed with "lockd: cannot monitor " > > grep 'lockd: cannot monitor' /var/log/messages | wc -l > 136026 > > in 20 minutes! I restarted the offending client (with

Re: lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

2008-01-21 Thread Hans-Peter Jansen
Am Montag, 21. Januar 2008 schrieb Hans-Peter Jansen: Hi, after installation of 2.6.24-rc8 on a local server, the syslog gets spammed with lockd: cannot monitor some client grep 'lockd: cannot monitor' /var/log/messages | wc -l 136026 in 20 minutes! I restarted the offending client (with

Re: lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

2008-01-21 Thread Trond Myklebust
On Mon, 2008-01-21 at 00:03 +0100, Hans-Peter Jansen wrote: Hi, after installation of 2.6.24-rc8 on a local server, the syslog gets spammed with lockd: cannot monitor some client grep 'lockd: cannot monitor' /var/log/messages | wc -l 136026 in 20 minutes! I restarted the offending

lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

2008-01-20 Thread Hans-Peter Jansen
Hi, after installation of 2.6.24-rc8 on a local server, the syslog gets spammed with "lockd: cannot monitor " grep 'lockd: cannot monitor' /var/log/messages | wc -l 136026 in 20 minutes! I restarted the offending client (with 2.6.18.something) for mercy reasons now.. Pete -- To unsubscribe

lockd spams syslog after upgrade from 2.6.18 to 2.6.24-rc8

2008-01-20 Thread Hans-Peter Jansen
Hi, after installation of 2.6.24-rc8 on a local server, the syslog gets spammed with lockd: cannot monitor some client grep 'lockd: cannot monitor' /var/log/messages | wc -l 136026 in 20 minutes! I restarted the offending client (with 2.6.18.something) for mercy reasons now.. Pete -- To