Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33932 - systemd service command-lines lost on every single package update.

Attached to Project: Arch Linux
Opened by James (shirokuma) - Tuesday, 19 February 2013, 11:10 GMT
Last edited by Allan McRae (Allan) - Tuesday, 19 February 2013, 13:24 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Service command-line options are lost on *every single package update* and have to be restored. This makes pacman+systemd in its current state very frustrating.

For example by default spamassassin is configured very badly and the only way to fix it is via the command line. So I change:

/usr/lib/systemd/system/spamassassin.service

I have to add "--socketpath=/var/lib/spamassassin/socket" to "ExecStart".

Now every time I upgrade spamassasin it overwrites my service file and I am forced to make the exact same change.

IMO the service files should be subject to the "pacnew/pacsave" style backups. I tried to find information about how I could edit the list of directories considered for backup using this mechanism but the information was not forthcoming.
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 19 February 2013, 13:24 GMT
Reason for closing:  Not a bug
Comment by Fabian Homborg (alfa) - Tuesday, 19 February 2013, 12:05 GMT
Copy the file to /etc/systemd/system and edit that one, or make a /etc/systemd/system/spamassassin.service that includes

.include /usr/lib/systemd/system/spamassassin.service

and the vars you want changed.

NOTABUG
Comment by James (shirokuma) - Tuesday, 19 February 2013, 12:11 GMT
That wouldn't work if there are dependencies on the service... without having to copy every single dependant service.

Sounds like a lot of hassle compared to the old system of using /etc/conf.d

The more I use systemd the less I like it.
Comment by Fabian Homborg (alfa) - Tuesday, 19 February 2013, 12:33 GMT
Yes, it does.
Comment by James (shirokuma) - Tuesday, 19 February 2013, 12:43 GMT
Apparently I'm supposed to copy the service file from /usr/lib/systemd to /etc/systemd/system.

Will try that.
Comment by James (shirokuma) - Tuesday, 19 February 2013, 12:47 GMT
Okay that works... /etc/systemd overrides /usr/lib/systemd whilst preserving target dependencies. This should be closed sorry about that.

Loading...