RocketJSquirrel
Senior Member
My log shows this sequence every hour, on the .260 firmware:
It's not a problem, but it makes me suspicious. In general, when a process is being restarted regularly, I suspect a memory leak which the developers couldn't fix. Restarting is the brute force method of avoiding the leak.
Just curious. Anybody have any insight on this?
Nov 11 08:59:57 notify_rc : restart_radvd
Nov 11 08:59:57 notify_rc : restart_diskmon
Nov 11 08:59:57 rc_service: restart_diskmon is waitting restart_radvd...
Nov 11 08:59:57 radvd[3991]: Exiting, sigterm or sigint received.
Nov 11 08:59:57 radvd[3991]: sending stop adverts
Nov 11 08:59:57 radvd[3991]: removing /var/run/radvd.pid
Nov 11 08:59:57 radvd[4005]: version 1.9.1 started
Nov 11 08:59:58 disk monitor: be idle
It's not a problem, but it makes me suspicious. In general, when a process is being restarted regularly, I suspect a memory leak which the developers couldn't fix. Restarting is the brute force method of avoiding the leak.
Just curious. Anybody have any insight on this?