Software Distributor Administration Guide (March 2009)

Table 11-3 swask Command Options and Default Values
• log_msgid=0
• logdetail=false
• logfile=/var/adm/sw/swask.log
• loglevel=1
• lookupcache_timeout_minutes=10
• patch_filter=*.*
• run_as_superuser=true
• verbose=1
• admin_directory=/var/adm/sw
• ask=true
• autoselect_dependencies=true
• autoselect_minimum_dependencies=false
• autoselect_patches=true
• enforce_scripts=true
• installed_software_catalog=products
For More Information
See Appendix A (page 299) for complete descriptions of each default.
11.11 Request Script Tasks and Examples
You can run request scripts from the swinstall or swconfig commands by setting
the ask option to true. This tells the commands to run request scripts (if any exist) in
addition to performing install or configuration tasks. (Note that the value of the ask
option if false for both swinstall and swconfig but is true for swask.)
11.11.1 swask Examples
Run all request scripts from the default depot (/var/spool/sw) and write the response
file (response) back to the same depot:
swask -s /var/spool/sw \*
Run the request script for Product1 from depot /tmp/sample.depot.1 on remote
host swposix, create the catalog /tmp/test1.depot on the local controller machine,
and place the response file (response) in the catalog:
# swask -s swposix:/tmp/sample.depot.1 \
-c /tmp/test1.depot Product1
Run request scripts from remote depot /tmp/sample.depot.1 on host swposix
only when a response file is absent, create the catalog /tmp/test1.depot on the
local controller machine, and place the response file (response) in the catalog:
# swask -s swposix:/tmp/sample.depot.1 \
-c /tmp/test1.depot -x ask=as_needed \*
11.11.2 swinstall Examples
To install all the software from local depot tmp/sample.depot.1 using any response
files generated by request scripts:
# swinstall -s /tmp/sample.depot.1 -x ask=true \*
11.11 Request Script Tasks and Examples 293