Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 4
    it is simply there to separate service runtime data from the mess in /tmp - Also to provide a safe harbor for said data from the various cleanup jobs that trample throughout /tmp. Commented Oct 13, 2016 at 12:34
  • 1
    Thanks for the info about the permissions. However, according to FHS "Programs may have a subdirectory of /run; this is encouraged for programs that use more than one run-time file." - this seems to contradict both the "long lived services" criterion as well as the inability of programs to create their subdirectories due to limited permissions. Commented Oct 13, 2016 at 12:34
  • 1
    @DirkHerrmann No it doesn't. Have a look at /run and check out the complex (well...) directory structure caused by udev, udisk etc. I am not an expert on this particular issue, but I guess the boot scripts (which are run as superuser) set everything up. Commented Oct 13, 2016 at 13:22
  • 4
    "/run is technically not necessary, it is simply there to separate service runtime data from the mess in /tmp." - Good thing too, so unprivileged processes can't squat names system services want to use. Kinda sucks if nginx wants to use /tmp/nginx.pid but it already exists because of some misbehaving program. /run/ prevents this by requiring privileges to write to. Commented Oct 13, 2016 at 14:45