<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">Date:   April 9, 1997

Patch:  3.0-ULK-0004

Component: Tivoli/UserLink

Problems Fixed:
	 PR 15660/IX62886  
               NO CLEAN BREAK ON NETWORK DISCONNECT FROM USERLINK     
         PR 15661/IX62891  
               USERLINK HANGS WHEN LOADED                             
         PR 20775
               usrlnkd core dumps on sunos and solaris                
         PR 20776   
               odadmin reexec fails to start usrnlnkd                 
         PR 20778  
               User Link can't pull filepacks with version numbers    
         PR 21016  
               odadmin reexec runs multiple daemons on NT             
         PR 21349/IX65885 
               USERLINK DAEMON FROM 3.1 CD CAUSING LOCKUP             
  
Architecture(s): SunOS, Solaris, HP-UX 9.x, AIX 4.1, HP-UX 10.0,
	NT 3.5.1, NT 4.0

Patches superseded by this patch:

	3.0-ULK-0003 

Patches this patch is dependent on:

	None

Database Changes:

	None 

Release Notes for this patch:

        Userlink has the following issues still outstanding:

        1. The usrlnkd can still lock up on AIX 3.x with frequent DHCP 
           requests.  For example, with 5 machines DHCP'ing every minute, 
           Userlink may lock up within a few hours.  When the daemon locks up, 
           it stop processing DHCP requests, and does not accept any new 
           connections. 

        2. Rebooting the machine on startup causes the child usrlnkd to hang. 
           If you reboot (warm) the client as the agent is initially trying
           to DHCP, the child usrlnkd process that was spawned will hang and 
           not go away.  The main usrlnkd still functions normally, but you 
           see this extra usrlnkd process hanging around.

        3. With Courier 3.1, if you attempt to pull Autopacks you can hang the 
           client side.  This is a problem with the Userlink client and will 
           be fixed in a separate client patch.  This problem can also 
           manifest itself with regular filepacks that have long running 
           After scripts.

        4. When installing the Userlink client, you must give the machine 
           name as the same name as the PCManagedNode object that corresponds 
           to that machine.


Files Replaced or Added by this Patch (for all supported values of $INTERP):

        bin/$INTERP/TAS/USERLINK/usrlnkd
	bin/$INTERP/TAS/USERLINK/get_version
	bin/$INTERP/TAS/USERLINK/get_version.pl
	bin/$INTERP/TAS/USERLINK/get_version.sh
        bin/$INTERP/TAS/USERLINK/bootm.in
        bin/$INTERP/TAS/USERLINK/killul.pl
        bin/$INTERP/TAS/USERLINK/pulldist.pl
        bin/$INTERP/TAS/USERLINK/pulldist.sh
        bin/$INTERP/TAS/USERLINK/set_ip.pl
        bin/$INTERP/TAS/USERLINK/set_ip.sh
        bin/$INTERP/TAS/USERLINK/userlink.cfg
        bin/$INTERP/TAS/USERLINK/userlink_ali.sh
        bin/$INTERP/TAS/USERLINK/userlink_client.sh
        bin/$INTERP/TAS/USERLINK/userlink_ir.tar
        bin/$INTERP/TAS/USERLINK/userlink_ist.tar
        bin/$INTERP/TAS/USERLINK/wkillul.sh
   
Patch Contents:

	- This README file
	- A cdrom image for this patch 

Applying the Patch:
    1)	Place the patch tape in the tape drive and extract the contents into
	a scratch directory. For the purpose of this release note, assume that
	the symbol $PATCH points to this directory. (Note: The tape drive may
	not be called /dev/rmt0 on your system.)

	# cd $PATCH
	# tar xvf /dev/rmt0
	# tar xvf 3.0-ULK-0004.tar

    2)  You must stop the usrlnkd process before installing this patch.
        This process is installed with Tivoli/UserLink and starts after
	installation or every time the oserv starts.  To stop the userlnkd
	process, complete the following steps.

	a)  Log in to the machine as the superuser.

	b)  Stop the usrlnkd process by using the ps(1), grep(1), and kill(1)
	    commands.  For example, on an HP-UX machine, enter:

	    root&gt; ps -ef | grep usrlnkd

	    root 24861 1069 0 13:21:57 ttys1 0:02 usrlnkd
	    root 25150 1069 6 16:41:39 ttys1 0:00 grep usrlnkd

	    root&gt; kill -9 24861
	  
    3)	Use the following steps to install the patch from the Tivoli desktop.
	NOTE: You must have the install_product and super authorization roles
	to successfully install this patch.

        a)  Select the "Install -&gt; Install Patch..." option from the
           "Desktop" menu to display the "Install Patch" dialog.

        b)  Press the "Select Media..." button to display the "File Browser"
	    dialog.

        c)  Enter the path to the directory containing the patch, $PATCH, in
	    the "Path Name:" field.

        d)  Press the "Set Media &amp; Close" button to return to the "Install
            Patch" dialog.

        e)  The patch install list now contains the name of the patch,
            3.0-ULK-0004.  Select the patch by clicking on it.

        f)  Select the clients to install this patch on. This patch changes
            binaries and needs to be installed on the TME server and
	    on each client.

        g)  Press the "Install" button to install the patch.
</pre></body></html>