Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
This note cross posted in TeMIP conference... <<< TAEC::DISK$HOGGAR_SYS:[NOTES$LIBRARY]TEMIP.NOTE;1 >>> -< Telecom. Management Information Platform conference >- ================================================================================ Note 314.0 Start IP Poller at boot time No replies DV780::SMITHG 29 lines 13-APR-1995 23:54 -------------------------------------------------------------------------------- I'm having some difficulty starting the IP poller automatically at boot time. Previous notes in the MCC conference address this but for VMS machines and MCC - we're using TeMIP V2.0A and OSF 3.0. The method that I've used is to build an IP poller startup script into /sbin/init.d that should be executed at boot time. The proper entry (a link from /sbin/rc3.d) is in place as well. It appears that the poller attempts to start, but then disappears. The startup file being used is: #!/bin/csh # /usr/mcc/mcc_system/mcc_ip_poller_enable.csh << ! <CR> 300 5 5 .nic.SNMP_alarms <CR> # end The mcc_ip_poller_enable.csh script has not been changed. Any help on this would be appreciated. Thanks, Gary
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
6274.1 | Fixed it | DV780::SMITHG | Wed Apr 19 1995 20:12 | 21 | |
<<< TAEC::DISK$HOGGAR_SYS:[NOTES$LIBRARY]TEMIP.NOTE;1 >>> -< Telecom. Management Information Platform conference >- ================================================================================ Note 314.1 Start IP Poller at boot time 1 of 1 DV780::SMITHG 13 lines 19-APR-1995 19:09 -< Fixed it >- -------------------------------------------------------------------------------- We were able to fix the script so that the IP poller starts at boot time. There were two issues: 1) the mcc_login.csh and temip_login.csh were not being properly sourced and, 2) we needed to execute the startup script from /sbin/init.d using the /usr/bin/nohup command as in: /usr/bin/nohup /usr/mcc/mcc_system/ip_poller_enable.csh There was evidently some signal that was being received that was causing the ip poller process to quit right after being started??? |