Sponsored Content
Top Forums Shell Programming and Scripting Maintaining Command Line Integrity Post 302569501 by dude2cool on Monday 31st of October 2011 01:47:12 PM
Old 10-31-2011
Hmm, the only way I can think of is for you to escape the double-quotes when you pass them to your script.

Code:
# /tmp/123.sh 1 \"2\" 3

1
"2"
3

 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Printing to Windows and maintaining control

I'm new at the entire spectrum of printing in Unix, and especially when--as I understand it--the printers are on a Windows server. At work we have a variety of printers and printing from Windows, or from Unix via lp or lpr works fine. The initial problem: Our users will be printing up to 20... (1 Reply)
Discussion started by: effigy
1 Replies

2. UNIX for Dummies Questions & Answers

Command for maintaining the list of commands used

Hi, There is a command by which you can maintain a list of commands previously typed. By this you dont have to type in the same command again and can use the up-down arrows to scroll through the list. Which is this command, i am not able to recall. (8 Replies)
Discussion started by: appledrive
8 Replies

3. UNIX for Advanced & Expert Users

Maintaining different version Control account

How can I maintain different version control account(any common unix based version control like CVS,RCS,SCCS..) from a single UNIX Login Account. Many programmers share a common UNIX user/login account.How do they maintain separate Version Control Account. (1 Reply)
Discussion started by: johnbach
1 Replies

4. UNIX for Dummies Questions & Answers

Maintaining HOURLY backups

I have a system where i take hourly back-ups of the system.The script for maintaining full backup for the last 5 days is find /backup/server -type f -mtime +4 -exec rm -f {} \; works fine for keeping the files of some 5 days old. In the case of hourly backups.How do we write to keep... (2 Replies)
Discussion started by: ravi55055
2 Replies

5. Shell Programming and Scripting

Maintaining file currency

I have a common data folder with files like x* which is accessed by 3 unix servers. Now each server will try to pick one file form this folder and move it to its local folder. How to maintain file concurrency in this case?I dont want the same file to be accessed by more than one process. (2 Replies)
Discussion started by: prasperl
2 Replies

6. Shell Programming and Scripting

Maintaining file structure

Hi guys, I am trying to store some output in a file and then compare it to another file. I am gathering information from 2 commands: cat /opt/jbin/server.log.tmp > A grep "ephemeral" /opt/jbin/log/server.log.2015-05-02-18 > B The contents of both file are the same. This means if I do a... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies

7. Solaris

Maintaining SA logs /var/adm/sa/

Hi all, I have enable sar and the sa cron jobs in the sys account. I would like to however, keep only 1 month of data. Can i check for Solaris10, does sa2 do automatic purging of logs in /var/adm/sa/ that are 1 week old ? -- Answer = yes ( in "/usr/lib/sa/sa2" if you open the script,... (2 Replies)
Discussion started by: javanoob
2 Replies

8. Shell Programming and Scripting

Checking integrity copied from remote server using UNIX command

I am getting a file (abc.txt) using scp from remote server. scp <connect string> -i $HOME/.ssh/id_dsa rem_id@hostname:/var/prod/abc.txt /var/prod/abc.out Before loading I need to check if the file is indeed same , for that I thought of checking the line count but when I used ssh command it was... (3 Replies)
Discussion started by: lalitpct
3 Replies
exit(1)                                                            User Commands                                                           exit(1)

NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps SYNOPSIS
sh exit [n] return [n] csh exit [ ( expr )] goto label ksh *exit [n] *return [n] DESCRIPTION
sh exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of the last command executed (an EOF will also cause the shell to exit.) return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe- cuted. csh exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the expression expr. The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to jump to a label that occurs between a while or for built-in command and its corresponding end. ksh exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8 bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit except for a shell which has the ignoreeof option (See set below) turned on. return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return is invoked while not in a function or a '.' script, then it is the same as an exit. On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari- able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not performed. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
break(1), csh(1), ksh(1), sh(1), attributes(5) SunOS 5.10 15 Apr 1994 exit(1)
All times are GMT -4. The time now is 02:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy