For autostarting on Suse:

http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=linux+start+dsmcad&uid=swg21240599&loc=en_US&cs=utf-8&lang=en


And RedHat:

http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=linux+start+dsmcad&uid=swg21159406&loc=en_US&cs=utf-8&lang=en

Bill Boyer
"Backup my harddrive? How do I put it in reverse?" - ??



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of James 
Marcinek
Sent: Friday, September 08, 2006 10:31 AM
To: [email protected]
Subject: Re: dsmcad on linux system

Richard,

The lsof sure did help. I found that the port the client was listening on was:  
1837 instead of 1581? What could cause this, the
other port not coming up? More importantly how does one correct this sort of 
thing. How do I correctly stop and start the dsmcad?
Should I just kill it and restart?

thanks,

James
----- Original Message -----
From: Richard Sims <[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, September 8, 2006 10:20:35 AM GMT-0500
Subject: Re: [ADSM-L] dsmcad on linux system

On Sep 8, 2006, at 10:06 AM, James Marcinek wrote:

> Hello everyone,
>
> I haven't work with the product in a while... I'm deploying TSM 5.3
> and I installed the ba client on a linux system. I had the web browser
> client up but not authenticating. I killed the dsmcad with a kill
> command. I started  it again and now the web browser page does not
> come up? Can someone tell me what the right way to stop/ start the
> client acceptor daemon and how to get this working again.
> I see the dsmcad process running...

James - Check your MANAGEDServices option settings, per the client manual.

Runtime problems should be apparent in the dsmwebcl.log, and thus correctable.

You can always use the lsof command to verify that the process is listening on 
the expected port number, and an http program (or
even
telnet) to verify port access.

    Richard Sims

Reply via email to