02-24-2015
The command
exit does just that, exit the current process. If the current process is the login shell, then you get logged off. What you are doing by calling
exec program is to say 'replace the current shell with
program' so when the
program ends, there is nothing to go back to.
What is your desired response?
- CNTL-d ends program but does not log out (where do you go then)
- Failure to find program logs out
- Normal termination logs out
- The complete opposite of any/all of these?
If you can be clear about what you want to happen, then we can probably work out a way to make it so.
Robin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am running JDictd (http://www.informatik.uni-leipzig.de/~duc/Java/JDictd/) from tcsh in Terminal on Mac OS X (:=Darwin=FreeBSD/Mach).
I am trying to get it to exit cleanly silently upon Mac OS X system shutdown.
My idea was that if there was a logout script in FreeBSD (basically a script... (1 Reply)
Discussion started by: ropers
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all
I know ho I can run a script when a user logs in, viz using the .login or .profile file, however what can I use to run a script when a user logouts ?
Thanks
J :confused: (1 Reply)
Discussion started by: jhansrod
1 Replies
3. Shell Programming and Scripting
there are many script in my project.i am having a problem when i am trying to quit from child script.what is the command to wrap up all the parent script and calling script as well? exit 0 is not working.please help.... (1 Reply)
Discussion started by: arghya_owen
1 Replies
4. Shell Programming and Scripting
I have a script abc.sh. Its contents are as follows: (7 Replies)
Discussion started by: lassimanji
7 Replies
5. Shell Programming and Scripting
Hi,
I am trying to exit the script from a function.
I was in assumption that if we use exit ( inside or outside the function) it will exit from the script.
alternatively, return will exit from that particular function.
but in my case, exit is exiting from the function and not the script.... (8 Replies)
Discussion started by: shellwell
8 Replies
6. Shell Programming and Scripting
Hi Everybody,
I want to run my own script on logout , i can use .bash_logout file... problem is this will work only for that particular user... i want to know the common file... so that script wil run for all the user...
2. How to run script on Shutdown ?
Thanks in advance
Anitha (4 Replies)
Discussion started by: anisn2002
4 Replies
7. Shell Programming and Scripting
I have a script planned for the Helpdesk to allow them to (on a couple of RHEL 3 / RHEL 5 servers) reset passwords, stop / start printers, and clear print queues. The appropriate sudo permissions were given to their accounts, and the individual functions all work just fine. The ability to move... (0 Replies)
Discussion started by: tearsong
0 Replies
8. Shell Programming and Scripting
I have to write a script in ksh which again should call another script. Say A.ksh is calling B.ksh. Now in B.ksh if the condition we are checking for is true then we have to go back to the main script A.ksh or if the condition in B.ksh is false then we have to totally come out of the scripts.
I... (1 Reply)
Discussion started by: vpv0002
1 Replies
9. Shell Programming and Scripting
Hi Team,
Need your help for the below code snippet. I wrote a module to read the file names remote server using file name convention.
Issue : My script is coming out from while loop without reading complete file.
test1()
{
while read line
do
echo $line
file_nm_convention=`echo... (3 Replies)
Discussion started by: gvkumar25
3 Replies
10. Shell Programming and Scripting
function2()
{
cmd1
cmd2
cmd3
....
cmdn
}
function2()
{
cmd11
cmd12
cmd13
....
....
}
for i in {1,2} (7 Replies)
Discussion started by: yanglei_fage
7 Replies
log(8) System Manager's Manual log(8)
NAME
log - Records input and output from a program
SYNOPSIS
/usr/sbin/log <logfile> <command>
OPERANDS
The file in which to record the interaction being logged. The command to execute.
DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until
<command> exits, the log program exits, and the exit status of <command> is returned.
The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and
/var/adm/smlogs/it.log installation log files.
RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation.
The log program does not search for the PATH variable to locate <command> and error messages are terse.
The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands
will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will
not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log
foo.tmp /sbin/sh -i
In the previous example, foo.tmp is the name of <logfile>.
The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must
exit by some other means.
ERRORS
Log open error
Explanation:
The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.
Exec Error
Explanation:
The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe-
cutable file.
Fork Error
Explanation:
The log program was unable to create one of the processes it requires to log data.
SEE ALSO
Commands: it(8), script(1)
log(8)