04-13-2017
Thanks for the response Aia.
You mean to say, there is no problem with defined function and only the double quotes are causing issue?
Even i tried without quotes, it is not working.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have gotten the script up to this point and it works fine a system but when i copy it to another unix server running solaris 9 as the original one , its gives an error './mon_fs.sh: 0: unknown test operator' .
(see script bellow)
can the Gurus see to this as i am just a beginner with... (2 Replies)
Discussion started by: ibroxy
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have the following shell script :
Nbr_BD_Link=0
Nbr_BD_Link=`
sqlplus sysadm/${PSWD}@${DB_Name} << EOF | tail -4 | head -1 2>/dev/null
set head off feedback off ;
select count(*) from dba_db_links ;
exit ;
EOF `
echo ${Nbr_BD_Link}
if ; then
... (4 Replies)
Discussion started by: big123456
4 Replies
3. Shell Programming and Scripting
hi
I get test: unknown operator status
if
then
echo "OK."
return 0
else
echo "not ok" 2>&1
exit -1
fi
I tried to change "A" with 'A' --> same error
I tried to change
if , I am getting: (3 Replies)
Discussion started by: melanie_pfefer
3 Replies
4. Shell Programming and Scripting
Hi All,
can some one figure out the syntax issue here. How to overcome this?
#!/bin/sh
$ HFR_MAIL=NO
$ PRP_MAIL=NO
$ MC_MAIL=NO
$ if && && ]; then
> echo "NO "
> else
> echo "YES"
> fi
test: unknown operator NO
$ if && && ]; then
> echo "NO"
> else
> echo "YES"
>... (4 Replies)
Discussion started by: shellscripter
4 Replies
5. Shell Programming and Scripting
Greetings, using ksh on Solaris, I am trying to identify the current version of a package installed on multiple servers using if statement in a precursor to upgrading.
I have searched the forums and have found many hits, reviewed 3 pages and have tried the different variations noted there. Also... (3 Replies)
Discussion started by: 22blaze
3 Replies
6. Shell Programming and Scripting
hi all, i am using the below command in my script
if ; then
This statement is causing the problme "ScriptName.ksh: XXX-XXX: unknown test operator"
could you please suggest me , how can i avoid these messages.
Singhal (7 Replies)
Discussion started by: singhald
7 Replies
7. Shell Programming and Scripting
Hi Guys,
I get the error while running below commands. Earlier the command used to execute, but after enclosing them in a function, the error is occuring
backupPath=`echo $folderName | sed -e 's,/vobs/dte/itgClient/client/RegressionTestLibPostOHS/,,'`
check_event=`cat... (7 Replies)
Discussion started by: ajincoep
7 Replies
8. Programming
Please excuse me if this is an easy fix, for I am new to Unix and C
'/problem1.c: line2: syntax error near unexpected token `
'/problem1.c: line2: `main()
and for one program it has
: command not found2: (above the syntax error)
As mentioned this is in C not C++, I have complied all... (3 Replies)
Discussion started by: apolo93
3 Replies
9. Shell Programming and Scripting
Hi ,
Os - Solaris
Shell - Ksh
I am getting below error in if condition
+ id
+
./om_wf_complete.sh: gid=4081(Infadmn): unknown test operator
+ exit 1
if ; then
touch /home/odwt/1.0.0/out/oworkflow.dat
chmod 777 /home/odwt/1.0.0/out/oworkflow.dat
elif ; then
touch... (8 Replies)
Discussion started by: nag_sathi
8 Replies
10. Shell Programming and Scripting
O/S solaris 9
shell ksh
if
then
chk_op="WARNING...reboot within the last 24hrs, restarted at `who -r | awk '{print $4$5"@"$6}'`" ;
else
if ;
then
last_reboot1=`who -b | awk '{print $4" "$5" "$6}'`
last_reboot2='..OK..'`uptime | awk '{print$3" "$4}'`
... (4 Replies)
Discussion started by: squrcles
4 Replies
LEARN ABOUT REDHAT
listen
LISTEN(7) SQL Commands LISTEN(7)
NAME
LISTEN - listen for a notification
SYNOPSIS
LISTEN name
INPUTS
name Name of notify condition.
OUTPUTS
LISTEN Message returned upon successful completion of registration.
WARNING: Async_Listen: We are already listening on name
If this backend is already registered for that notify condition.
DESCRIPTION
LISTEN registers the current PostgreSQL backend as a listener on the notify condition name.
Whenever the command NOTIFY name is invoked, either by this backend or another one connected to the same database, all the backends cur-
rently listening on that notify condition are notified, and each will in turn notify its connected frontend application. See the discussion
of NOTIFY for more information.
A backend can be unregistered for a given notify condition with the UNLISTEN command. Also, a backend's listen registrations are automati-
cally cleared when the backend process exits.
The method a frontend application must use to detect notify events depends on which PostgreSQL application programming interface it uses.
With the libpq library, the application issues LISTEN as an ordinary SQL command, and then must periodically call the routine PQnotifies to
find out whether any notify events have been received. Other interfaces such as libpgtcl provide higher-level methods for handling notify
events; indeed, with libpgtcl the application programmer should not even issue LISTEN or UNLISTEN directly. See the documentation for the
library you are using for more details.
NOTIFY [notify(7)] contains a more extensive discussion of the use of LISTEN and NOTIFY.
NOTES
name can be any string valid as a name; it need not correspond to the name of any actual table. If notifyname is enclosed in double-quotes,
it need not even be a syntactically valid name, but can be any string up to 63 characters long.
In some previous releases of PostgreSQL, name had to be enclosed in double-quotes when it did not correspond to any existing table name,
even if syntactically valid as a name. That is no longer required.
USAGE
Configure and execute a listen/notify sequence from psql:
LISTEN virtual;
NOTIFY virtual;
Asynchronous NOTIFY 'virtual' from backend with pid '8448' received.
COMPATIBILITY
SQL92
There is no LISTEN in SQL92.
SQL - Language Statements 2002-11-22 LISTEN(7)