Conference decwet::networker

    After reflection, let me add to question 3 in .0 that we have been
    doing our DU installations by unpacking the kit to a disk on the
    NetWorker server, then mounting this disk and running nsr_ize -i right
    from it.  That is why we haven't been running setld on the clients to
    install the client kit.  Hmm.  Maybe we should be . . . .
    
    tl

re: .0

  1.  I'll defer this to Richard/Wes

  2.  V4.2C will not run on a DU 3.x machine, your only option would be
      to run V4.2B+patch 12 on those clients

  3.  My (limited) understanding of this, is that most people normally, setld
      the client kit on a server (creating just the tar file) then they remote
      access the tar file (via ftp or nfs) un-tar locally and run nsr_ize to
      do the setup.

      as for not utilizing setld -- we're only part way there, it's on our 
      (rather full) plate, to have the client setld kit do the unbundling and 
      nsr_ize for the customer. This will make installation simpler, and be more
      DUNIX-like.

re: .1
   
      right now setld only buys you tracking on the client, you'd still have
      to unbundle and nsr_ize locally. Remote accessing the unbundled tar file
      should probably work, however, I need to defer to Richard/Wes, whether or
      not nsr_ize tries to create links instead of copying the actual binaries
      on a client install (I know it does links for the server)
      
      

1. The server patch contains everything that is in the client patch.  What's
different about them is the client patch does not contain server specific
binaries.  So you only need to install the server patch on servers, and
the client patch on clients.

-- Rich Randall

On the server, install the server software then install the 
server patch.  The server install includes all of the client 
bits.

Wes

    Perfect.  Clear as a bell now.  Thanks for taking the time to describe
    this!
    
    tl
    

    By the by, the nsrv42b-012 patch kit contains files that do not have
    the SETUID protection bit:
    
    # ls -l nw_patches/nsrv42b-012/decaxp/decaxp/
    total 8392
    -rwx--x--x   1 root     system   1171456 Mar 21 13:20 nsrarchive
    -r-xr-xr-x   1 root     system    712704 Mar 21 13:25 nsrinfo
    -r-xr-xr-x   1 root     system   1302528 Mar 21 13:20 nwbackup
    -rwx--x--x   1 root     system   1581056 Mar 21 13:20 nwrecover
    -rwx--x--x   1 root     system   1261568 Mar 21 13:21 recover
    -rwx--x--x   1 root     system   1089536 Mar 21 13:21 save
    -rwx--x--x   1 root     system    811008 Mar 21 13:21 savefs
    -r-xr-xr-x   1 root     system    663552 Mar 21 13:30 uasm
    #
    
    This caused some backups that are not run from root to fail at my site.
    
    Fyi,
    tl

    Thanks.  Please also note that, when the patch files are copied, that:
    
    	cp -p . . .
    
    MUST be used, or the file protections, etc. will not be preserved.
    
    Thanks
    tl

    Hold the phone:  the file protections restore just fine, if 'tar xvpf'
    is used.  But, the ownership isn't right:
    
    # ls -lR decaxp/
    total 16
    drwxr-xr-x   2 root     bin         8192 May 19 14:32 decaxp
    drwxr-xr-x   2 root     bin         8192 May 19 14:32 decpt
    
    decaxp/decaxp:
    total 8392
    -rws--x--x   1 root     system   1171456 Mar 21 13:20 nsrarchive
    -r-xr-xr-x   1 root     system    712704 Mar 21 13:25 nsrinfo
    -r-xr-xr-x   1 root     system   1302528 Mar 21 13:20 nwbackup
    -rws--x--x   1 root     system   1581056 Mar 21 13:20 nwrecover
    -rws--x--x   1 root     system   1261568 Mar 21 13:21 recover
    -rws--x--x   1 root     system   1089536 Mar 21 13:21 save
    -rws--x--x   1 root     system    811008 Mar 21 13:21 savefs
    -r-xr-xr-x   1 root     system    663552 Mar 21 13:30 uasm
    
    decaxp/decpt:
    total 7552
    -rws--x--x   1 root     system   1032192 Mar 21 13:22 nsrarchive
    -r-xr-xr-x   1 root     system    712704 Mar 21 13:25 nsrinfo
    -r-xr-xr-x   1 root     system   1155072 Mar 21 13:22 nwbackup
    -rws--x--x   1 root     system   1441792 Mar 21 13:22 nwrecover
    -rws--x--x   1 root     system   1114112 Mar 21 13:22 recover
    -rws--x--x   1 root     system    942080 Mar 21 13:23 save
    -rws--x--x   1 root     system    696320 Mar 21 13:23 savefs
    -r-xr-xr-x   1 root     system    638976 Mar 21 13:23 uasm
    #
    
    Sorry for the false alarm.
    
    tl

    Okay.  More input: the instructions in the README included with
    nsrv42b-012 are incorrect in two regards:
    
    Instead of:
    
    # tar xvf clientkit.tar
    
    do
    
    # tar xvpf clientkit.tar
    
    and instead of:
    
    # cp * /usr/bin
    
    do
    
    # cp -p * /usr/bin
    
    tl