Under both Redhat Linux 7.2/x86 and Gentoo Linux 1.4rc4/x86, the dsmc
scheduler (run out of inittab) always spawns 3 processes with the TSM
5.1.5.15 client for Linux... I always saw only one process spawned with
the ADSM 3.1 client when we used ADSM 3.1.

Is this normal to have three running at the same time?

I'm not finding it to be a problem, but just really curious. If it's a bug
of some kind, then I'll open a ticket on it... if it's post-ADSM v3
behavior then I'll update the local documentation saying to expect that.

I know that the TSM clients are more efficient compared to ADSM 3.1 such as
creating multiple connections - one to handle commands/info and one to
handle actual data transfer... but I don't know what the story is with the
TSM client scheduler, although I suspect it might be a similar thing for
performance reasons?

A ``ps -ef|grep dsmc'' command's output shows:

root     24594     1  0 Apr18 ?        00:01:28 /usr/bin/dsmc sched -password
root      3919 24594  0 Apr18 ?        00:00:00 /usr/bin/dsmc sched -password
root      8136  3919  0 Apr18 ?        00:00:00 /usr/bin/dsmc sched -password

What are the other two processes for? (The first, pid 24594, ppid 1 --
init -- is clearly the parent process and the other two are child processes.)

strace -f -p <pid> tells me pid 8136 is doing absolutely nothing. pid 3919
is doing poll(), and pid 24594 is doing time()/getpid()/write()/nanosleep()
-- looks like some sort of delay loop and doing administrative tasks while
3919 might be a different process for purpose of watching the connection to
the TSM server?

-Dan