Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Netmon\s+\"sleeping\"\s+for\s+1\,5\s+to\s+2\s+hrs\s+after\s+startup\s*$/: 3 ]

Total 3 documents matching your query.

1. Netmon "sleeping" for 1,5 to 2 hrs after startup (score: 1)
Author: "Engelsen, Bjørn
Date: Wed, 29 Sep 1999 11:20:25 +0200
Lately our netmon has stopped without any obvious reason. After restarting it (or restarting all daemons) , it seems to do no polling for almost two hours. Unmanage/manage of an object turns it into
/lists/html/nv-l/1999-09/msg00531.html (9,663 bytes)

2. Re: Netmon "sleeping" for 1,5 to 2 hrs after startup (score: 1)
Author: James Shanks <James_Shanks AT TIVOLI DOT COM>
Date: Wed, 29 Sep 1999 07:39:47 -0400
I would look at your name resolution and make sure that is working well. Then I would read the man page on netmon and start a netmon trace for all the options and see what you get. James Shanks Tivol
/lists/html/nv-l/1999-09/msg00535.html (10,380 bytes)

3. Re: Netmon "sleeping" for 1,5 to 2 hrs after startup (score: 1)
Author: Leslie Clark <lclark AT US.IBM DOT COM>
Date: Wed, 29 Sep 1999 07:40:28 -0400
I see this most clearly on systems where the seedfile is excluding things by oid or by name wildcard. These systems usually have a lot of stub objects in the database (the ones that go away when you
/lists/html/nv-l/1999-09/msg00536.html (12,072 bytes)


This search system is powered by Namazu