swagent man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

swagentd(1M)							  swagentd(1M)

NAME
       swagentd,  swagent - daemon that invokes swagent; serve local or remote
       SD software management tasks

SYNOPSIS
       executed by only.

       option=value] option_file]

   Remarks
	 ·  This command supports operation on remote systems.	See below.

	 ·  For an overview of all SD commands, see the sd(5) man page by typ‐
	    ing on the command line.

DESCRIPTION
       The roles of UNIX target and source systems require two processes known
       as the and For most purposes, the distinction between  these  two  pro‐
       cesses  is  invisible  to  the  user and they can be viewed as a single
       process.

       Each SD command interacts with the daemon  and  agent  to  perform  its
       requested tasks.

       The  daemon process must be scheduled before a UNIX system is available
       as a target or source system.  This can be done either manually	or  in
       the  system  start-up script.  The agent process is executed by to per‐
       form specific software management tasks.	 The agent is never invoked by
       the user.

   Remote Operation
       You  can	 enable	 SD  to manage software on remote systems.  To let the
       root user from a central SD controller (also called the central manage‐
       ment  server  or	 manager  node)	 perform operations on a remote target
       (also called the host or agent):

       1)   Set up the root, host, and template Access Control Lists (ACLs) on
	    the remote machines to permit root access from the controller sys‐
	    tem.  To do this, run the following command on each remote system:

	    NOTES:

	      ·	 controller is the name of the central management server.

	      ·	 If remote system is 11.00, make sure SD patch PHCO_22526 or a
		 superseding  patch  is installed on remote system before run‐
		 ning

	      ·	 If remote system is older than 11.00 or for some other reason
		 does  not  have in place, copy script from an 11.11 or higher
		 system to the remote system.

       2)   have enhanced GUI interfaces for remote  operations.   Enable  the
	    enhanced  GUIs  by	creating the file on the controller.  Use this
	    command:

	    See sd(5), swinstall(1M),  swcopy(1M),  swjob(1M),	swlist(1M)  or
	    swremove(1M) for more information on interactive operations.

       NOTE: You can also set up remote access by using directly on the remote
       machines to grant root or non-root access to users from the  controller
       system.

   Disable and Enable
       The  daemon  can be disabled by the system administrator by setting the
       entry in to and executing:

       The daemon can be enabled by the system administrator  by  setting  the
       entry in to and executing:

   Options
       The  command  supports  the  following options to control its behavior.
       (These options do not apply to which you cannot start from the  command
       line.)

	      The	     kill  option  stops the currently running daemon.
			     Stopping the daemon will not stop any agent  pro‐
			     cesses   currently	 performing  management	 tasks
			     (such as installing or  removing  software),  but
			     will  cause any subsequent management requests to
			     this host to be refused.  This option is  equiva‐
			     lent  to  sending a SIGTERM to the daemon that is
			     running.

	      The	     no fork option runs the daemon as	a  synchronous
			     process rather than the default behavior of fork‐
			     ing to run it asynchronously.  This  is  intended
			     for  running the daemon from other utilities that
			     schedule processes, such as

	      The	     restart option stops the currently running daemon
			     and  restarts  a  new daemon.  Because the daemon
			     processes	options	 only  at  startup,  you  must
			     restart  the  daemon  after you have modified any
			     daemon options.  Otherwise, the modified  options
			     have no effect.

	      Set the	     option  to	 value	and override the default value
			     (or a value in an option_file specified with  the
			     option).  Multiple options can be specified.

	      Read the session options and behaviors from
			     options_file.

EXTERNAL INFLUENCES
   Default Options
       In  addition  to	 the standard options, you can change SD behaviors and
       policy options by editing the system-wide default values found  in  the
       file.   (Note  that the user-specific default values in do not apply to
       the agent or daemon.)

       To specify values in the defaults file, you must use the following:

       The optional command_name prefix denotes one of the SD commands.	 Using
       the  prefix  limits the value change to that command.  If you leave the
       prefix off, the change applies to all commands that use the option.

       You can also override default values from the command line with the  or
       options:

       NOTE:  the only way to change default values for the agent is to modify
       the system-wide defaults file.  You cannot change agent	defaults  from
       the command line.

       The  following  section lists all of the keywords supported by the com‐
       mand.  If a default value exists, it is listed after the

   Daemon Options
       These options apply only to the daemon, After changing daemon  options,
       you  must  restart the daemon for these options to take effect (see the
       command-line option above).

	      The location of the agent program invoked by the daemon.

	      This is the default log file for the
			daemon.

	      Controls the time in minutes to cache and re-use the results  of
	      hostname
			or  IP	address resolution lookups.  A value of 0 dis‐
			ables the facility to cache and re-use lookup results.
			The  maximum  value allowed is 10080 minutes, which is
			one week.

			A value of:
			disables the lookup caching mechanism.
			is the maximum value allowed.
	      The maximum number of agents that are permitted to run  simulta‐
	      neously.
			The value of -1 means that there is no limit.
	      Defines in minutes how often the daemon wakes up to scan the job
	      queue
			to determine if any scheduled jobs  must  be  started.
			When set to 0, no scheduled jobs will be initiated.
	      Defines  the  protocol  sequence(s) and endpoint(s) on which the
	      daemon
			listens and which the other commands  use  to  contact
			the  daemon.  If the connection fails for one protocol
			sequence, the next is attempted.  SD supports both the
			tcp and udp protocol sequence on most platforms.
   Agent Options
       These  options  apply  only  to the agent, You cannot set these options
       directly from the command line.	To set agent options,  you  must  edit
       the system-wide defaults file.  See the heading above for instructions.
	      If the	or  controller	has  set the target agent will consult
			and use the configured value  of  its  own  option  to
			determine  the	source that it will use in the install
			or copy.
			The agent's value for is specified using  the  syntax.
			If  the	 host portion is not specified, the local host
			is used.  If the path portion is  not  specified,  the
			path sent by the command is used.  If there is no con‐
			figured value at all for the agent will apply the con‐
			troller-supplied path to its own local host.
	      Defines the command called by the source agent to compress files
			before	transmission.	If the is set to other than or
			this path must be changed.
	      Defines the default
			used by the agent when it compresses files  during  or
			after  transmission.   If  is  set  to	false,	the is
			recorded for each file compressed so that the  correct
			uncompression  can later be applied during a or a with
			set to true.  The specified must  produce  files  with
			the  specified.	  The must be able to process files of
			the specified unless the format	 is  which  is	uncom‐
			pressed	 by  the  internal uncompressor (The only sup‐
			ported compression types are and
	      Defines the script called by the agent to	 perform  release-spe‐
	      cific
			configure cleanup steps.
			Please	Note:	Transition links do not exist on 11.31
			and newer releases so there are no  configure  cleanup
			steps  to  perform therefore the is never executed for
			these releases.
	      Defines the script called by the agent to	 perform  release-spe‐
	      cific install
			cleanup	 steps	immediately after the last postinstall
			script has been run.  For an OS	 update,  this	script
			should at least remove commands that were saved by the
			script.	 This script is executed  after	 all  filesets
			have been installed, just before the reboot to the new
			operating system.
			Please Note:  Transition links do not exist  on	 11.31
			and  newer  releases  so  there are no install cleanup
			steps to perform; therefore, the is never executed for
			these releases.
	      Defines  the  script called by the agent to perform release-spe‐
	      cific install
			preparation.  For an OS update, this script should  at
			least  copy commands needed for the checkinstall, pre‐
			install, and postinstall scripts to a path where  they
			can  be	 accessed  while  the  real commands are being
			updated.  This script is executed  before  any	kernel
			filesets are loaded.
			Please	Note:	Transition links do not exist on 11.31
			and newer releases so there are no install setup steps
			to perform; therefore, the is never executed for these
			releases.
	      Defines the script called by the agent for kernel building after
			kernel filesets have been loaded.
	      Defines the path to the system's bootable kernel.
			This path is passed to the via the  environment	 vari‐
			able.
	      Defines  the  command called by the agent to mount all file sys‐
	      tems.
	      Defines the command called by the agent  to  reboot  the	system
	      after all
			filesets  have	been  loaded,  if  any of the filesets
			required reboot.
	      Defines the script called by the agent to	 perform  release-spe‐
	      cific
			remove	preparation.   For  an	OS update, this script
			will invoke the command when a fileset is removed.
			Please Note:  Transition links do not exist  on	 11.31
			and  newer releases so there are no remove preparation
			steps to perform; therefore, the is never executed for
			these releases.
	      Defines  the  protocol sequence(s) and endpoint(s) used when the
	      agent
			attempts to contact an alternate source	 depot	speci‐
			fied  by the option.  SD supports both the udp and tcp
			protocol sequence/endpoint.
	      If both source and target machine are  updated  to  SD  revision
	      B.11.00
			or later, the system administrator at the source depot
			machine can set this option to track which user	 pulls
			which  software from a depot on the source machine and
			when the software is pulled.  (A user running  from  a
			target machine cannot set this option; only the admin‐
			istrator of the source depot machine can set it.)
			When is set to a file is created on the	 source	 depot
			(for writable directory depots) or in (for tar images,
			CD-ROMs, or other nonwritable depots).
			Users can invoke the interactive user interface (using
			to  view,  print,  or  save the audit information on a
			remote or local depot.	Users can view audit  informa‐
			tion based on language preference, as long as the sys‐
			tem has the corresponding SD message catalog files  on
			it.   For  example,  a	user can view the source audit
			information in Japanese during one invocation of  then
			view the same information in English at the next invo‐
			cation.
	      Defines the path to the kernel's template file.
			This path is passed to the via the  environment	 vari‐
			able.
	      Defines the kernel build preparation script called by the agent.
			This  script must do any necessary preparation so that
			control scripts can  correctly	configure  the	kernel
			about  to  be built.  This script is called before any
			kernel filesets have been loaded.
	      Defines the command called by the	 target	 agent	to  uncompress
	      files
			after  transmission.   This  command  processes	 files
			which were stored on the media in a compressed format.
			If  the	 compression_type  stored with the file is the
			internal uncompression is used instead of the external
			The default value for HP-UX is undefined.
   Session File
       and do not use a session file.
   Environment Variables
       The environment variables that affect the and commands are:
	      Determines the language in which messages are displayed.
			   If  is not specified or is set to the empty string,
			   a default value of is used.	See  the  lang(5)  man
			   page by typing for more information.
			   Note: The language in which the SD agent and daemon
			   log messages are displayed is  set  by  the	system
			   configuration variable script, For example, must be
			   set to or to make the agent and daemon log messages
			   display in Japanese.
	      Determines  the  locale  to  be  used to override any values for
	      locale
			   categories specified by  the	 settings  of  or  any
			   environment variables beginning with
	      Determines the interpretation of sequences of bytes of text data
	      as
			   characters (for example,  single  versus  multibyte
			   characters	 in    values	 for	vendor-defined
			   attributes).
	      Determines the language in which messages should be written.
	      Determines the format of dates
			   (create_date and mod_date) when displayed  by  Used
			   by all utilities when displaying dates and times in
			   and
	      Determines the time zone	for  use  when	displaying  dates  and
	      times.
   Signals
       The  daemon  ignores  SIGHUP, SIGINT and SIGQUIT.  It immediately exits
       gracefully  after  receiving  SIGTERM  and  SIGUSR2.   After  receiving
       SIGUSR1,	 it waits for completion of a copy or remove from a depot ses‐
       sion before exiting, so that it	can  register  or  unregister  depots.
       Requests to start new sessions are refused during this wait.
       The  agent  ignores  SIGHUP, SIGINT, and SIGQUIT.  It immediately exits
       gracefully after receiving SIGTERM, SIGUSR1, or SIGUSR2.	  Killing  the
       agent may leave corrupt software on the system, and thus should only be
       done if absolutely necessary.  Note that when an SD command is  killed,
       the agent does not terminate until completing the task in progress.
   Locking
       The ensures that only one copy of itself is running on the system.
       Each  copy  of  that is invoked uses appropriate access control for the
       operation it is performing and the object it is operating on.
RETURN VALUES
       When the option is not specified, the returns:
	      When the daemon is successfully initialized and is now
			  running in the background.
	      When initialization failed and the daemon terminated.

       When the option is specified, the returns:

	      When the daemon successfully initialized and then
			  successfully shutdown.
	      When initialization failed or the daemon	unsuccessfully	termi‐
	      nated.

DIAGNOSTICS
       The and commands log events to their specific logfiles.

       The (target) log files cannot be relocated.  They always exist relative
       to the root or depot target path (for example, for the root and for the
       depot

       You can view the target log files using the or command.

       Daemon Log
	      The  daemon logs all events to (The user can specify a different
	      logfile by modifying the option.)

       Agent Log
	      When operating on (alternate) root file systems, the  logs  mes‐
	      sages to the file beneath the root directory (for example, or an
	      alternate root directory).

       Source Depot Audit Log
	      If both source and target machine are updated to	HP-UX  version
	      10.30  or	 later,	 the  system administrator at the source depot
	      machine can track which user pulls which software from  a	 depot
	      on the source machine and when the software is pulled.  Refer to
	      the option for more information.

       When operating on software  depots,  the	 logs  messages	 to  the  file
       beneath	the  depot  directory (for example, When accessing a read-only
       software depot (for example, as a source), the  logs  messages  to  the
       file

EXAMPLES
       To start the daemon:

       To restart the daemon:

       To stop the daemon:

FILES
       Contains the master list of current SD options (with their default val‐
       ues).

       The directory which contains all configurable
	      and non-configurable data for SD.	 This directory	 is  also  the
	      default location of logfiles.

       Contains	 the  active  system-wide  default  values  for some or all SD
       options.

       The file which stores the list of depots registered at the local host.

AUTHOR
       was developed by the Hewlett-Packard Company.   was  developed  by  the
       Hewlett-Packard Company and Mark H. Colburn (see pax(1)).

SEE ALSO
       install-sd(1M),	swacl(1M),  swask(1M), swconfig(1M), swcopy(1M), swin‐
       stall(1M),   swjob(1M),	 swlist(1M),   swmodify(1M),	swpackage(1M),
       swreg(1M), swremove(1M), swverify(1M), sd(4), swpackage(4), sd(5).

       available at

       SD customer web site at

								  swagentd(1M)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net