top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Folder /run/http-xxx deleted after reboot on Fedora

0 votes
407 views

I have added a new service which starts a second httpd instance in fedora 19. The pid of the process is stored in /run/http-xxx directory, and my problem is that this directory disappears after each reboot.

How can I stop the system from deleting this folder in /run?

posted Aug 12, 2013 by Naveena Garg

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
/run is a tmpfs and lives in memory
 man tmpfiles.d

1 Answer

0 votes

I have solved my problem by placing the pid file inside the httpd folder (with a different name). But what creates this /run/httpd folder on reboot?

For sure, it is not the httpd server (it would have created the /run/http-xxx folder also).

answer Aug 12, 2013 by anonymous
Similar Questions
0 votes

I cannot manage to get fedora 19 to start a vnc server on reboot. I have tried various approaches:

a) edit /etc/systemd/system/vncserver@:1.service It does not work. It kills any vncserver I am running at :1, but *never* starts a new one.
systemctrl status vncserver@:1.service reports the service as dead, but without any error message.

b) I wrote a small bash script that starts vncserver at :1, and set a cronjob on the user. The server runs ok when I run the script from the terminal (I can see gnome desktop in it), but gnome does not start from the cronjob. (I have even set a sleep of 30 seconds to delay the start of the vncserver). The vncserver starts, but it is empty.

Method b worked in fedora 18, but not anymore in fedora 19. What is the way to start a tiger vnc server at reboot for a user?

+1 vote

I'm trying to set up Joomla on my laptop to play around with a site I'm planning. However SELinux seems to block write access for the installation routine to the direcotry /var/www/html and none of the solutions I've found by googling to allow SELinux httpd write access seems to work (installation hangs immediately).

setenforce 0 deosn't have any effect either as far as I can tell, as I still can't install Joomla. Anyone successfully installed Joomla 3 on Fedora 19 please can tell how I should proceed?

0 votes

I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs:

 # systemctl start transmission-daemon.service

If I let it be for a few minutes (~5), it finishes with a failure. The log is extremely unhelpful. This is very strange because it was working just fine until a few days ago.

+3 votes

I'm running a new FC20 system

systemctl -t service -a -l

to check services and I'm seeing several that I don't have installed for example. I've tried using systemctl disable to remove the service, and don't get anything back.

How do I prune my services list/get the unknown or uninstalled packages out?

...