Re: dropwatch for network drop monitor

[Oliver Hartkopp <oliver@hartkopp.net>]

Neil Horman wrote:

> 
> Quick update for you, I've reproduced the problem.  The inability to restart
> after the first few errors is actually by design.  Since you had to kill the
> user space process, it left the kernel bits in a state where they were still
> monitoring, so a second start command (when you restarted the user space daemon)
> caused an error, and the program shutdown (which I probably shouldn't do,
> returning instead to the command console).  You can work around this by issuing
> a stop command, which successfully stops the kernel bits and lets you restart
> them.

Hard terminations are mostly critical to handle. I'll try the workaround.

> 
> This also tells me that the kernel netlink warning is not fatal (as our netlink
> message commands are getting processed properly).  I still need to figure out
> why thats happening though.
> 

Ok.

> As for the ctrl-c issue, I've got no idea whats going on there, its like the
> recv operation is restarting after we catch the SIGINT.  I think I may just
> switch that to a poll operation on the netlink socket and stdin input.  That
> should fix that up quick.  Expect a git commit on that sometime this weekend,
> and some subseqent netdev posts to fix the kernel bits. 

You can also send me an off-list mail when you have something to test this
weekend.

I can produce a lot of drops on my machine ;-)

Regards,
Oliver