Hi all,
By running a (command) script I'm getting the following
error: .: /usr/bin/test: cannot execute binary file
This is the command:
$ . test
The script (test) is very simple
sqlplus user/password @1.sql
sqlplus user/password @2.sql
Can enyone tell me what the problem is. (5 Replies)
Hi all,
I have created a script file .sh and had some allias commands, local variable, some grep features, and listing files/directories, and it worked correctly and I got the outputs I am looking for after I run the script . However, some of the grep commands and some other functions did not... (2 Replies)
Hi all,
I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like:
ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory
/tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
Hi All,
Need your guuys help here.
#!/bin/bash
{
echo "POLICY LIST"
echo "===================================="
bppllist
echo " "
echo "POLICY DETAILS"
echo "===================================="
for type in daily weekly monthly quarterly
echo... (6 Replies)
hi All,
we have a script to remove the files from particular path,when we tryingto run manually the script went to success and removed the files but the same script which is running by other team it got failed and giving the error "2 (RC)2 "..what is the cause of the failure..and we passing the... (2 Replies)
Hi,
My requirements are
I wanted to move my daily logs to /appl/logs/old folder
Archive and compress all 10 days older log files under /appl/logs/old in YYYYMMDD format file
To remove any 60 days older log files from /appl/logs/old
I tried this scenario with logrotate utility
... (1 Reply)
Hi I was trying to fetch data from database. But the number of rows exported were huge so i got the error. Experts please advice. Thanks a lot for your supprt. #: ./script.sh ./script.sh: xmalloc: subst.c:3076: cannot allocate 1401346369 bytes (0 bytes allocated) (2 Replies)
Hi,
I have the the below script
more runcda.sh
if *\).*/\1/p' $1_dr) ]; then
echo "ParallelGCThreads Found with Value"
else
echo "ParallelGCThreads Not Found - Add !!"
fi
$ ./runcda.sh output.log
./runcda.sh: test: argument expected
ParallelGCThreads Not Found - Add !!
Why am i... (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT OPENDARWIN
killall
KILLALL(1) BSD General Commands Manual KILLALL(1)NAME
killall -- kill processes by name
SYNOPSIS
killall [-d | -v] [-h | -?] [-help] [-l] [-m] [-s] [-u user] [-t tty] [-c procname] [-SIGNAL] [procname ...]
DESCRIPTION
Killall kills processes selected by name, as opposed to the selection by pid as done by kill(1). By default, it will send a TERM signal to
all processes with a real UID identical to the caller of killall that match the name procname. The super-user is allowed to kill any
process.
The options are as follows:
-d | -v Be more verbose about what will be done. For a single -d option, a list of the processes that will be sent the signal will
be printed, or a message indicating that no matching processes have been found.
-h | -?
-help Give a help on the command usage and exit.
-l List the names of the available signals and exit, like in kill(1).
-m Match the argument procname as a (case insensitive) regular expression against the names of processes found. CAUTION!
This is dangerous, a single dot will match any process running under the real UID of the caller.
-s Show only what would be done, but do not send any signal.
-SIGNAL Send a different signal instead of the default TERM. The signal may be specified either as a name (with or without a lead-
ing SIG), or numerically.
-u user Limit potentially matching processes to those belonging to the specified user.
-t tty Limit potentially matching processes to those running on the specified tty.
-c procname
When used with the -u or -t flags, limit potentially matching processes to those matching the specified progname.
ALL PROCESSES
Sending a signal to all processes with uid XYZ is already supported by kill(1). So use kill(1) for this job (e.g. $ kill -TERM -1 or as root
$ echo kill -TERM -1 | su -m <user>)
DIAGNOSTICS
The killall command will respond with a short usage message and exit with a status of 2 in case of a command error. A status of 1 will be
returned if either no matching process has been found or not all processes have been signalled successfully. Otherwise, a status of 0 will
be returned.
Diagnostic messages will only be printed if requested by -d options.
SEE ALSO kill(1), sysctl(3)HISTORY
The killall command appeared in FreeBSD 2.1. It has been modeled after the killall command as available on other platforms.
AUTHORS
The killall program was originally written in Perl and was contributed by Wolfram Schneider, this manual page has been written by Jorg
Wunsch. The current version of killall was rewritten in C by Peter Wemm using sysctl(3).
BSD June 25, 1995 BSD