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
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
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
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
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
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
6 matches
Mail list logo