12-08-2008
explain the commands below
logfile=$(find $jobroot/logs -mtime -1 | grep runoraback ) echo 'here is the logfile:'
echo "$logfile"
echo "$logfile" > $wkdir/log.$$
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
:start
/@~/{
h
s/\(.*\)@~.*$/\1/
s/@~$//
s/@~/\
/g
p
g
s/.*@~\(.*\)/\1/
}
//{
N
s/\n/ /
b start
} (2 Replies)
Discussion started by: djkane
2 Replies
2. Programming
Hello all,
i've written a small piece of code that will read commands from standard input and executes the commands.
Its working fine and is execting the commands well. Accepting arguments too. e.g
#mkdir <name of the directory>
The problem is that its not letting me change the directory i.e... (4 Replies)
Discussion started by: Phrozen Smoke
4 Replies
3. Shell Programming and Scripting
I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config.
I am not sure if I can do this with BASH scripting.
I have set up password less login by adding my public key to authorized_keys file, it works.
I am a little... (1 Reply)
Discussion started by: bash_in_my_head
1 Replies
4. UNIX for Dummies Questions & Answers
Is it possible for both commands to work? (1 Reply)
Discussion started by: phunkypants
1 Replies
5. Shell Programming and Scripting
cur_fy=`grep "CONSOL" $GLDATA/parms/cur_fiscalyear.lis | awk '{print $2}'
Here i don't understand "CONSOL" and awk'{print$2)
Please help me out
cur_fiscalyear.lis contents :
DL 2011
MOL 2011
MV 2011
SF 2010
CONSOL 2011
MVU 2011 (3 Replies)
Discussion started by: Diddy
3 Replies
6. Shell Programming and Scripting
cat $BDDATA/svucon$i_bal_dup_email.dat ; uuencode $dup_in $dup_out
here svucon$i_bal_dup_email.dat ???
and uuencode ??
Please use and tags when posting code, data or logs etc. to preserve formatting and enhance readability, thanks. (2 Replies)
Discussion started by: Diddy
2 Replies
7. Shell Programming and Scripting
Dear unix team
i'm user for a system build on unix system ,so we need to run a lot of scripts not in one sission but every script on the associated terminal , so the script name = the name of the terminal which will run this script on it . and someone create a batch that make as below :
1- but... (4 Replies)
Discussion started by: fofatoti
4 Replies
8. Shell Programming and Scripting
why the case 2 will happen ? , ' should stop the history substitution ,shouldn't it?
case 1
# echo "123"|sed '/123/!d'
123
case 2
# echo "123
> 456
> 1
> "|sed '/123/!d'
-bash: !d': event not found
case 3
# echo "123
> 456
> 12
> "|sed '/123/'\!d
123
# bash --version (1 Reply)
Discussion started by: justlooks
1 Replies
9. UNIX for Dummies Questions & Answers
Could you please tell the meaning of Below mentioned perl script lines:
format OWNER_TOTAL =
@< Owner Code @<<<<<<total: @#######.## @#######.## @#######.## @#######.## @#######.## @#######.## @#######.## @#######.## @#######.## @#######.## @######
#.##
$prev_cust_type, $prev_owner_code,... (2 Replies)
Discussion started by: vinothrajan55
2 Replies
10. UNIX for Dummies Questions & Answers
Hi friends! I'm learning UNIX and I have a small question. Working with Shell, i put the name of one executable (in c language) + one number and it says this:
$ gcc misterioso_4.c
$ ./misterioso_4 6
got: ,
I can not find an answer in the manual because I havent applied any variable.... (5 Replies)
Discussion started by: dakota
5 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)