Re: Dsmsched.log and timestamp

  Same problem, same fix!  :)

  [ For people not familiar with this bug, anything run from /etc/inittab
thinks
that it is in the Eastern Standard Time zone, and in order to remedy this,
you have to set the Time Zone (TZ) variable, which is normally set in the
file /etc/TZ.  After checking the HP support site, I could not find a reference

to change this particular "feature" in HPUX 10.x.  I do not know if HPUX 11.x
suffers from the same problem.
  The fix involves create a small shell script to set the TZ variable and then
runs the dsmc sched command.
  ie
   adsm:3:respawn:/usr/local/bin/runsched </dev/null >/dev/null 2>&1

  where runsched looks like

  #!/usr/bin/ksh
  . /etc/TZ
  exec /usr/bin/dsmc sched </dev/null >/dev/null 2>&1

  Enjoy! ]

kells

Any coincidence of opinion, real or imagined, between myself and
Mainland Information Systems is exactly that.



Valeriano Bassi wrote:

> Hi forumers,
> we have had the following problem with some  HP ADSM clients.
> After rebooting an HP UX B.10.2 with ADSM client version 3.1.05, entries in
> Dsmsched.log have an erroneous timestamp,
> that is they were 6 hours early than Server time. ADSM server is at 3.1.1.3
> service level.
> We know that this was a timezone problem on HP-UX V8 and 9 that can be
> circumvented
> by starting a script from /etc/inittab that exports the TZ variable and
> then start dsmc sched.
> But, this should be solved on HP UX V10 ...
>
> Anyone did suffer (and solved) this problem?
> Your help will be very appreciated.