11-02-2011
shouldn't work=/work/input/telefonia be defined as WORK=/work/input/telefonia?
check all of your if/then/else/fi combos to make sure they're balanced. Also check the here-docs, etc...
Last edited by vgersh99; 11-02-2011 at 06:03 PM..
This User Gave Thanks to vgersh99 For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello
I am executing the following script
nawk 'NR == 1 || substr($0,63,5) ~ /H... / && \
_++ == 2 { fn && close(fn); fn = "part_" ++c; _ = 1 }
{ print > fn }' sample.dat
When i execute as it is it is executing fine. but when i execute the whole script as a single line like below
... (2 Replies)
Discussion started by: dsdev_123
2 Replies
2. Shell Programming and Scripting
My script is as below :
#!/bin/sh
for line in `cat Results.txt`
do
FEILD1=`echo $line |awk -F"|" '{print $1}'`
FEILD2=`echo $line |awk -F"|" '{print $2}'`
FEILD3=`echo $line |awk -F"|" '{print $3}'`
FEILD4=`echo $line |awk -F"|" '{print $4}'`
echo "$FEILD1 $FIELD2 $FIELD3 $FIELD4"
done ... (15 Replies)
Discussion started by: shwetainnani
15 Replies
3. Shell Programming and Scripting
I am executing the below in telnet
#!/usr/bin/ksh
File1=simple.txt # The file to check
LogFile=simple.log # The log file
DelayMax=30 # Timeout delay
Tolerance=2
# BEGIN ##############################
while true
do
StampNow=$(date +%s)/60 # stamp in minutes
... (3 Replies)
Discussion started by: chinniforu2003
3 Replies
4. UNIX for Dummies Questions & Answers
Hi ,
I m getting an error after executing the script.
My script.
Script is used to find out the date on 8 different machines(mentioned in SERVERNAMES file).
I have added public key to avoid ssh password and ssh without password working fine.
#!/bin/sh
fn_VMFind()
{
Date=`ssh -t... (5 Replies)
Discussion started by: pinga123
5 Replies
5. Shell Programming and Scripting
Hi
Please assist. Im getting an error while execuing the script name d "cdsnd.basel.cd_new
" as siiadm user. Thanks.
siiadm> ls -l
total 64
-rwxr-xr-x 1 siiadm sboadm 1004 Sep 17 2008 cdsnd.basel.cd
-rwxr-xr-x 1 siiadm sapsys 998 Nov 16 09:14 cdsnd.basel.cd_new... (1 Reply)
Discussion started by: samsungsamsung
1 Replies
6. Shell Programming and Scripting
Hi,
I am not able to figure out what the problem is:
getting the following error
sqltst.sh: 1: not found
here is the script
#!/bin/sh
. /home/dev1/.profile
. /home/dev1/.infenv
`sqlplus -s $REPDB_LOGON << EOF
SET SERVEROUT ON
SET FEEDBACK OFF
SET HEADING OFF
SET TRIMSPOOL... (4 Replies)
Discussion started by: svajhala
4 Replies
7. Linux
hi all,
i am getting libssh2 error while executing script in RHEL 6, when i locate that file its not there below is the ouput of this
# locate libssh2_agent_init
# cat /etc/issue
Red Hat Enterprise Linux Server release 6.1 (Santiago)
Kernel \r on an \m
how do i resolve this issue, i... (1 Reply)
Discussion started by: muzaffar.k
1 Replies
8. UNIX for Dummies Questions & Answers
I have the following script test.sh owned by dwdev account and group dwdev, the permissions on the script are as follows.
-rw-r-x--- 1 dwdev dwdev 279 Sep 17 13:19 test.sh
Groups:
cat /etc/group | grep dwdev
dwdev:x:704:dwdev
dwgroup:x:725:dwdev
writers:x:726:dwdev
User:
cat /etc/passwd |... (3 Replies)
Discussion started by: Ariean
3 Replies
9. Shell Programming and Scripting
getting error as below while executing script in linux.
OS version:
Linux VGP-3GPSDB-LX 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
./imxtract.sh: line 395: unexpected EOF while looking for matching ``'
./imxtract.sh: line 402: syntax error:... (1 Reply)
Discussion started by: Riverstone
1 Replies
10. Red Hat
Hi,
I wrote this script to test if the output for DIR1 and DIR2 comes out as I want :
#!/bin/bash
DAY=$(date +%d)
MONTH=$(date +%b)
YEAR=$(date +%Y)
DIR1=$($MONTH$YEAR"_Blast_BC01")
DIR2=$($MONTH$YEAR"_Blast_BC15")
echo $DIR1
echo $DIR2
This is the output I want for echo $DIR1 ... (12 Replies)
Discussion started by: anaigini45
12 Replies
LEARN ABOUT HPUX
xtappaddworkproc
XtAppAddWorkProc() XtAppAddWorkProc()
XtAppAddWorkProc - register a procedure to be called when the event loop is idle.
Synopsis
XtWorkProcId XtAppAddWorkProc(app_context, proc, client_data)
XtAppContext app_context;
XtWorkProc proc;
XtPointer client_data;
Inputs
app_context
Specifies the application context.
proc Specifies the procedure that is to be called when the application is idle.
client_data
Specifies data to be passed to proc when it is called.
Returns
A handle of type XtWorkProcId that can be passed to XtRemoveWorkProc() to unregister the work procedure.
Description
XtAddWorkProc() registers the procedure proc and the data client_data to be called by XtAppNextEvent() or XtAppProcessEvent() when there
are no pending input events and it would otherwise block. Multiple work procedures can be registered, and the most recently added one is
always the one that is called. However, if a work procedure itself adds another work procedure, the newly added one has lower priority
than the current one.
A work procedure returns a Boolean. If it returns True, it will automatically be unregistered and will not be called again. If it returns
False it will be called the next time the application is idle. See XtWorkProc(2) for more information.
Usage
XtAppAddWorkProc() implements a limited form of background processing. Most applications spend most of their time waiting for input; to do
useful work during this idle time, you can register a work procedure that will run when the application is idle.
A work procedure must return quickly or the application will not be able to promptly respond to user events. If a large task needs to be
done in the background, the work procedure should periodically save its state and return False. Work procedures should not be used to do
frivolous work in the background. In a multi-tasking system, an idle application should generally actually be idle, and not steal CPU time
from other processes.
A work procedure can be explicitly removed by calling XtRemoveWorkProc() with the XtWorkProcId returned by this function.
Structures
The XtWorkProcId type is defined as follows:
typedef unsigned long XtWorkProcId;
See Also
XtAppNextEvent(1), XtAppProcessEvent(1), XtRemoveWorkProc(1),
XtWorkProc(2).
Xt - Event Handling XtAppAddWorkProc()