| Summary: | dev-db/redis: systemd unit file | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Julien Sanchez <julien.sanchez> |
| Component: | Current packages | Assignee: | Johan Bergström <bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | systemd |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 448882 | ||
| Attachments: |
Redis systemd unit file
redis-2.6.15.ebuild diff |
||
Created attachment 360938 [details, diff]
redis-2.6.15.ebuild diff
+*redis-2.6.15-r1 (15 Oct 2013) + + 15 Oct 2013; Pacho Ramos <pacho@gentoo.org> +files/redis.service, + +files/redis.tmpfiles, +redis-2.6.15-r1.ebuild: + Add unit file (#488114 by Julien Sanchez) + |
Created attachment 360936 [details] Redis systemd unit file I have added systemd unit file for redis ebuild. I kept the same defaults as in the current default confd file. Could you review both ebuild patch and service files? (Of course, I have tested them on my system). Just a side note, isn't there an inconsistency between confd and initd files about PID file path? confd file's default is /var/run/redis/redis.pid and initd file's one is /run/redis/redis.pid. What is Gentoo ebuild policy about {/var/run,/run} files? Should /run paths be always used now?