Works, thanks!
Applied the patch, and then repeatedly logged in, checked that home
directories are present, and rebooted.
Used 218-3 plus your patch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia
control: forwarded -1
http://lists.freedesktop.org/archives/systemd-devel/2015-January/026730.html
Am 01.01.2015 um 14:32 schrieb Michael Biebl:
> Upon further investigation, it looks like the Names= option was dropped
> from unit file parsing in v186. So even if the sysv-generator would
> write a
Am 01.01.2015 um 14:32 schrieb Michael Biebl:
> So the "obvious" fix I had in mind will not work. Any other ideas, how
> we can fix this? Shall we create symlinks in /run/systemd/?
> A possible issue with that approach might be, that multiple init scripts
> could have the same Provides: foo, so onl
Am 01.01.2015 um 03:40 schrieb Michael Biebl:
> Am 01.01.2015 um 03:25 schrieb Michael Biebl:
>> Am 01.01.2015 um 03:08 schrieb Michael Biebl:
>>> It looks though, as the sysv-genenator does not properly handle
>>> Provides, especially multiple names listed in Provides.
>>>
>>> # systemctl show ni
Am 01.01.2015 um 03:25 schrieb Michael Biebl:
> control: retitle -1 Provides: in SysV init scripts are not handled correctly,
> leading to wrong orderings
> control: severity -1 serious
>
> Am 01.01.2015 um 03:08 schrieb Michael Biebl:
>> control: found -1 215-8
>>
>> Am 01.01.2015 um 02:39 schri
control: retitle -1 Provides: in SysV init scripts are not handled correctly,
leading to wrong orderings
control: severity -1 serious
Am 01.01.2015 um 03:08 schrieb Michael Biebl:
> control: found -1 215-8
>
> Am 01.01.2015 um 02:39 schrieb Luke Diamand:
>> sysv-generator seems to correctly gene
control: found -1 215-8
Am 01.01.2015 um 02:39 schrieb Luke Diamand:
> sysv-generator seems to correctly generate an autofs.service file which has a
> dependency on NIS, specifically, ypbind:
>
> $ grep "After" autofs.service
> After=network-online.target remote-fs.target systemd-journald-dev-log
control: tags -1 moreinfo
Am 01.01.2015 um 02:39 schrieb Luke Diamand:
> Package: systemd-sysv
> Version: 218-3
> Severity: important
> Tags: upstream
>
> Dear Maintainer,
>
> I'm finding that autofs mounts which come from NIS maps don't show up when
> using systemd.
>
> I have a VM with an amd
Package: systemd-sysv
Version: 218-3
Severity: important
Tags: upstream
Dear Maintainer,
I'm finding that autofs mounts which come from NIS maps don't show up when
using systemd.
I have a VM with an amd64 install of Jessie which uses autofs with a NIS map.
Booting up, and the autofs mount points
9 matches
Mail list logo
