04-06-2010
Quote:
Originally Posted by
gomes1333
Check if killall exist in the /sbin directory???
Show the entry that you have in your cron.
Hi,
killall's path is /usr/bin/killall. I have made the change in the /etc/logrotate.conf file. thank you... will check the next day if i receive same email from cron.daily.
---------- Post updated 04-06-10 at 01:16 AM ---------- Previous update was 04-05-10 at 08:54 AM ----------
hi,
I changed the killall path from /sbin/killall to /usr/bin/killall and since then i did not receive any email from cron.daily...I think its working as expected.
But as maverick said, that i must create a new file in logrotate.d dir, I think that is how ideally custom logrotate files should be created but I would like to confirm if creating an entry in logrotate.conf would be problematic.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: HarryTellegen
5 Replies
2. Shell Programming and Scripting
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)
Discussion started by: aama100
2 Replies
3. UNIX for Dummies Questions & Answers
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)
Discussion started by: nypreH
4 Replies
4. Solaris
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)
Discussion started by: ronny_nch
6 Replies
5. Shell Programming and Scripting
Hi,
Please check the below code...:wall:
if ; then
echo "/var/log/AAA/BBB/xxx_*.log /var/log/AAA/BBB/yyy_*.log {" >> /etc/logrotate.conf
echo " weekly" >> /etc/logrotate.conf
echo " rotate 10" >> /etc/logrotate.conf... (2 Replies)
Discussion started by: Dedeepthi
2 Replies
6. UNIX and Linux Applications
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)
Discussion started by: nagavenkatesh
2 Replies
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: laxyblack
1 Replies
8. Shell Programming and Scripting
Hi guys,
./test.sh &
#!/usr/bin/ksh
echo "No.Of Items :"
read count
echo "Report Time (Min):"
read time
some other command ....
exit 0;
thanks (3 Replies)
Discussion started by: asavaliya
3 Replies
9. Shell Programming and Scripting
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)
Discussion started by: brij123
2 Replies
10. Shell Programming and Scripting
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 LINUX
killall
KILLALL(1) User Commands KILLALL(1)
NAME
killall - kill processes by name
SYNOPSIS
killall [-Z,--context pattern] [-e,--exact] [-g,--process-group] [-i,--interactive] [-o,--older-than TIME] [-q,--quiet] [-r,--regexp]
[-s,--signal signal] [-u,--user user] [-v,--verbose] [-w,--wait] [-y,--younger-than TIME] [-I,--ignore-case] [-V,--version] [--] name ...
killall -l
killall -V,--version
DESCRIPTION
killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent.
Signals can be specified either by name (e.g. -HUP or -SIGHUP ) or by number (e.g. -1) or by option -s.
If the command name is not regular expression (option -r) and contains a slash (/), processes executing that particular file will be
selected for killing, independent of their name.
killall returns a zero return code if at least one process has been killed for each listed command, or no commands were listed and at least
one process matched the -u and -Z search criteria. killall returns non-zero otherwise.
A killall process never kills itself (but may kill other killall processes).
OPTIONS
-e, --exact
Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be unavailable (i.e.
it is swapped out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries
are skipped. killall prints a message for each skipped entry if -v is specified in addition to -e,
-I, --ignore-case
Do case insensitive process name match.
-g, --process-group
Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belong-
ing to the same process group were found.
-i, --interactive
Interactively ask for confirmation before killing.
-l, --list
List all known signal names.
-o, --older-than
Match only processes that are older (started before) the time specified. The time is specified as a float then a unit. The units
are s,m,h,d,w,M,y for seconds, minutes, hours, days, weeks, Months and years respectively.
-q, --quiet
Do not complain if no processes were killed.
-r, --regexp
Interpret process name pattern as an extended regular expression.
-s, --signal
Send this signal instead of SIGTERM.
-u, --user
Kill only processes the specified user owns. Command names are optional.
-v, --verbose
Report if the signal was successfully sent.
-V, --version
Display version information.
-w, --wait
Wait for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if
none are left. Note that killall may wait forever if the signal was ignored, had no effect, or if the process stays in zombie
state.
-y, --younger-than
Match only processes that are older (started after) the time specified. The time is specified as a float then a unit. The units are
s,m,h,d,w,M,y for seconds, minutes, hours, days, weeks, Months and years respectively.
-Z, --context
(SELinux Only) Specify security context: kill only processes having security context that match with given expended regular expres-
sion pattern. Must precede other arguments on the command line. Command names are optional.
FILES
/proc location of the proc file system
KNOWN BUGS
Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way.
Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user.
killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans.
If processes change their name, killall may not be able to match them correctly.
AUTHORS
Werner Almesberger <werner@almesberger.net> wrote the original version of psmisc. Since version 20 Craig Small <csmall@enc.com.au> can be
blamed.
SEE ALSO
kill(1), fuser(1), pgrep(1), pidof(1), pkill(1), ps(1), kill(2).
Linux 2011-02-22 KILLALL(1)