| 1 |
On Tue, Sep 25, 2012 at 6:56 PM, walt <w41ter@×××××.com> wrote: |
| 2 |
> On 09/25/2012 02:42 PM, Canek Peláez Valdés wrote: |
| 3 |
>> |
| 4 |
>> On Tue, Sep 25, 2012 at 2:24 PM, walt <w41ter@×××××.com> wrote: |
| 5 |
>>> |
| 6 |
>>> I just installed and booted with systemd and most services are working |
| 7 |
>>> normally, except syslog.service and remote-fs.service. Both of those |
| 8 |
>>> failed on bootup with a "No such file or directory" error. |
| 9 |
>>> |
| 10 |
>>> I can't figure out how to make systemd tell me which files it can't |
| 11 |
>>> find. Any ideas? |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> The syslog.service works as a place-holder for whatever syslog you |
| 15 |
>> have installed (or not). So, if you have syslog-ng, you do |
| 16 |
>> |
| 17 |
>> ln -s /usr/lib/systemd/system/syslog-ng.service |
| 18 |
>> /etc/systemd/system/syslog.service |
| 19 |
> |
| 20 |
> |
| 21 |
> My problem is that I don't have syslog-ng.service in /usr/lib/systemd. |
| 22 |
> Neither systemd nor syslog-ng installed it. Do I write it myself? |
| 23 |
|
| 24 |
No, I suppose is in syslog-ng sources, but the ebuilds in Gentoo |
| 25 |
disables systemd support (at least for 3.3.5): |
| 26 |
|
| 27 |
# grep -n systemd /usr/portage/app-admin/syslog-ng/syslog-ng-3.3.5-r1.ebuild |
| 28 |
68: --disable-systemd \ |
| 29 |
|
| 30 |
So you can fill a bug in Gentoo to get systemd support in syslog-ng, |
| 31 |
or just take the unit file from the source and put it in |
| 32 |
/etc/systemd/system. I don't know why it is diabled, though. |
| 33 |
|
| 34 |
>> I do however have the remote-fs.service (systemd-191, out of the |
| 35 |
>> oven), I don't know why it isn't installed in your case. Which version |
| 36 |
>> are you using. |
| 37 |
> |
| 38 |
> Same: 191. I do have syslog.target and remote-fs.target installed, but |
| 39 |
> not the corresponding *.system files. Maybe the useflags determine this? |
| 40 |
|
| 41 |
Sorry: I meant remote-fs.target; I don't think there is |
| 42 |
remote-fs.service, it is a target (and one of the special ones). Do |
| 43 |
you need remote filesystem support? If not, then don't worry about it; |
| 44 |
but if you want to find the problem, send the output from systemctl |
| 45 |
status remote-fs.target. Mine is: |
| 46 |
|
| 47 |
# systemctl status remote-fs.target |
| 48 |
remote-fs.target - Remote File Systems |
| 49 |
Loaded: loaded (/usr/lib64/systemd/system/remote-fs.target; enabled) |
| 50 |
Active: active since Mon, 24 Sep 2012 18:33:09 -0500; 1 day and 3h ago |
| 51 |
Docs: man:systemd.special(7) |
| 52 |
|
| 53 |
Regards. |
| 54 |
-- |
| 55 |
Canek Peláez Valdés |
| 56 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 57 |
Universidad Nacional Autónoma de México |
Archives