03-29-2002
Hi,
Thanks for the inputs.. Currently the server is up and running. I don't have clearance for a down. Of course I will come back with further details after my next shutdown..
Thanks again,
5 More Discussions You Might Find Interesting
1. IP Networking
Why would I get TIME_WAIT when i netstat a port?? What would be some scenarios of this situation?? (1 Reply)
Discussion started by: eloquent99
1 Replies
2. UNIX for Advanced & Expert Users
What is the maximum number of TCP ports that can be consumed at any one time? How can I determine what the number is or increase it?
I was under the impression that with our system (UnixWare 7.1.1) 1024 was the maximum under our current Kernel tuning parms, but I think that is really just... (4 Replies)
Discussion started by: dlkox
4 Replies
3. UNIX for Advanced & Expert Users
in TCP, is TIME_WAIT state really essential..!!! (3 Replies)
Discussion started by: sasikanth
3 Replies
4. Red Hat
Hi,
I want to kill TCP connections which have status as TIME_WAIT & no PID
(as per the output of the "netstat - p" command).
Is there any command/utility available to kill connections to a specific port or IP address.
The problem is that these connections don't have process ID (see... (4 Replies)
Discussion started by: Davinder31may
4 Replies
5. UNIX for Dummies Questions & Answers
Server has more TIME_WAIT connections in Apache(port 80) Hi,
My webserver has 16GB of RAM and CentOS 5.5, Apache 2.2.3, It's shared webserver used of for webhosting. I have optmized the server as :
<IfModule prefork.c>... (4 Replies)
Discussion started by: chandranjoy
4 Replies
LEARN ABOUT ULTRIX
rrpc_shutdown
rrpc_shutdown(3ncs) rrpc_shutdown(3ncs)
Name
rrpc_shutdown - shut down a server
Syntax
#include <idl/c/rrpc.h>
void rrpc_$shutdown(handle, status)
handle_t handle;
status_$t *status;
Arguments
handle A remote procedure call (RPC) handle.
status The completion status. If the completion status returned in is equal to status_$ok , then the routine that supplied it was success-
ful.
Description
The routine shuts down a server, if the server allows it. A server can use the routine to allow or disallow remote shutdown.
Diagnostics
This section lists status codes for errors returned by this routine in
rrpc_$shutdown_not_allowd
You send an request to a server that has not issued an call.
Restrictions
On the client side, because of the way the calls are defined and implemented in the run-time library you must explicitly call into the
entry point vector table for the interface to send an request across the network. The following is an example of a call that works as
desired:
(*rrpc_$client_epv.rrpc_$shutdown)(handle, &status);
The server side stub routine calls the entry point on behalf of the client. The results of the call are then passed back to the client.
Before making the shutdown call, the server must have previously executed the following call:
rpc_$allow_remote_shutdown((unsigned long) TRUE,NULL,&status);
If the server has not allowed remote shutdown, the call returns an status code.
Files
See Also
intro(3ncs), rpc_allow_remote_shutdown(3ncs), rpc_shutdown(3ncs)
rrpc_shutdown(3ncs)