Hmm is this file going to be running all the time, every 15 seconds? Maybe you should set up a cron job.
If not, then try this:
Code:
changed="NO"
while [ $changed == "NO" ]; then
do
echo $FIELDS > new_alert.tmp
diff new_alert.tmp last_alert.tmp
if [ $? -eq 0 ]; then
echo No new alert messsages `date`
sleep 15
changed="YES"
else
continue
fi
done
Hello,
I host a couple of Call of Duty gameing servers. There are some hackers who love the crash them. When they crash them it simply causes a segmentaion fault and kills the PID. I was wondering it you could help me write a script to simply restart the program after it has been crashed. The... (9 Replies)
:confused: Everytime our UNIXWARE 7 Server is restarted we also have to restart the spooler. If the spooler is not restarted, print jobs get stuck in the queu. Once restarted by using the following command lpstop and lpstart everything works fine.
Does anyone have any ideas what could be causing... (0 Replies)
Hi!
My unix os version is OSF1 CP1 V4.0 878 alpha.
It startup normally but it restarts within 5 sec.
I would like to know how to solve .
Please reply to me.
Thanks .
akzin (2 Replies)
HI
We have Compaq ML350 G2 server with UNIX SCO 5.0.5 OS , can anyone help us to get rid about the system restarting problem by itself every after2-24 hours with following error " MEMORY CORE DUMP " .
Waiting for your ASAP help.
Thank You . (4 Replies)
Hello people,
My solaris server is rebooting, not sure how!!! Which log should I look in to? I checked /var/adm/messages and dmesg also. How do I check older dmesg logs? I checked lastlog and also ran the last command. Nothing useful pointing to why server rebooted.
Also when server reboots I... (4 Replies)
Hi All,
I can seem to find the syslog daemon in the /etc/init.d/ dir. i have made change to the syslog.conf i need to restart the daemon. am using solaris 10. i have no problem on version 9
Anyone with a template i can use for log review for auditing purposes. (1 Reply)
Hi,
I use gfortran to run the code. Some times I need to stop the program
and restart it. On restarting I need to run the program from the beginning.
Is there any script or option available to restart the program from where
it stopped? This script/option will be immensely useful for... (2 Replies)
Hi,
How is it possible to restart only your process. I can get the process killed but I am not able to start it.
For eg : i first did this ps -ef|grep _out --displays all the process with _out in the name
then I killed kill -15 36044 -- process id.
Now how can i start the same... (1 Reply)
Hi friends,
I have one unix command which is used to check the network status manually.
followig is the command
check_Network this command give follwoing status
Network 1 is ok
Network 2 is ok
network 3 is ok
network 4 is ok
.
.
.
.
Network 10 is... (8 Replies)
Environment: SUSE 10.3
I made a configuration change in '/etc/syslog-ng/syslog-ng.conf' file in a server.
An article found on web says "After the change '/etc/init.d/syslog-ng' should be restarted". But there is no 'syslog-ng' in /etc/init.d directory.
What is syslog-ng or a... (4 Replies)
Discussion started by: JDBA
4 Replies
LEARN ABOUT PLAN9
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.10 1 Mar 1994 queuedefs(4)
07-25-2003
