Bug#484526: nfdump: 0 (zero) is a valid shm id

2008-12-19 Thread Jorik Jonker
Hi all, It appears to me that 0 indeed is a valid shm key, but it is only returned when the daemon tries to reconnect to an existing segment, for instance if the daemon did not close properly. The daemon started perfectly every "first time" I ran it, but every subsequent launch it failed. ipcs lea

Bug#484526: nfdump

2008-12-19 Thread Remco Post
actually, this patch is invalid. The fact that nfcapd cant start is because of an unclean shutdown, leaving the ols shared memory segment floating around while it shouldn't. At first glance it appears as if you're right, but look at lines 221 and further. Either the page already exists, whi

Bug#484526: nfdump: 0 (zero) is a valid shm id

2008-09-01 Thread Andreas Putzo
Hi, On Jun 04 18:55, Christoph Biedl wrote: > Package: nfdump > Version: 1.5.7-2 > Severity: normal > > I noticed nfcapd did not restart after a config change. After a long > search the reason was found at bookkeeper.c:160: > > 158 shm_id = shmget(shm_key, sizeof(bookkeeper_t), 0600

Bug#484526: nfdump: 0 (zero) is a valid shm id

2008-06-04 Thread Christoph Biedl
Package: nfdump Version: 1.5.7-2 Severity: normal Hi, I noticed nfcapd did not restart after a config change. After a long search the reason was found at bookkeeper.c:160: 158 shm_id = shmget(shm_key, sizeof(bookkeeper_t), 0600); 159 160 if ( shm_id > 0 ) { 161