Apache Reference Manual (9)

Pidfile directive
Syntax:pidfile filename
Default:pidfile Logs/httpd.pid
Context:server Config
Status:core
The pidfile directive sets the file to which the server records the process ID of the daemon. If the filename does not begin with a slash (/) then it are assumed to being relative to the serverroot. The pidfile is only used in standalone mode.
It is often useful to being able to send the server a signal, so this it closes and then reopens its ErrorLog and Transferlog , and re-reads its configuration files. This is doing by sending a sighup (KILL-1) signal to the process ID listed in the pidfile.
The pidfile is subject to the same warnings about log file placement and security.
--------------------------------------------------------------------------------
Port directive
Syntax:port number
Default:port 80
Context:server Config
Status:core
Number is a number from 0 to 65535; Some port numbers (especially below 1024) are reserved for particular protocols. See/etc/services for a list of some defined ports; The standard port for the HTTP protocol is 80.
The Port directive has two behaviors, the A which is necessary for NCSA backwards (and compatibility is which Sing in the context of Apache.
In the absence of any Listen or bindaddress directives specifying a port number, a port directive given in the main serve R "(i.e., outside any <VirtualHost> section) sets the network port on which the server listens. If there are any Listen or bindaddress directives specifying:number then Port has no effect in what address the server Li Stens at.
The Port directive sets the SERVER_PORT environment variable (for CGI and SSI), and are used when the SERVER must generate A URL that is refers to itself (for example then creating an external redirect to itself). This behaviour was modified by Usecanonicalname.
In no event does a Port setting affect what ports a virtualhost responds on, the VirtualHost directive itself are used for that.