Perfect. That will do it. Thanks.
Scott Bursik
Enterprise Systems Management
PepsiCo Business Solutions Group
scott.bursik@pbsg.com
(972) 963-1400
-----Original Message-----
From: JamesHorwath@glic.com [mailto:JamesHorwath@glic.com]
Sent: Wednesday, July 23, 2003 2:45 PM
To: Bursik, Scott {PBSG}
Cc: nv-l@lists.tivoli.com
Subject: RE: [nv-l] netviewd daemon behavior
Scott,
If the map is open for R/W there is a lock file in the
/usr/OV/databases/openview/mapdb/MAP_NAME/map.lock, where MAP_NAME is the
name of your map. You could test for the existence of this file.
Regards,
Jim
Jim Horwath
Guardian
IT Unix Services
610-807-8795
To: nv-l@lists.tivoli.com
cc:
bcc:
Subject: RE: [nv-l] netviewd daemon behavior
Thanks for the answer Don. In my scripts I used to check for daemon issues
by performing a /usr/OV/bin/ovstatus | grep NOT and if I got a return I
would page. Now that the netviewd daemon is there and either running or not
running as normal behavior, does anyone have any suggestions as how to
perform daemon status check in scripts and ignore the netviewd daemon?
Thanks,
Scott Bursik
Enterprise Systems Management
PepsiCo Business Solutions Group
scott.bursik@pbsg.com
(972) 963-1400
-----Original Message-----
From: Davis, Donald [mailto:donald.davis@firstcitizens.com]
Sent: Wednesday, July 23, 2003 10:31 AM
To: Bursik, Scott {PBSG}; nv-l@lists.tivoli.com
Subject: RE: [nv-l] netviewd daemon behavior
Scott,
Anytime you have the Read/Write map open, the netviewd daemon is stopped.
Starting NetView with the "netview -dconsole" switch stops the netviewd
daemon.
The netviewd daemon's purpose in life is to run the R/W map when no one else
is using it.
Don Davis
First Citizens Bank
Systems Engineer Consultant
Raleigh, NC. 27603-3526
-----Original Message-----
From: Bursik, Scott {PBSG} [mailto:Scott.Bursik@pbsg.com]
Sent: Wednesday, July 23, 2003 10:55 AM
To: nv-l@lists.tivoli.com
Subject: [nv-l] netviewd daemon behavior
NetView 7.1.3 - AIX 4.3.3
I am a little confused about the behavior of the netviewd daemon. I have it
set to automatically start and it does, but I have health scripts that check
for stopped daemons and from time to time netviewd is not running and when
an ovstatus is performed on that daemon, it reports that it exited normally.
Should the netviewd daemon stop on its own and what is the condition where
this might happen?
Thanks,
Scott Bursik
PepsiCo Business Solutions Group
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|