Software Distributor Administration Guide (March 2009)

Table Of Contents
1. On the target system, type:
ps -e | grep swagentd
2. If the daemon does not appear to be running, you can start it by typing (as root
on the target system):
/usr/sbin/swagentd
3. If you attempt to start a daemon when one is already running, you will see a
message about the other daemon; this is harmless.
You can also kill and restart a currently running daemon by typing:
/usr/sbin/swagentd -r
Other possible causes for this problem are listed in the section “Connection Timeouts
and Other WAN Problems ” (page 338).
TIP: An easy way to determine if a target system has the SD-UX daemon installed
and running is to type:
/usr/sbin/swlist -l depot @ <one or more target hostnames>
which will attempt to contact each target to get a list of registered depots. Those targets
which have the SD-UX daemon installed will report either:
# Initializing...
# Target <hostname> has the following depot(s):
# <...insert list of depots...>
or
# Initializing...
WARNING: No depot was found for <hostname>.
For more information on daemon activity, see the daemon logfile in /var/adm/sw/
swagentd.log.
B.2.2 GUI Won’t Start or Missing Support Files
You can start the GUI in these ways:
For swinstall, swcopy, or swremove, type the command with no additional
options or arguments.
Include the -i option with any other options and arguments when you type the
command on the command line. (Required for swlist.)
For the Job Browser, type sd on the command line.
When using the GUI, you might encounter these problems:
Can’t open the display or display is set incorrectly
Missing GUI support files
334 Troubleshooting