Skip to contentSkip to conversation

kernel: sock: sock_set_timeout: `trinity-main' (pid 1349) tries to set negative timeout

DISCUSSION Toralf Förster 2 participants 2 messages Nov 2, 2013

lore
Share & tools
lore

Toralf Förster

author
#0 lore raw

I'm observing such syslog messages in a user mode linux image and do wonder why trinity-main does such unusal things (and not the child which I'd expect of course) :

Nov  2 19:14:25 trinity kernel: sock: sock_set_timeout: `trinity-main' (pid 1349) tries to set negative timeout
Nov  2 19:14:25 trinity kernel: sock: sock_set_timeout: `trinity-main' (pid 1349) tries to set negative timeout
Signature · 3 lines
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
#1 lore raw
Quoted 6 lines · Toralf Förster

I'm observing such syslog messages in a user mode linux image and do wonder why trinity-main does such unusal things (and not the child which I'd expect of course) :

Nov  2 19:14:25 trinity kernel: sock: sock_set_timeout: `trinity-main' (pid 1349) tries to set negative timeout
Nov  2 19:14:25 trinity kernel: sock: sock_set_timeout: `trinity-main' (pid 1349) tries to set negative timeout

The main process periodically does setsockopt calls on all the open sockets that children inherit.

Dave