07-03-2006
the slash was the problem, now the variables are getting into the package.
thanks!
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Apologies if anyone has read my recent post on the same subject in the Linux forum, just thought actually the solution might more likely come from scripting.
Essentially, I am trying to restrict access to directories based on the user's name AND their location on a session-by-session... (3 Replies)
Discussion started by: en7smb
3 Replies
2. Solaris
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies
3. Shell Programming and Scripting
Hi All,
OS:AIX 64 bits
Would like to know what is the command to launch vnc session from unix shell script so that Reports server is started from vnc session which should be launched from within the shell script.
Thanks for your time!
Regards, (0 Replies)
Discussion started by: a1_win
0 Replies
4. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
5. Shell Programming and Scripting
Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
Discussion started by: jgt
3 Replies
6. Solaris
what is the difference between desktop session and console session in solaris
as i am wondering we use option -text for the former and -nowin for the later (1 Reply)
Discussion started by: kishanreddy
1 Replies
7. Shell Programming and Scripting
Hello all,
I would like to declare and use variables inside an ssh session. I have the feeling that it's not possible. Here is the situtation simpified:
#:/bin/sh
test="salut"
echo $test
ssh hudson@10.41.21.99 <<EOF
export testssh="salut"
echo testssh=$testssh
... (4 Replies)
Discussion started by: Lotfus
4 Replies
8. Shell Programming and Scripting
Hi,
I need help in writing a shell script which can read data from a text file (Cancel_ID.txt) and then calls sqlplus session (Cancel.sql) with the first line parameter of the text file ("0322600453") till all rows are not completed.
... (4 Replies)
Discussion started by: Khan28
4 Replies
9. UNIX for Advanced & Expert Users
Below code runs n number of session at a time when called. I want to restrict it to run only for 3 sqlplus at a time. Is there a way to do the same.
for name in `cat abc.txt`
do
(sqlplus -s usert/password@host <<-EOF>> error.txt
SET LINESIZE 1000
select '$name',... (4 Replies)
Discussion started by: ATWC
4 Replies
LEARN ABOUT LINUX
deb-split
deb-split(5) Debian deb-split(5)
NAME
deb-split - Debian multi-part binary package format
SYNOPSIS
filename.deb
DESCRIPTION
The multi-part .deb format is used to split big packages into smaller pieces to ease transport in small media.
FORMAT
The file is an ar archive with a magic value of !<arch>. The file names might contain a trailing slash (since dpkg 1.15.6).
The first member is named debian-split and contains a series of lines, separated by newlines. Currently seven lines are present. The first
is the format version number, 2.1 at the time this manual page was written. The second is the package name. The third is the package ver-
sion. The fourth is the md5sum of the package. The fifth is the total size of the package. The sixth is the maximum part size. The seventh
is the current part number, followed by a slash and the total amount of parts (as in '1/10').
Programs which read multi-part archives should be prepared for additional lines to be present, and should ignore these if this is the case.
If the version number has changed, an incompatible change has been made and the program should stop. If it has not, then the program should
be able to safely continue, unless it encounters an unexpected member in the archive (except at the end), as described below.
The second, last required member is named data.N, where N denotes the part number. It contains the raw part data.
These members must occur in this exact order. Current implementations should ignore any additional members after data.N. Further members
may be defined in the future, and (if possible) will be placed after these two.
SEE ALSO
deb(5), dpkg-split(1).
Debian Project 2010-01-28 deb-split(5)