Symlinks and Apache Weirdness with DA

nemonoman

Verified User
Joined
Apr 7, 2007
Messages
26
I got good advice on dealing with non-resolving symlinks here:
https://forum.directadmin.com/showthread.php?t=57644
and things SEEMED to work ok with harden_symlinks_patch=no.

What I discovered was that they would also FAIL to resolve, depending on how apache was started.

I manually started apache in the shell with apachectl: apachectl start, apachectl restart, apachectl graceful.

But it appears that DA restarts apache with another command. I'm guessing something like 'service httpd restart'.

So on a server reboot, with the 'service httpd restart' command, SYMLINKS AGAIN FAILED TO RESOLVE.

Also note that the httpd start, stop. restart, reload buttons on the DA SERVICE MONITOR page use the httpd command.

So if you stop apache, and the restart with apachectl
1. Symlinks resolve
2. HTTPD Command buttons on the DA SERVICE MONITOR page DO NOT WORK.

ALSO, it appears that embedded DA apache commands will not function compatibly with apachectl -- but I haven't found a way to test this.
But in the shell, issuing a 'service httpd stop' or reload command FAILS if the apachectl has started apache

I'm out of my depth here. Apache now recommends apachectl commands, not service httpd. Also they've now changed the format of those commands -- used to be apachectl -K start, now no -K, just apachectl start.
 
Last edited:
Back
Top