<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] /run vs /var/run in configuration files
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20/run%20vs%20/var/run%20in%20configuration%20files&In-Reply-To=%3C5053300F.30603%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="018629.html">
<LINK REL="Next" HREF="018676.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] /run vs /var/run in configuration files</H1>
<B>Guillaume Rousse</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20/run%20vs%20/var/run%20in%20configuration%20files&In-Reply-To=%3C5053300F.30603%40gmail.com%3E"
TITLE="[Mageia-dev] /run vs /var/run in configuration files">guillomovitch at gmail.com
</A><BR>
<I>Fri Sep 14 15:24:31 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018629.html">[Mageia-dev] /run vs /var/run in configuration files
</A></li>
<LI>Next message: <A HREF="018676.html">[Mageia-dev] /run vs /var/run in configuration files
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18674">[ date ]</a>
<a href="thread.html#18674">[ thread ]</a>
<a href="subject.html#18674">[ subject ]</a>
<a href="author.html#18674">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 11/09/2012 13:44, Colin Guthrie a écrit :
><i> 'Twas brillig, and Guillaume Rousse at 11/09/12 11:47 did gyre and gimble:
</I>>><i> Le 11/09/2012 12:23, Sander Lepik a écrit :
</I>>>><i> 11.09.2012 13:15, Guillaume Rousse kirjutas:
</I>>>>><i> [...]
</I>>>>><i>
</I>>>>><i> The /run - /var/run merge (/usrmove) is supposed to make the change
</I>>>>><i> transparent for applications. Manually converting applications to
</I>>>>><i> explicitely refers to the new location doesn't change its usefulness.
</I>>>>><i>
</I>>>><i> Well, if your system can't mount /var for some reason then keeping
</I>>>><i> things on /run might make recovery easier.
</I>><i>
</I>>><i> Then we probably should not refer to systemd directory as
</I>>><i> /usr/lib/systemd, but as /lib/systemd for exactly the same reason.
</I>><i>
</I>><i> I don't really see the comparison here.
</I>The point was: if the canonical path for /usr/lib|/lib directory (which
is actually the same) if the longuest one, why should the canonical path
for the /var/run|/run directory be the shortest one ?
><i> systemd is build to use /usr/lib/systemd these days, so it's technically
</I>><i> incorrect to refer to it as anything else (of course technically
</I>><i> incorrect != practically incorrect!)
</I>><i>
</I>>><i> Also, the usefulness of an available /run when /var is quite discutable,
</I>>><i> whereas its main purpose is to store pid files for backgroud processes,
</I>>><i> most of them using /var/lib for storing their data.
</I>><i>
</I>><i> Well, not just pid files. It also stores socket files which are critical
</I>><i> for IPC and such like and is an important bridge between initrd and the
</I>><i> real rootfs.
</I>><i>
</I>><i> Personally I'm more in favour of using /run directly and adding lint
</I>><i> rules that cause a build failure if files are packaged in either
</I>><i> /var/run or /run.
</I>Shipping /var/run or /run files/directory is a different issues, and is
rather related to tmpfs conversion.
However, a distinct lint rule could be to disallow the creation of
/var/run subdirectories in tmpfiles.d configuration files, or to use
/var/run pathes for PID files in systemd unit configuration files, if
/run is to be preferred.
><i> If nothing else it's marginally more efficient to use /run. No spinning
</I>><i> media stat required to dereference the index. In extreme cases, it will
</I>><i> help extend battery life. The benefits are tiny I'm sure, but it does
</I>><i> depend on context/setup and if there is no other tangible reasons, maybe
</I>><i> even this small advantage is enough to sway in one direction rather than
</I>><i> the other!
</I>Well, I'm not really impressed by potential perf issues, especially with
no backing benchmarks. I'm rather concerned about ease of maintainance,
and consistency between spec files.
Anyway, I just found out than /usr/lib and /run are the actual
directory, with /lib and /var/run the symlinks. Which makes an argument
of favor of considering the first one as canonical.
--
BOFH excuse #182:
endothermal recalibration
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018629.html">[Mageia-dev] /run vs /var/run in configuration files
</A></li>
<LI>Next message: <A HREF="018676.html">[Mageia-dev] /run vs /var/run in configuration files
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18674">[ date ]</a>
<a href="thread.html#18674">[ thread ]</a>
<a href="subject.html#18674">[ subject ]</a>
<a href="author.html#18674">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>