11-12-2010
Well the purpose is not to echo after sudoing into the vserver. The code inside there is proprietary and so I did not want to post it here
Secondly,
If I sudo on command prompt it works fine. Prompts me for a password and I enter the password an can enter the vserver correctly!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
set -A arr a1 a2 a3 a4
# START
ssh -xq $Server1 -l $Username /usr/bin/ksh <<-EOS
integer j=0
for loop in ${arr}
do
printf "array - ${arr}\n"
(( j = j + 1 ))
j=`expr j+1`
done
EOS
# END
=========
this is not giving me correct output.
I... (5 Replies)
Discussion started by: reldb
5 Replies
2. Shell Programming and Scripting
I tried doing
ftp myhost <<HERE
username
password
quit
HERE
but it doesnt work. Why?
When I do ftp host, I always get prompted for username, and once I type that in I get prompted for password. But when I try doing it from here document it freezes. (2 Replies)
Discussion started by: JamesByars
2 Replies
3. UNIX for Advanced & Expert Users
now running mac os x 10.53 and sudo chmod comes back with : operation not permitted.
sample file:
-rwxr-xr-x+ 1 1000 com.apple.monitor_all_services 276592 Jun 8 2007 342345.tif
i am running as root. (1 Reply)
Discussion started by: Movomito
1 Replies
4. Shell Programming and Scripting
Hi All,
i have a cron entry like
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /amex/sssmonitor/dss_chk.ksh
and the script is like
#!/bin/ksh
file=`uname -n`
> /sunmast/projects/oasis/COREDEV/Dss$file.log
> /tmp/output_sss
today=`date`
varb=`ps -ef | grep... (5 Replies)
Discussion started by: usha rao
5 Replies
5. Shell Programming and Scripting
When I use sudo with ulimit there is an error but if I use ulimit without sudo there is no error.
In bash:
user1@debian:~$ sudo -u user2 -H ulimit -S -c unlimited
sudo: ulimit: command not found
user1@debian:~$
user1@debian:/home/user1$ ulimit -S -c unlimited
user1@debian:/home/user1$... (3 Replies)
Discussion started by: cyler
3 Replies
6. UNIX for Dummies Questions & Answers
Have a sudo statement inside of a here document. It prompts me for a password, but doesnt wait for me to enter my password. Is there a way I can use the command without sudo or anyway that I can enter the password correctly?
Eg :
while read remotehost
do
ssh -t $2@$remotehost ... (0 Replies)
Discussion started by: mnanavati
0 Replies
7. Shell Programming and Scripting
Can we use a here document inside a here document?
Something like this
ssh user@remotehost << REMOTE
sudo vserver vsernamename enter << VSERVER
perform actions on vserver.
VSERVER
REMOTE (6 Replies)
Discussion started by: mnanavati
6 Replies
8. Red Hat
This is the first time for using sudo for me.
# visudo
## Allows people in group admin to run all commands
%admin ALL=(ALL) ALL
# groupadd admin
# useradd temp
# usermod -a -G admin temp
# id temp
uid=506(temp) gid=506(temp) groups=506(temp),507(admin)
#
#sudo... (5 Replies)
Discussion started by: getrue
5 Replies
9. Solaris
Hi All, im a bit new to Solaris 10 iv been working on Redhat and cant seem to get the sudo working on Solaris 10:D
Iv installed the below packages via pkgadd command:
gcc-4.7.2-sol10-x86-local
libiconv-1.14-sol10-x86-local
libintl-3.4.0-sol10-x86-local
sudo-1.8.13-sol10-x86-local
... (1 Reply)
Discussion started by: SolarisRSA
1 Replies
10. UNIX for Beginners Questions & Answers
H Forum,
I was thankful in getting help from this post that allowed me to connect to multiple severs at once using here documents to gather data into variables. But I've discovered that the same bash command that works on my RHEL 7 servers do not work on RHEL 6? What's strange about my... (4 Replies)
Discussion started by: greavette
4 Replies
LEARN ABOUT SUSE
droplang
DROPLANG(1) PostgreSQL Client Applications DROPLANG(1)
NAME
droplang - remove a PostgreSQL procedural language
SYNOPSIS
droplang [ connection-option... ] langname [ dbname ]
droplang [ connection-option... ] [ --list ] [ -l ] dbname
DESCRIPTION
droplang is a utility for removing an existing programming language from a PostgreSQL database. droplang can drop any procedural language,
even those not supplied by the PostgreSQL distribution.
Although backend programming languages can be removed directly using several SQL commands, it is recommended to use droplang because it
performs a number of checks and is much easier to use. See DROP LANGUAGE [drop_language(7)] for more.
OPTIONS
droplang accepts the following command line arguments:
langname
Specifies the name of the backend programming language to be removed.
[-d] dbname
[--dbname] dbname
Specifies from which database the language should be removed. The default is to use the database with the same name as the current
system user.
-e
--echo Display SQL commands as they are executed.
-l
--list Show a list of already installed languages in the target database.
droplang also accepts the following command line arguments for connection parameters:
-h host
--host host
Specifies the host name of the machine on which the server is running. If host begins with a slash, it is used as the directory for
the Unix domain socket.
-p port
--port port
Specifies the Internet TCP/IP port or local Unix domain socket file extension on which the server is listening for connections.
-U username
--username username
User name to connect as.
-w
--no-password
Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as
a .pgpass file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to
enter a password.
-W
--password
Force droplang to prompt for a password before connecting to a database.
This option is never essential, since droplang will automatically prompt for a password if the server demands password authentica-
tion. However, droplang will waste a connection attempt finding out that the server wants a password. In some cases it is worth
typing -W to avoid the extra connection attempt.
ENVIRONMENT
PGDATABASE
PGHOST
PGPORT
PGUSER Default connection parameters
This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see in the documentation).
DIAGNOSTICS
Most error messages are self-explanatory. If not, run droplang with the --echo option and see under the respective SQL command for details.
Also, any default connection settings and environment variables used by the libpq front-end library will apply.
NOTES
Use createlang(1) to add a language.
EXAMPLES
To remove the language pltcl:
$ droplang pltcl dbname
SEE ALSO
createlang(1), DROP LANGUAGE [drop_language(7)]
Application 2010-05-14 DROPLANG(1)