vxconfigd just calls the standard calls to log syslog data. Is the timezone set correctly or differently when vxconfigd starts versus when syslogd starts? I would have thought that syslogd itself timestamped the messages, but that would make this output next to impossible. -- Ronald S. Karr tron |-<=>-| [EMAIL PROTECTED]
On September 5, 2006, Gravizi, Thomas wrote: >Greetings all, > > > >We recently upgraded to Volume Manager 4.1, and it seems that >vxcm:vxconfigd messages are out of time line. See below. Is there any >reason why these particular messages would be 4 hours different than the >rest of the /var/adm/messages ? > > > >Sep 3 12:38:28 venice genunix: [ID 110798 kern.warning] WARNING: Page83 >data not standards compliant HIT > >ACHI OPEN-3 -SUN 2109 > >Sep 3 12:38:28 venice last message repeated 2 times > >Sep 3 16:38:32 venice vxvm:vxconfigd: [ID 952067 daemon.warning] >V-5-1-554 Disk HDS9970V0_4 names group > >oaracdg, but group ID differs > >Sep 3 16:38:33 venice vxvm:vxconfigd: [ID 968451 daemon.warning] >V-5-1-554 Disk HDS9970V0_5 names group > >oaracdg, but group ID differs > >Sep 3 12:38:35 venice vxesd[223]: [ID 360244 daemon.notice] Event >Source daemon started > >Sep 3 12:38:35 venice syseventd[134]: [ID 617319 daemon.error] SIGHUP >caught - reloading modules > >Sep 3 12:38:36 venice syseventd[134]: [ID 661968 daemon.error] Daemon >restarted > > > >Thanks, > > > >Thomas Gravizi > >UNIX Systems Administrator > >Enterprise Operations > >STERIS Corporation - Mentor, OH > >[EMAIL PROTECTED] > >440.392.7630 - phone > >440.350.7078 - fax > > > > > > > >_______________________________________________ >Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu >http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx