Re: multiple dsmcad procs running

2006-04-06 Thread Richard Sims
On Apr 6, 2006, at 9:25 AM, Vlijmen, M. van wrote: Goodday, We have IBM Tivoli Storage Manager 5.3.2.0 running on a ppc64 redhat machine One of the clients is a hp 9000 with hpux 11.i V1. By accident I started three instances of adsmcad. I killed two of them and happily went home at the end of

Re: multiple dsmcad procs running

2006-04-06 Thread Jurjen Oskam
On Thu, Apr 06, 2006 at 03:25:58PM +0200, Vlijmen, M. van wrote: > Am I right in assuming that correct authentication only takes place between > the server and the dsmcad process that initiated the first > contact with the server? So, in this case the TSM server didn't recognize > the dsmcad proce

Re: Multiple DSMCAD processes on RH Linux

2004-02-27 Thread Paul Ripke
This is correct - early Linux kernels created threads via clone(), which look from the outside like multiple processes. It's not ps that can't tell the difference, since they really are separate processes, that just happen to share most resources. AFAIK, it was just a fairly easy but very ugly way

Re: Multiple DSMCAD processes on RH Linux

2004-02-27 Thread Rainer Schöpf
On Fri, 27 Feb 2004, Thomas Rupp, Vorarlberger Illwerke AG wrote: > I'm running Red Hat Linux Advanced Server release 2.1AS/i686 (Pensacola) > with the TSM 5.2.0.0 client. > When I start dsmcad by simply entering the command I get 5 dsmcad > processes. > > root 8431 1 0 09:51 ?

Re: Multiple DSMCAD processes on RH Linux

2004-02-27 Thread Tuncel Mutlu (B.T.B.S.G.)
We have the same case, only 3 instances, still in test. TSM Client - 5.2.0.0 HW: IBM Xseries 345 Model No: 8670 - 31x OS: Linux Suse 7.3 root 12477 538 0 14:42 pts/000:00:00 ./dsmc sched root 12479 12477 0 14:42 pts/000:00:00 ./dsmc sched root 12480 12479 0 14:42 pts/0

Re: Multiple DSMCAD

2002-01-25 Thread Lancaster, Dominic
It's no different really to running multiple dsmcad's on any other platform - to this end the Appendix in the 'Windows Client' install covers it fairly well in terms of variables etc BUT ... the big thing I have found is (on NT) to ensure you have a different IP address and WebPort number for each