I tried killing one of the processes listed from the netstat command like this :
The error is as shown.
How else can I clear all these hogging processes?
Also are these processes the cause of port 80 being blocked? Clearing them will resolve this problem and allow me to start apache without any problem?
I am not by any means a UNIX guru if you can't already tell by the question I'm about to ask.
How do I launch Apache web server on my SOlaris 8 server without rebooting it?
Any help would be much appreciated!!!
-Thanks (5 Replies)
I successfully installed Apache, but When I tried to start it I experienced problems.
After installing and compiling, I typed the PREFIX "usr/local/
apache/bin/apachect1 start." The output was path not found.
After checking the apachect1 file using vi, I found the file empty.
There was no... (4 Replies)
Hi All,
I am trying to start the docbase but i am getting the following error-:
$ ./dm_start_ncsglorbiprd00
interpreter "/bin/sh" not found
file link resolves to "/usr/bin/sh"
sh: ./dm_start_ncsglorbiprd00: not found.
Can anyone please help me in this regard.
Thanks in advance
... (0 Replies)
I've been working on a project to replace one of the my group's primary NIS servers. It also runs mysql and apache, as it is the host for the our team's hardware tracking database and website. Its running apache 1.3, and for some odd reason, I can't get apache to start on system boot. The... (1 Reply)
I just installed Apache 2.2.6 & when trying to start it i got this:
Invalid command 'SSLProtocol', perhaps misspelled or defined by a module not included in the server configuration
Any help? (3 Replies)
Hi,
I just installed Apache 2.0.54 and when I try and start httpd I get
mohit@mohit-desktop:/sw/pkg/apache/bin$ ./httpd -k start
httpd: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
(13): make_sock: could not bind to address :80
no listening... (1 Reply)
Sir,
I have installed an Apache server in Fedora 9 (packages)
and when i go to etc folder and try the command
httpd -k start
it says command not found....can any one help me out!!!
---------- Post updated at 12:02 PM ---------- Previous update was at 11:46 AM ----------
When i... (4 Replies)
Hello,
I am facing an issue while starting the apache server after compiling php and curl.
Below are the versions i am using.
php-5.2.17
httpd-2.2.17
curl-7.16.0
CentOS5.5x64
Compiling above packages without curl working very fine but when trying to compile php with curl below error is... (1 Reply)
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
LEARN ABOUT BSD
kill
KILL(1) General Commands Manual KILL(1)NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO csh(1), ps(1), kill(2), sigvec(2)BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)