ADSM-L

[no subject]

2015-10-04 17:31:35
on redhat i'd suggest having an initscript in /etc/rc.d/init.d/adsm.linux
i've attached the one i use (no guarantees, read the script before
using).  it probably has something to do with a PATH not being set
or one of the DSM envirornment variables.

you can have it added to the aproproiate runlevels using
/sbin/chkconfig --add adsm.linux

and then start it up by rebooting or simply

/etc/rc.d/init.d/adsm.linux start

John

On Tue, Apr 11, 2000 at 11:49:39AM +0200, Martin Trcka wrote:
> Hello,
>
> I've got problem  on of my RH linux boxes. I have installed linux client
> v317 on RH6.0 (kernel 2.2.5), made proper changes in inittab, dsm.sys.
>
> The problem is, that even manual backup works perfectly, when it comes to
> scheduled backups - simply nothing happens, even if the process is still
> running. On the other linux box (RH6.1, kernel 2.2.12) everything looks the
> same and works perfectly, scheduled backups, manual backups, etc..
>
> Here are some facts about the bad machine:
>
> $tail /etc/inittab
> adsm:35:respawn:/usr/adsm/dsmc sched 1>/dev/null 2>&1
>
> $cat /usr/adsm/dsm.sys
> servername server_a
> commethod tcpip
> tcpport 1500
> tcpserveraddress ...
> nodename ...
> errorlogname ...
> schedlogname  ...
> passwordaccess generate
>
> I am sure these directives are ok, as manual backup works correctly.
>
> i noticed that after some time, in the listing of running processes, the
> initial /usr/adsm/dscm sched changes to [dsmc]. What does it mean ? (on the
> other linux box, which works correctly) it always looks like this 
> :/usr/adsm/...
>
> So, what could be wrong ?
>
> Thanx in advance.
> ] --
> "...Naucte se milovat sve problemy"
>
> Martin Trcka, sysadmin at SMP, a.s.
> mailto: mtrcka AT smpas DOT cz

<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=