I'm running minidlna and httpd on a RaspPI with archlinuxarm. Disk space for both services is located on a NAS drive and automounted. Both service files therefore contain the following dependencies: --------------------------------------------- Requires=network.target autofs.service remote-fs.target nss-lookup.target After=network.target autofs.service remote-fs.target nss-lookup.target --------------------------------------------- Both services fail to start (see syslog messages below, which indicate that the NAS-directories are not yet mounted or mountable) - httpd exits because its root-directory is not yet available - minidlna keeps running in an invalid state, because it didn't find its directories during startup After that both services can be started manually without problems with systemctl start ... Jan 1 01:00:22 mars minidlnad[189]: [1970/01/01 01:00:22] minidlna.c:582: error: Media directory "P,/srv/dlna/bilder" not accessible [Datei oder Verzeichnis nicht gefunden] Jan 1 01:00:33 mars apachectl[187]: Syntax error on line 174 of /etc/httpd/conf/httpd.conf: Jan 1 01:00:33 mars apachectl[187]: DocumentRoot must be a directory
Can you show the output of 'systemctl cat minidlna', 'systemctl cat httpd' (or whatever the units are called)? And the output of systemctl list-dependencies --all for them?
Created attachment 95026 [details] requested information, unpack with tar -xvzf data.tgz information as you requested in 4 file minidlna.dependencies httpd.dependencies minidlna.cat httpd.cat the .cat files are generated by the cat-command, my systemctl doesn't know any cat-option for the systemctl-command. The service files for httpd and minidlna are the files from the original archlinux-distribution with the exception, that I've added the Requires- and After-Options. BR Hans-Peter
Can you please attach the files as-is without making it so complicated to view them?
Closing due to lack of response.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.