HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swask(1M) swask(1M)
(Hewlett-Packard Company)
See loglevel below and the sd(5) manual page, by typing man 5 sd, for more infor-
mation.
logfile=/var/adm/sw/swask.log
Defines the default log file for swask.
loglevel=1
Controls the log level for the events logged to the command logfile and the target agent
logfile. A value of
0 provides no information to the logfile.
1 enables verbose logging of key events to the log files.
2 enables very verbose logging, including per-file messages, to the log files.
patch_filter=*.*
Used in conjunction with the autoselect_patches or patch_match_target
options to filter the available patches to meet the criteria specified by the filter. A key use is
to allow filtering by the "category" attribute. Requires patches that are in an enhanced SD
patch format.
run_as_superuser=true
This option controls SD’s nonprivileged mode. This option is ignored (treated as true) when
the invoking user is super-user.
When set to the default value of true, SD operations are performed normally, with permis-
sions for operations either granted to a local super-user or set by SD ACLs. (See swacl(1M)
for details on ACLs.)
When set to false and the invoking user is local and is not super-user, nonprivileged mode
is invoked:
• Permissions for operations are based on the user’s file system permissions.
• SD ACLs are ignored.
• Files created by SD have the uid and gid of the invoking user, and the mode of created
files is set according to the invoking user’s umask.
SD’s nonprivileged mode is intended only for managing applications that are specially
designed and packaged. This mode cannot be used to manage the HP-UX operating system
or patches to it. For a full explanation of nonprivileged SD, see the Software Distributor
Administration Guide, available at the
http://docs.hp.com web site.
See also the
admin_directory
and installed_software_catalog options.
verbose=1
Controls the verbosity of the output (stdout):
0 disablesoutput to stdout. (Error and warning messages are always written to stderr).
1 enables verbose messaging to stdout.
Session Files
Each invocation of swask defines a task session. The invocation options, source information, software
selections, and target hosts are saved before the task actually commences. This lets you re-execute the
command even if the session ends before proper completion.
Each session is saved to the file $HOME/.sw/sessions/swask.last
. This file is overwritten by
each invocation of
swask.
To save session information in a different location, execute swask with the -C session__file option.
A session file uses the same syntax as the defaults files. You can specify an absolute path for a session file.
If you do not specify a directory, the default location for a session file is
$HOME/.sw/sessions/
.
To re-execute a session, specify the session file as the argument for the
-S session__file option.
When you re-execute a session file, the values in the session file take precedence over values in the system
defaults file. Likewise, any command line options or parameters that you specify when you invoke swask
take precedence over the values in the session file.
Software and Target Lists
You can use files containing software and target selections as input to the
swask command. See the -f
and -t options for more information.
Section 1M−−852 − 5 − HP-UX Release 11i: December 2000
___
___