09-09-2008
So... how is the Solaris pkgadd command going to know where you have set this new BASEDIR value? Are you passing it as a parameter on the pkgadd command-line somehow?
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I have this code, and i want work with a ls -shalR output in .txt
What i need read to do this??
Where start?
#!/usr/bin/perl
# Allrights- A perl tool for making backups of file permissions
# Copyright (C) 2005 Norbert Klein <norbert@acodedb.com>
# This program is free... (1 Reply)
Discussion started by: joangopan
1 Replies
2. Shell Programming and Scripting
I am posting a script below which essentially excutes the following functions in the described order.
1) From a source directory pools together three files generated by system logs for each user session, tar's these files and archives them as a log set in a destination directory and these... (0 Replies)
Discussion started by: Sammy
0 Replies
3. UNIX for Advanced & Expert Users
I am creating a package(Solaris10 on sparc) that needs user input.
As I understand it, I need to use a request script.
My problem is that the value I set in my request script is not visible in my postinstall script. Not sure if I am doing it right.
Here is an example request script... (4 Replies)
Discussion started by: Tornado
4 Replies
4. Shell Programming and Scripting
Hi,
I have a script which connect to ATM's and pull two files from the ATM.
The which i try to pull is like
PIC20085200001*.JPG
First 7 digit consist of year montn and date as well
After todays execution i want to change the date to next date
I add few lines in the script but it is not... (6 Replies)
Discussion started by: Renjesh
6 Replies
5. Shell Programming and Scripting
Is there an equivalent of basedir in shell script? I have a file location and I want to lowercase just the filename not the path. (2 Replies)
Discussion started by: mainegate
2 Replies
6. Shell Programming and Scripting
Hi,
In the request script I need to read user input and store to variable to use it later in postinstall script.
e.g.
LOGDIR=/app/log
echo "Please type the Log Directory : (current value: $LOGDIR)"
read LOGDIR
When asked, if the user enters a value the parameter is ok and I... (2 Replies)
Discussion started by: potro
2 Replies
7. Shell Programming and Scripting
hello forum members,
I have a script which is used find the Uname and passwords and redirects into a output.txt file.I hardcoded a string "ciadev" but iwant search two more strings also "absdev" and "absprod" So modify this script please.
I am lookinmg forward from you,
please find the below... (2 Replies)
Discussion started by: rajkumar_g
2 Replies
8. Shell Programming and Scripting
I am working on a script to install a software distribution which ships as a *.tar.gz file. The company doesn't name the dist consistently, but the resulting directory out of the *.tar.gz file (ie: XXX_X_X_X) is consistent and shows the software version.
I'm writing this with BASH-3.25.x... (4 Replies)
Discussion started by: forrie
4 Replies
9. Shell Programming and Scripting
Hello;
I'm having about 800 log files and i'm trying to write a script that report the counts of lines per second or "requests per second" in each log file and report the output which includes the timestamp for the highest lines per second count and the log file name and the highest number per... (5 Replies)
Discussion started by: Katkota
5 Replies
pkgask(1M) pkgask(1M)
NAME
pkgask - stores answers to a request script
SYNOPSIS
pkgask [-d device] [-R root_path] -r response pkginst...
pkgask allows the administrator to store answers to an interactive package (one with a request script, that is, a user-created file that
must be named request). Invoking this command generates a response file that is then used as input at installation time. The use of this
response file prevents any interaction from occurring during installation since the file already contains all of the information the pack-
age needs.
The following options are supported
-d device Run the request script for a package on device. device can be a directory pathname or the identifiers for tape, floppy disk
or removable disk (for example, /var/tmp, /dev/diskette, and /dev/dsk/c1d0s0). The default device is the installation spool
directory.
-R root_path Define the full path name of a directory to use as the root_path. All files, including package system information files,
are relocated to a directory tree starting in the specified root_path.
Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the
global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's
file system. See zones(5).
-r response Identify a file or directory which should be created to contain the responses to interaction with the package. The name
must be a full pathname. The file, or directory of files, can later be used as input to the pkgadd(1M) command.
The following operands are supported:
pkginst Specify the package instance, or list of instances for which request scripts will be created. The token all may be used to
refer to all packages available on the source medium.
0 Successful completion.
>0 An error occurred.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1), installf(1M), pkgadd(1M), pkgchk(1M), pkgrm(1M), removef(1M),
admin(4),attributes(5)
The -r option can be used to indicate a directory name as well as a filename. The directory name is used to create numerous response files,
each sharing the name of the package with which it should be associated. This would be used, for example, when you will be adding multiple
interactive packages with one invocation of pkgadd(1M). Each package would need a response file. To create multiple response files with the
same name as the package instance, name the directory in which the files should be created and supply multiple instance names with the
pkgask command. When installing the packages, you will be able to identify this directory to the pkgadd(1M) command.
If the default admin file is too restrictive, the administration file may need to be modified to allow for total non-interaction during a
package installation. Seeadmin(4) for details.
6 Apr 2005 pkgask(1M)