I have a Unix Script that has several exit in the middle. each returning seperate
exit codes.
I have to catch all the exit's and perform an operation say "Mail the status code" before the actual code completes.
How can i do this in KSH ? (3 Replies)
HI All,
I have created a unix script which takes 2 parameters and using sftp tranfers files to remote location
following is the script
#!/bin/ksh
#
#
# Parameter 1 is the complete path of the destination server
# Parameter 2 is the complete path of the file which is to be FTP... (1 Reply)
I know that the exit codes in scripting "$*" will returns all the parameters/arguments passwd to the script.
But I also know that "$@" will also returns the same. What is the difference between those two ? (1 Reply)
Good Morning All..
I was wondering about getting exit codes of a command in a shell script. I'm trying to run uvscan (McAfee command line scanner) and I want to have the log file say why, if at all, the process failed/exited.
Something to the extent of
If ; then
echo "This is why it... (1 Reply)
Hello,
I need to ensure that SCP does not leave any partially transmitted files on the remote server due to transmission errors.
Can it be assumed that:
1) if SCP returns a success with Exit Code == 0, a complete local file has been copied in its entirety to the remote location?
2)... (1 Reply)
how do i/is there a way to return the exit code from the remote host?
echo $? from the local host only gives 0, if the rexec command itself executes successfully. But what if in the case of the remote command failiing? echo $? on the localhost still gives 0, but I'm interested in the exit code... (4 Replies)
I am trying to run this SH on Linux and getting error at IF condition.
I want to read the EXIT code and send the failure or success message.
Please help me on this. This worked when i was running on Solaris.
#!/bin/bash
$ORACLE_HOME/bin/sqlplus abc/xyz@qwe @/home/test.sql
if ;... (4 Replies)
I have a script which connects to a remote server via FTP and gets some file from there.
#!/bin/bash
/usr/bin/ftp -n remote.hostname.com <<EOF
quote USER user123
quote PASS password123
lcd /dir1/dir2/dir3
cd /
mget file_pattern*
close
bye
EOF
rc=$?
if ]
... (7 Replies)
Discussion started by: dhruuv369
7 Replies
LEARN ABOUT FREEBSD
lockf
LOCKF(1) BSD General Commands Manual LOCKF(1)NAME
lockf -- execute a command while holding a file lock
SYNOPSIS
lockf [-kns] [-t seconds] file command [arguments]
DESCRIPTION
The lockf utility acquires an exclusive lock on a file, creating it if necessary, and removing the file on exit unless explicitly told not
to. While holding the lock, it executes a command with optional arguments. After the command completes, lockf releases the lock, and
removes the file unless the -k option is specified. BSD-style locking is used, as described in flock(2); the mere existence of the file is
not considered to constitute a lock.
If the lockf utility is being used to facilitate concurrency between a number of processes, it is recommended that the -k option be used.
This will guarantee lock ordering, as well as implement a performance enhanced algorithm which minimizes CPU load associated with concurrent
unlink, drop and re-acquire activity. It should be noted that if the -k option is not used, then no guarantees around lock ordering can be
made.
The following options are supported:
-k Causes the lock file to be kept (not removed) after the command completes.
-s Causes lockf to operate silently. Failure to acquire the lock is indicated only in the exit status.
-n Causes lockf to fail if the specified lock file does not exist. If -n is not specified, lockf will create file if necessary.
-t seconds Specifies a timeout for waiting for the lock. By default, lockf waits indefinitely to acquire the lock. If a timeout is speci-
fied with this option, lockf will wait at most the given number of seconds before giving up. A timeout of 0 may be given, in
which case lockf will fail unless it can acquire the lock immediately. When a lock times out, command is not executed.
In no event will lockf break a lock that is held by another process.
EXIT STATUS
If lockf successfully acquires the lock, it returns the exit status produced by command. Otherwise, it returns one of the exit codes defined
in sysexits(3), as follows:
EX_TEMPFAIL The specified lock file was already locked by another process.
EX_CANTCREAT The lockf utility was unable to create the lock file, e.g., because of insufficient access privileges.
EX_UNAVAILABLE
The -n option is specified and the specified lock file does not exist.
EX_USAGE There was an error on the lockf command line.
EX_OSERR A system call (e.g., fork(2)) failed unexpectedly.
EX_SOFTWARE The command did not exit normally, but may have been signaled or stopped.
SEE ALSO flock(2), sysexits(3)HISTORY
A lockf utility first appeared in FreeBSD 2.2.
AUTHORS
John Polstra <jdp@polstra.com>
BSD July 7, 1998 BSD