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