03-06-2006
By default, the at command uses the Bourne shell. What you're seeing with "Job 2 will be executed using /bin/sh" message is a warning. You can call at with a -k option to tell it to use the Korn shell.
As far as SIGHUP vs SIGINT, it depends on the process you're trying to interrupt. Many processes handle SIGHUPs gracefully -- for example syslogd will reread its configuration file. Other process, if not coded specifically for processing SIGHUP will terminate. SIGINTs, on the other hand, are almost universally "process-terminating". Experiment.
I'm glad I could be of help.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello All,
I would like to know if it is possible to launch a job in background for infinite time.
example:
myScript.ksh
while true
do
( echo "(`date`)"; top -U user | grep 'Memory:' ) >> log &
sleep 1800
done
and when i do... (5 Replies)
Discussion started by: midhun_u
5 Replies
2. Shell Programming and Scripting
Hi,
I would like to invoke a shell script with period (in seconds) as a parameter and want it to run olny for that period. The script should come out after that period even some work is going inside the script.
Regards (2 Replies)
Discussion started by: sanjay1979
2 Replies
3. Shell Programming and Scripting
Hi all,
now i am writting one bash script. in that my requirement is
i need to create one directory and that the directory details to be stored in one file Ex. date/time and all in one file.
after that i need to delete the folder automatically exactly after 3months.
between these time... (5 Replies)
Discussion started by: anishkumarv
5 Replies
4. Shell Programming and Scripting
Hey guys, I'm fairly new at unix shell scripting and I have a quick question.
Quick overview I devolped a script where I generate a file ..and I want to grep any time greater than 30 minutes.
What i do is runa command to generates the below and puts it into a file:
I run
./ggsci << endit... (4 Replies)
Discussion started by: nomiezvr4
4 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Below is my OS details.
uname -an
SunOS mymachine 5.10 Generic_144488-07 sun4v sparc SUNW,SPARC-Enterprise-T5220
I need to know when was my Apache server last started. Whats is the best and most reliable way to find out not just for Apache but for any PID per say?
I am... (16 Replies)
Discussion started by: mohtashims
16 Replies
6. HP-UX
Hi,
Can some one please tell me how do I generate a report of the Memory Consumption over a time period:
HP-UX B.11.31 U ia64 0440531406 unlimited-user license
I normally use glance to monitor memory in run time.
Note: I do not have root privileges.
Thanks
Danish
... (5 Replies)
Discussion started by: danish0909
5 Replies
7. Shell Programming and Scripting
I used this script to get the connection to a domain in two specific minutes. I need to extend to give result over a range of minutes.
The below gives total number of connections in the minutes 00:40 and 01:13 on 22nd March.
egrep "22/Mar/2013:00:40|22/Mar/2013:01:13"... (1 Reply)
Discussion started by: anil510
1 Replies
8. Shell Programming and Scripting
All,
How to get the list of files through a unix command which exists / created / updated between 8 PM to 11:59 PM from a particular location.
Regards
Oracle User (3 Replies)
Discussion started by: Oracle_User
3 Replies
9. Shell Programming and Scripting
Hello All,
As I stated in subject, I need a command to terminate my tcpdump command in a certain time period. (using HP-UX)
I am using below one to terminate when number of captured packages reach 3 limit.
But what if there will no packet come in 5 min for instance?
Please help me to find a... (2 Replies)
Discussion started by: mrcrowley
2 Replies
10. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
LEARN ABOUT CENTOS
systemd.kill
SYSTEMD.KILL(5) systemd.kill SYSTEMD.KILL(5)
NAME
systemd.kill - Kill environment configuration
SYNOPSIS
service.service, socket.socket, mount.mount, swap.swap
DESCRIPTION
Unit configuration files for services, sockets, mount points and swap devices share a subset of configuration options which define the
process killing parameters of spawned processes.
This man page lists the configuration options shared by these four unit types. See systemd.unit(5) for the common options of all unit
configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5) and systemd.mount(5) for more information on the specific
unit configuration files. The execution specific configuration options are configured in the [Service], [Socket], [Mount], or [Swap]
section, depending on the unit type.
OPTIONS
KillMode=
Specifies how processes of this service shall be killed. One of control-group, process, none.
If set to control-group, all remaining processes in the control group of this unit will be terminated on unit stop (for services: after
the stop command is executed, as configured with ExecStop=). If set to process, only the main process itself is killed. If set to none,
no process is killed. In this case only the stop command will be executed on unit stop, but no process be killed otherwise. Processes
remaining alive after stop are left in their control group and the control group continues to exist after stop unless it is empty.
Defaults to control-group.
Processes will first be terminated via SIGTERM (unless the signal to send is changed via KillSignal=). Optionally, this is immediately
followed by a SIGHUP (if enabled with SendSIGHUP=). If then, after a delay (configured via the TimeoutStopSec= option), processes still
remain, the termination request is repeated with the SIGKILL signal (unless this is disabled via the SendSIGKILL= option). See kill(2)
for more information.
KillSignal=
Specifies which signal to use when killing a service. Defaults to SIGTERM.
SendSIGHUP=
Specifies whether to send SIGHUP to remaining processes immediately after sending the signal configured with KillSignal=. This is
useful to indicate to shells and shell-like programs that their connection has been severed. Takes a boolean value. Defaults to "no".
SendSIGKILL=
Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the
service around. Takes a boolean value. Defaults to "yes".
SEE ALSO
systemd(1), systemctl(8), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
systemd.exec(5), systemd.directives(7)
systemd 208 SYSTEMD.KILL(5)