blob: cd8a4be05f23c655ad9658dfe16405c0c5687574 [file] [log] [blame]
Patrick Williamsc124f4f2015-09-15 14:41:29 -05001# This configuration file lists filesystem objects that should get verified
2# during startup and be created if missing.
3#
Brad Bishop6e60e8b2018-02-01 10:27:11 -05004# Entries have the following format:
Patrick Williamsc124f4f2015-09-15 14:41:29 -05005# <type> <owner> <group> <mode> <path> <linksource>
6# where the items are separated by whitespace !
7#
Brad Bishop6e60e8b2018-02-01 10:27:11 -05008# The # character introduces a comment lasting until end of line.
9# Blank lines are ignored.
10#
Brad Bishop19323692019-04-05 15:28:33 -040011# <type> : d|f|l|b : (d)irectory|(f)ile|(l)ink|(b)ind
Patrick Williamsc124f4f2015-09-15 14:41:29 -050012#
13# A linking example:
14# l root root 0777 /var/test /tmp/testfile
15# f root root 0644 /var/test none
16#
17# Understanding links:
18# When populate-volatile is to verify/create a directory or file, it will first
19# check it's existence. If a link is found to exist in the place of the target,
20# the path of the target is replaced with the target the link points to.
21# Thus, if a link is in the place to be verified, the object will be created
22# in the place the link points to instead.
23# This explains the order of "link before object" as in the example above, where
24# a link will be created at /var/test pointing to /tmp/testfile and due to this
25# link the file defined as /var/test will actually be created as /tmp/testfile.
26d root root 1777 /run/lock none
27d root root 0755 /var/volatile/log none
28d root root 1777 /var/volatile/tmp none
29l root root 1777 /var/lock /run/lock
Patrick Williamsc124f4f2015-09-15 14:41:29 -050030l root root 0755 /var/run /run
31l root root 1777 /var/tmp /var/volatile/tmp
32l root root 1777 /tmp /var/tmp
33d root root 0755 /var/lock/subsys none
34f root root 0664 /var/log/wtmp none
35f root root 0664 /var/run/utmp none
36l root root 0644 /etc/resolv.conf /var/run/resolv.conf
37f root root 0644 /var/run/resolv.conf none