In my system now /var/run points to /run, where there isn't any apache2 directory, could this be the same problem? If yes, is it safe to create the apache2 folder inside /run as suggested in the first link?

I'm guessing this thread will move to the Software forum as I suspect it is not a common upgrade problem with apache2 (I think I know of some systems which will have d-u'd to /run versions fine without this problem), but I won't move it myself anyway until that is confirmed.

aptosid.com has been using /run/ with according sysvinit/ initramfs-tools for about a month, therefore this certainly isn't a general issue. That said, dæmon initscripts have always been required to create /var/run/<d>/ subdirectories while starting, as RAMRUN has been a valid configuration option for years, so any failure resulting from this would have been a RC bug already.

and then just use it's initscript instead to start|stop it when I want:

Code:

service apache2 start

or

Code:

/etc/init.d/apache2 start

Are you just calling apachectl without any arguments or with arguments but not start as the first one?

Code:

apachectl start

should have made /var/run/apache2 but I think none of the other ways of calling apachectl will do it (apart from adding options after start).

dario

Post subject:Posted: 17.05.2011, 14:35

Joined: 2010-11-27
Posts: 63

Status: Offline

I used to start it using:

Code:

apachectl graceful

now i tried apachectl start and it works, i'm very sorry (need an auto-facepalm smiley) for the stupid question, i didn't try this but only "apachectl restart", i was convinced that the result of "restart" was the same as calling "stop" and after "start".
However, thank you very much!