9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I tried writing a script and there was a problem with SFTP part
can some one correct where is is the mistake
Enveronment file
#!/bin/bash
export HOST_NAME=<>
export USER_NAME=<>
export PASSWORD=<>
export SOURCE_PATH=/u03/informatica/current/server/infa_shared/TgtFiles/mfg
export... (4 Replies)
Discussion started by: spradeep86
4 Replies
2. Shell Programming and Scripting
Hi,
I am trying to capture logs of the script in the file as well as on the screen. I have used exec and tee command for this. While using exec command I am getting the correct output in the file but, script output is not getting displayed on the screen as it get executed.
Below is my sample... (14 Replies)
Discussion started by: Prathmesh
14 Replies
3. Shell Programming and Scripting
###############
#filename.sh
###############
CUREENT_DATE=02
log_file_path="$CUREENT_DATE"-"${0##%*/}`|cut -d "." -f1|awk -F "/" '{print $NF}'`"".log"
echo $log_file_path
################
#output required
02-filename.log (6 Replies)
Discussion started by: mohitmehral
6 Replies
4. Shell Programming and Scripting
ret=`sqlplus -s /nolog << EOF
connect $db_user/$db_pwd@$db_sid;
SPOOL ./$DirectoryName/TableData.txt;
set pagesize 0 feedback off verify off heading off echo off linesize 150
while read var_ack_party_name
do
select * from bus_event where ack_party_name like... (13 Replies)
Discussion started by: rkrish
13 Replies
5. Shell Programming and Scripting
#!/bin/ksh
db_user=$DB_USER_NAME
db_pwd=$DB_PASSWORD
db_sid=$TWO_TASK
if ; then
echo "\tUsage: MoveUsageProcessing <BC Log file Name>"
exit 1
else
BCLogFileName=$1
fi
grep -i 'MoveUsage daemon needs to run on this account before it can be billed' $1 |awk -F\| '{for(i=0;++i<=NF;) if($i ~... (1 Reply)
Discussion started by: Rajesh Putnala
1 Replies
6. Emergency UNIX and Linux Support
Please correct my script if it any exceptional, since im calling other external script with in my script.
#!/bin/bash
FE1=TMM
DT1=/home/myHome/dated_1
REPORT=/home/otherHome/Report.sh
## Run the report for FE1 & DT1
cd /home/myHome
SERV_LST=/home/myHome/srvc-lst
echo "Welcome to... (5 Replies)
Discussion started by: raghunsi
5 Replies
7. Shell Programming and Scripting
Wrong post (2 Replies)
Discussion started by: tuffEnuff
2 Replies
8. Shell Programming and Scripting
I am new to awk, can somone please correct the following script
awk -F "," 'BEGIN {
foreach ((getline < "file1.csv") > 0)
{i++
a=1 --> assuming the first column in the row will be stored in a
foreach (a in f1) {
if (a == $5) continue
print a;
}
}
} file2.csv'
Here is what I... (11 Replies)
Discussion started by: nuthalapati
11 Replies
9. Shell Programming and Scripting
Here is the script. I am not able to increment and Print echo "2=" ${arr}
(Bold line)
Can someone please help me correct it? I am thinking there is some escape sequence error. Just started learning scripts ...
Thanks
#!/bin/ksh
set -A arr a1 a2 a3 a4
# START
Server1=gmi
... (6 Replies)
Discussion started by: psreddy1234
6 Replies
Perl::Critic::Policy::InputOutput::ProhibitExplicitStdinUser Contributed Perl DocumentaPerl::Critic::Policy::InputOutput::ProhibitExplicitStdin(3)
NAME
Perl::Critic::Policy::InputOutput::ProhibitExplicitStdin - Use "<>" or "<ARGV>" or a prompting module instead of "<STDIN>".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Perl has a useful magic filehandle called *ARGV that checks the command line and if there are any arguments, opens and reads those as
files. If there are no arguments, *ARGV behaves like *STDIN instead. This behavior is almost always what you want if you want to create a
program that reads from "STDIN". This is often written in one of the following two equivalent forms:
while (<ARGV>) {
# ... do something with each input line ...
}
# or, equivalently:
while (<>) {
# ... do something with each input line ...
}
If you want to prompt for user input, try special purpose modules like IO::Prompt.
CONFIGURATION
This Policy is not configurable except for the standard options.
CAVEATS
Due to a bug in the current version of PPI (v1.119_03) and earlier, the readline operator is often misinterpreted as less-than and greater-
than operators after a comma. Therefore, this policy misses important cases like
my $content = join '', <STDIN>;
because it interprets that line as the nonsensical statement:
my $content = join '', < STDIN >;
When that PPI bug is fixed, this policy should start catching those violations automatically.
CREDITS
Initial development of this policy was supported by a grant from the Perl Foundation.
AUTHOR
Chris Dolan <cdolan@cpan.org>
COPYRIGHT
Copyright (c) 2007-2011 Chris Dolan. Many rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module
perl v5.16.3 2014-06-09 Perl::Critic::Policy::InputOutput::ProhibitExplicitStdin(3)