You are not logged in.

#1 2015-11-06 14:36:01

veggen
Member
Registered: 2013-01-29
Posts: 12

Help debugging a self-made package: /var/run already exists

I converted a DEB package to an Arch one, but I have one more hurdle to overcome. I'm getting "var/run already exists". For the sake of testing, I renamed my /var/run to /var/run2, ran the installation and merged the two back. It worked ok. So I just need to figure out how to make it create a directory inside /var/run without trying to make /var/run itself. It creates many more directories on the system without problems and I can't figure out what makes this one special.

How do I debug this? Not sure where to start.... Can someone please provide an advice?

Offline

#2 2015-11-06 15:12:28

respiranto
Member
Registered: 2015-05-15
Posts: 479
Website

Re: Help debugging a self-made package: /var/run already exists

file-hierarchy(7) wrote:

       /var/run
           This compatibility symlink points to /run, ensuring that
           programs referencing this legacy path correctly find their
           runtime data.

I don't think any part of a program should be installed into /run, which is mounted as tmpfs.
You should most probably change some (or at least one) compile-time parameters, so you will need to get the sources instead of the .deb .

Unless you are by chance using debtap, could you provide your PKGBUILD?

Offline

#3 2015-11-06 15:14:36

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,559

Re: Help debugging a self-made package: /var/run already exists

Having the package install anything to /var/run or /run is bad, as it will disappear on each boot. Delete the dir in the package and use tmpfiles to create what's needed.

Offline

Board footer

Powered by FluxBB