The correct way to start the apache server is to use the apachectl command.
You can also check your configuration files.
A common error is probably this one :
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
This is caused by one or more processes running on the 443 (secure socket) port. You can get all the process ID’s that are running on this port with the command fuser or a more classical "ps auxww" with a less readable format.
nicolas@grimm:~$ fuser 443/tcp 443/tcp: 7977 6815 9819 35217 # Now you just have to do a **kill** on those process. nicolas@grimm:~$ kill -9 7977 6815 9819 35217 # Or in a single line: nicolas@grimm:~$ kill -9 $(fuse 443/tcp 2>/dev/null)
Other typical error would be those following :
(28)No space left on device: Couldn&#8217;t create accept lock
(28)No space left on device: mod\_rewrite: could not create rewrite\_log_lock Configuration Failed
You may have some troubles while using a network share on windows because of access restriction errors. Don’t panic, just use CACLS on windows XP.
If you have change your rc file of your favorites bash (like ~/.bashrc in "bash"), you can reload it easly by using "exec". Just type the following command line :
nicolas@grimm:~/$ exec bash
Exec replace the current process image with a new process image . So, now if you add aliases in your ~/.bash_aliases, just use "exec bash" and you could use your aliases in your current terminal. This way is also useful if you want to change your current shell without spawn another process. I mean, if you have a box where your login shell is a classical "sh", you can also do an "exec bash", that will replace your current shell by a friendly one.
Update: You can also use
exec $SHELL which would be compatible with all your shells, though be aware your active shell may not be the same.
Many DOS commands in the 32-bit versions of Windows are similar but support different parameters, different commands or using different registry key name. Thus, if you wish to write a batch file that can run on different types of machines, it may prove beneficial to determine the version of Windows on which the batch file is running. This way the batch file can execute commands appropriate to the operating system.
In our list of "CLI workaround for Windows XP", a missing command is SLEEP or WAIT. For fixing this I suggest you two solution, first is simply a batch workaround using PING command, the second solution use the Windows Server 2003 Ressource Kit tools.
With PING you can produce a fixed delay by testing the loopback address. This can be really usefull if you don’t want (or if you can’t) install extra software.
# Doing an approximative pause of 60 seconds
PING -n 61 127.0.0.1>nul
Second way is to install the [Windows Server 2003 Resource Kit tools] from microsoft.com. You will get a SLEEP.exe that will do all the requested stuff.
# Doing a pause of 60 seconds