Funny but true....


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Funny but true....
Prev   Next
# 1  
Old 03-26-2008
Funny but true....

Hallo everybody

I am having a shell script called auto_run.sh in that only the first line works.
the second line which has sed command is working only at the # prompt. not within the shell script. What could be the reason.

*... sed 's/ //g' KTI >abc works in another shell script without the first line.when i add the exec....statement it stops working. Please can anyone help me.Thanks


exec auto_inv.4ge >KTI
sed 's/ //g' KTI > abc
exit
 
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. What is on Your Mind?

Funny *NIX commands

Hello All, Just want to share some funny *NIX commands :). $ make love make: *** No rule to make target `love'. Stop. On a FreeBSD make: $ make love Not war. $ \(- bash: (-: command not found $ man woman No manual entry for woman $ touch /me touch: cannot touch `/me':... (5 Replies)
Discussion started by: RavinderSingh13
5 Replies

2. What is on Your Mind?

Old, but still funny

Annoyances.org - Upgrading to Wife 1.0 (0 Replies)
Discussion started by: jgt
0 Replies

3. What is on Your Mind?

Very Funny - Had to laugh

Guys, This is funny. http://i28.photobucket.com/albums/c228/jralph2005/bart.png jaysunn (2 Replies)
Discussion started by: jaysunn
2 Replies

4. What is on Your Mind?

Funny things from FunnyJunk

Just one i like. Missing Cat! ! ! (0 Replies)
Discussion started by: Action
0 Replies

5. Shell Programming and Scripting

Echo working funny

Hello, this is my first post and question. I have search before for this problem but didn't find anything similar. My case: I have a string inside the variable string1 like this: string1="lala lele lili lolo lulu" When I do echo of it, it appears like this: echo $string1 lala lele lili... (8 Replies)
Discussion started by: hemtar
8 Replies

6. What is on Your Mind?

Funny Quotes-UNIX

If you people find something funny like these go ahead and post it :) (5 Replies)
Discussion started by: vidyadhar85
5 Replies
Login or Register to Ask a Question
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)