Re: initab, process not starting.

Well amazingly that is what fixed it. Thanks Ole for providing me that
information.
This is some strange thing with TSM running in inittab.

I think it may not be the log file definitions themselves but just updating
the dsm.sys itself that triggers the process to work in inittab.
I removed the log files afterwards and it continued to work after I killed
the dsmc process.... as i said it is something strange going on.
Maybe it has something to do with the way inittab loads the environments.

Thanks again

S


_____

From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of
Bergström Ole
Sent: 08 February 2007 07:17
To: aix-l@xxxxxxxxxxxxx
Subject: Re: initab, process not starting.


Hi,

I had a similar problem once and it was due to the misisng error- and
sched-log definitions.
When started from inittab the system tried to write the logfiles under / and
was not able to do that.
After adding:

schedlogname /usr/tivoli/tsm/client/ba/bin/dsmsched2.log
errorlogname /usr/tivoli/tsm/client/ba/bin/dsmerror2.log

into dsm.sys it works.

Regards,
Ole.


_____

From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of
Murphy, Sean
Sent: 7. helmikuuta 2007 19:37
To: aix-l@xxxxxxxxxxxxx
Subject: initab, process not starting.




Starting the dsmc process (via inittab) does not work.

# lsitab adsm

adsm:2:respawn:/usr/bin/dsmc sched -quiet > /dev/null 2>&1 # ADSM scheduler

# init -q

# ps -ef | grep dsm

#

I tried changing the run levels to "0123456"

I tried removing it and re-adding it but it will not start via inittab.

This process works fine running from the command line.

Does anyone have any ideas why this process will not start?





Also, this may be related, but i am not sure,

when doing an who -r on <server>, it returns with nothing, i.e a blank line.



Thanks in advance to anyone that has any ideas.



Sean