| 1 |
walt <w41ter@×××××.com> wrote: |
| 2 |
|
| 3 |
> On 07/26/2013 06:39 AM, gottlieb@×××.edu wrote: |
| 4 |
> > must I check that every entry previously in /etc/init.d now has an entry |
| 5 |
> > in /usr/lib/systemd/system? What do I do if there is no corresponding |
| 6 |
> > entry? |
| 7 |
> |
| 8 |
> I actually had to write a few of my own *.service files, which belong in |
| 9 |
> /etc/systemd/system/ instead of /usr/lib64/systemd/system. (systemd looks |
| 10 |
> in both places for service files) |
| 11 |
> |
| 12 |
> I started playing with systemd on a virtual gentoo machine many months |
| 13 |
> ago when gentoo's systemd was still very incomplete and lacked *.system |
| 14 |
> files for several important packages. I'm hoping the gentoo devs have |
| 15 |
> made progress with that problem, but fedora and arch linux have already |
| 16 |
> made the switch to systemd and you can steal *.service files from those |
| 17 |
> if you need to. |
| 18 |
> |
| 19 |
> BTW, I'm still using systemd only on my virtual machines so far. The |
| 20 |
> recent upgrade on ~amd64 is an ugly mess IMHO. |
| 21 |
|
| 22 |
Any documentation on what is in a service file? It does not look too |
| 23 |
bad, but I would rather see the full documentation on what you can have |
| 24 |
in there and exactly how they work. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Your life is like a penny. You're going to lose it. The question is: |
| 29 |
How do |
| 30 |
you spend it? |
| 31 |
|
| 32 |
John Covici |
| 33 |
covici@××××××××××.com |
Archives