12-24-2019
Thank you Neo,
We will swap to paid gmail service.
Kind regards
Boris
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How can I determine if the data collection rate is 1 Hz on Solaris? (0 Replies)
Discussion started by: laila63
0 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am trying to write a script to Count Files in a directory located on a remote server and send an email Notification if it exceeds a limit. The code given below doesnot check the condition and sends the mail everytime irrespective of the condition. I have put this script in the cron. Can... (10 Replies)
Discussion started by: amitsayshii
10 Replies
3. UNIX for Dummies Questions & Answers
Would appreciate some help, system was displaying an error regarding the kernal when a "sar" was run, after a reboot we get "WARNING user login limit exceeded by 1 user". We have plenty of licences. any ideas? (1 Reply)
Discussion started by: nchrocc
1 Replies
4. UNIX and Linux Applications
Does anyone know what's Sendmail outgoing email rate? e.g. 1000 outgoing email per minutes. If so, can we modify it?
Thanks.
:) (1 Reply)
Discussion started by: sunmagic2003
1 Replies
5. Shell Programming and Scripting
Hi,
I need help in writing unix script for checking space of some directories on the system and also send an email when it reaches the threshold limit.
I have written the followng code;
#!/bin/ksh
ADMIN="me@somewhere.com"
# set alert level 80% is default
THRESHOLD=80
df | grep -E... (5 Replies)
Discussion started by: jmathew99
5 Replies
6. AIX
Hello,
How can i tell ifthe ratio between fr and sr is ok?
is fr/sr ratio of 0.9 acceptable?
thanks. (1 Reply)
Discussion started by: LiorAmitai
1 Replies
7. Solaris
Hi all, I'm using to Solaris machine. When I run a simple script this messenger come out:"limit: stacksize: Can't remove limit". Any one know the way to resolve this problem without reboot the machine?
Thanks in advance. (3 Replies)
Discussion started by: Diabolist9
3 Replies
8. UNIX and Linux Applications
Just had a migration from Autosys 4.5 to R11.3.
After the migration to R11.3, Autosys jobs have been failing when the log file reaches a size of 800 MB.
This did not happen before the migration, when Autosys 4.5 was used.
Is there a way to configure the file size limit/cap in Autosys... (1 Reply)
Discussion started by: kimo222
1 Replies
9. Shell Programming and Scripting
Deal all,
I have a directory called
I want to know how many MBs are transferred to it every 2 hours.
How can I do this?
Any ideas?
I have a simple idea but I can't translate it into shell script, the idea is:
1- get the size of the folder now, using
2- then get the size of the... (4 Replies)
Discussion started by: Mohannad
4 Replies
10. UNIX for Advanced & Expert Users
I have D-Link Router DSL-2730U that support busybox OS and iptables version 1.4.0
I managed successfully to block the host for being connect to the internet using the following command
block by ip address
iptables -I FORWARD -d 192.168.1.6 -j DROP
Or By mac source
iptables -I... (0 Replies)
Discussion started by: iLinux85
0 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)