Subject: | |
From: | |
Reply To: | |
Date: | Mon, 25 Feb 2013 12:06:35 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Mon, 25 Feb 2013 18:54:29 +0100, David Sommerseth
<[log in to unmask]> wrote:
>What about cron/at jobs? Or some other tasks running which would run some
>grep calls?
>
>In the meantime, I double checked ...
>
> $ cat /proc/sys/net/ipv6/neigh/default/retrans_time
> $ awk '{print $0}' < /proc/sys/net/ipv6/neigh/default/retrans_time
> $ dmesg | tail -n2
> process `cat' is using deprecated sysctl (syscall)
net.ipv6.neigh.default.retrans_time; Use
net.ipv6.neigh.default.retrans_time_ms instead.
> process `awk' is using deprecated sysctl (syscall)
net.ipv6.neigh.default.retrans_time; Use
net.ipv6.neigh.default.retrans_time_ms instead.
>
>So, as you see ... now the kernel complains about 'cat' and 'awk' accessing
>the deprecated syscall. I feel very confident you had something which
>did run grep again that file inside /proc/sys/net/ipv6.... So you need to
>check against /var/log/messages to see if you can find out what else
>happened at the time when this log line was logged.
Thanks for taking the trouble. No cron or at jobs and the only entry in the
logs at a nearby time was the "new usb device" one, so I guess it was
probably connected with that.
Stephen Isard
|
|
|