On 06/23/2014 03:14 PM, Carlos E. R. wrote:
On 2014-06-23 19:31, Dylan wrote:
On 23/06/14 18:19, Andrey Borzenkov wrote:
В Mon, 23 Jun 2014 15:05:15 +0200 "Carlos E. R." <robin.listas@telefonica.net> пишет:
On 2014-06-23 14:44, Anton Aylward wrote:
However I get this:
# systemd-tmpfiles --clean Two or more conflicting lines for /tmp configured, ignoring. Two or more conflicting lines for /var/tmp configured, ignoring.
Same here.
Telcontar:~ # systemd-tmpfiles --clean Two or more conflicting lines for /tmp configured, ignoring. Two or more conflicting lines for /var/tmp configured, ignoring. Two or more conflicting lines for /tmp/systemd-private-* configured, ignoring. Two or more conflicting lines for /var/tmp/systemd-private-* configured, ignoring.
That more or less matches documentation:
If multiple files specify the same path, the entry in the file with the lexicographically earliest name will be applied, all all other conflicting entries logged as errors.
To avoid these errors you would need to copy /usr/lib/tmpfiles.d/tmp.conf into /etc/tmpfiles.d and edit, so it hides file in /usr/lib.
So since the (relevant) files in /usr/lib/tmpfiles.d and /run/tmpfiles.d are called tmp.conf, and the one Cristian suggested making in /etc/tmpfiles.d/ is called localtmp.conf; the new file is acted upon and the others cause errors. Had the manpage been read, this would have been blindingly obvious - it was here...
It is not obvious to me. I still do not understand what happens, even after reading the manpage several times.
For instance, what exact lines are conflicting, and from what exact files are they being read? I still do not see a "--verbose" or "--debug" option that would tell me that.
I agree, not only with the point about the lack of "--verbose" or "--debug" (or "--explain") but with it NOT being obvious. Yes a /etc/tmpfiles.d/tmp.conf would override the one in /usr/lib. But that's not the point. The localtemp.conf Does not override any lines in tmp.conf, it add lines that don't exit. It does not contradict them. It suplements them. The closest I can see to a problem lies in this phrase: <quote> All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same path, the entry in the file with the lexicographically earliest name will be applied, all all other conflicting entries logged as errors. </quote> That means localtemp comes before tmp. Maybe it should be renamed "zzlocaltemp" Well, no, it seems that interpretation of tha man page is not correct either: # mv localtmp.conf zzlocaltmp.conf # systemd-tmpfiles --remove --clean Two or more conflicting lines for /tmp configured, ignoring. Wrote > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org