Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Problem\s+with\s+netmon\s+in\s+6\.0\.1\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Problem\s+with\s+netmon\s+in\s+6\.0\.1\s*$/: 3 ]

Total 3 documents matching your query.

1. Problem with netmon in 6.0.1 (score: 1): Author: KOCH François Athesa <KOCH AT ulysse.cea DOT fr>; Date: Wed, 25 Oct 2000 09:08:07 +0200; Hi, Since I upgraded netview from 6.0 to 6.0.1, the netmon daemon permanently crashes (after less than 1 minute). There are no errors in the trace file, and ovstatus just tells 'exited on signal 11'.; /usr/local/webapp/mharc-adsm.org/html/nv-l/2000-10/msg00281.html (10,765 bytes)
2. Re: Problem with netmon in 6.0.1 (score: 1): Author: James_Shanks AT tivoli DOT com; Date: Wed, 25 Oct 2000 09:11:22 -0400; A signal 11 is indicates a segmentation violation. Usually a core file is produced. There is probably nothing you can do about this except to call Support and get some help from them with it. Typical; /usr/local/webapp/mharc-adsm.org/html/nv-l/2000-10/msg00285.html (11,919 bytes)
3. RE: Problem with netmon in 6.0.1 (score: 1): Author: "Desai Daxesh (tel1dxd)" <tel1dxd AT ups DOT com>; Date: Wed, 25 Oct 2000 10:43:18 -0400; Are you running Netview on AIX4.3.3? If you are then you need to apply bos.obj.tcp.clinet/server.4.3.3.25. This might resolve your problem. We had same problem but it was with ovw_binary exit signal; /usr/local/webapp/mharc-adsm.org/html/nv-l/2000-10/msg00289.html (12,494 bytes)

Current List: 1 - 3
Page: [1]