On 07/06/2014 07:45 PM, lee wrote:
Joe Zeff <joe(a)zeff.us> writes:
> On 07/06/2014 12:43 AM, lee wrote:
>> Not even the configuration files are where they belong.
>
> Actually, they're exactly where they belong. They just aren't where
> you expect them to be.
They belong under /etc, not hidden somewhere in /var.
as all things in var there are temporary state files
root@hal: ~ # ls -lR /var/lib/systemd
/var/lib/systemd:
total 12
drwxr-xr-x. 2 root root 4096 Jun 25 22:15 catalog
drwxr-xr-x. 2 root root 4096 Jun 21 19:29 coredump
-rw-------. 1 root root 512 Jul 7 08:03 random-seed
/var/lib/systemd/catalog:
total 12
-rw-r--r-- 1 root root 9570 Jun 25 22:15 database
/var/lib/systemd/coredump:
total 0
maybe you meant /usr/lib/systemd where initial files for services are?
(but /usr/lib is ok .. i see no problem with that)
configuration directory (for both systemd and systemd services)
are in /etc/systemd (btw : the services configurations and declarations
from /etc/systemd overwrites those from /usr/lib/systemd)
moreover you can separately configure a service without modifying the
.service file (which usually is linked in /etc/systemd) :
"Along with a unit file foo.service, a directory foo.service.d/ may
exist. All files with the suffix ".conf" from this directory will be
parsed after the file itself is parsed. This is useful to alter or add
configuration settings to a unit, without having to modify their unit
files. Make sure that the file that is included has the appropriate
section headers before any directive." (man systemd.unit)
HTH,
Adrian