09-04-2010
Thank you for your efforts, it's getting killed , is there no way of keeping a process alive that was started from php ? The process dies on reload/stop/etc...
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I need a shell script to kill apache and restart it, in case the number of processes keeps growing. The logic is like the below, but I don't know how to get the number and neither the syntax. Could somebody kindly help?
if no_of_processes (ps ax ¦ grep httpd) > 200
then
killall httpd... (14 Replies)
Discussion started by: _joshua_
14 Replies
2. SuSE
I have a process that gradually eats up memory, it's currently at 80.2% and slowing down the linux server
> ps aux | grep SNMPME
root 3129 0.0 80.2 3591752 2480700 ? Sl Feb13 5:04 /opt/nampe/lib/snmpme/SNMPME config/startup.xml
Is there a command I can execute to restart this... (3 Replies)
Discussion started by: brendan76
3 Replies
3. Web Development
I need to restart my apache, but apachectl configtest tells me that
Syntax error on line 208 of /etc/httpd/conf/httpd.conf:
Cannot load /usr/local/apache/libexec/libphp4.so into server: /usr/local/apache/libexec/libphp4.so: undefined symbol: ap_signal
I've tried rebuilding php, I'm not... (2 Replies)
Discussion started by: tatebn
2 Replies
4. Shell Programming and Scripting
I have posted this on the Web subforum but it seems that nobody knows to do this, maybe someone has a solution here. Thank you
I have a PHP application that starts a couple of processes on the server...the problem is that if I restart apache those running apps will die.
How can I start them... (1 Reply)
Discussion started by: valiadi
1 Replies
5. Shell Programming and Scripting
Hi,
I have a problem with running out of memory in my Ubuntu web server (4GB RAM) because many people try to access my server.
I used to restart manually my apache server to clear out the memory & swap.
Can anyone tell me how to write bash script that can automatically restart apache when... (2 Replies)
Discussion started by: nica
2 Replies
6. Shell Programming and Scripting
Hi All
I have written below basic restart script but it is giving me the following error -
error - syntax error at line 40 : `else' is not matched .
below is the script can someone assist me what i am doing wrong -
#!/bin/ksh
cd bin
. ./set_sysm
sleep 60
./swstop -f 0
... (1 Reply)
Discussion started by: honey26
1 Replies
7. Red Hat
Have no idea on what the below error message is:
Process not running: /opt/java15/jdk/bin/java -classpath /opt/apache/apache-ant-1.7.0-mod/lib/ant-launcher.jar org.apache.tools.ant.launch.Launcher -buildfile build.xml dist.
Any help? (3 Replies)
Discussion started by: gull05
3 Replies
8. Red Hat
Hello,
I'l like to create a script that restart a service (/etc/init.d/httpd restart) and also check if after restart the service is actually running. Sometimes it happen that at the first try the service fails to restart.
Thanks (2 Replies)
Discussion started by: bazzola
2 Replies
9. Red Hat
Hi
Im apache service restart
Error
$ service httpd reload
Reloading httpd:
service httpd reload
Reloading httpd:
service httpd start
Starting httpd: (98)Address already in use: make_sock: could not bind to address :80
(98)Address already in... (1 Reply)
Discussion started by: mnnn
1 Replies
10. Red Hat
When I update the server with new SSL certificates, and restart httpd, I get errors :
# service httpd restart
Stopping httpd:
rm: cannot remove `/usr/local/apache2/bin/httpd/logs/httpd.pid': Not a directory
Starting httpd: ... (0 Replies)
Discussion started by: anaigini45
0 Replies
LEARN ABOUT OPENDARWIN
systemd.kill
SYSTEMD.KILL(5) systemd.kill SYSTEMD.KILL(5)
NAME
systemd.kill - Process killing procedure configuration
SYNOPSIS
service.service, socket.socket, mount.mount, swap.swap, scope.scope
DESCRIPTION
Unit configuration files for services, sockets, mount points, swap devices and scopes share a subset of configuration options which define
the killing procedure of processes belonging to the unit.
This man page lists the configuration options shared by these five unit types. See systemd.unit(5) for the common options shared by all
unit configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5) and systemd.scope(5) for more
information on the configuration file options specific to each unit type.
The kill procedure configuration options are configured in the [Service], [Socket], [Mount] or [Swap] section, depending on the unit type.
OPTIONS
KillMode=
Specifies how processes of this unit shall be killed. One of control-group, process, mixed, none.
If set to control-group, all remaining processes in the control group of this unit will be killed 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 mixed,
the SIGTERM signal (see below) is sent to the main process while the subsequent SIGKILL signal (see below) is sent to all remaining
processes of the unit's control group. 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.
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.
Defaults to control-group.
KillSignal=
Specifies which signal to use when killing a service. This controls the signal that is sent as first step of shutting down a unit (see
above), and is usually followed by SIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to SIGTERM.
Note that, right after sending the signal specified in this setting, systemd will always send SIGCONT, to ensure that even suspended
tasks can be terminated cleanly.
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(1), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
systemd.exec(5), systemd.directives(7), kill(2), signal(7)
systemd 237 SYSTEMD.KILL(5)