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 amd64 install of Jessie which uses autofs with a NIS map. > Booting up, and the autofs mount points do not show up. If I restart autofs > manually they then start working properly. I have an almost identical VM which > has sysvinit instead of systemd where autofs works just fine. > > Looking at the logging in journalctl, it looks like autofs is being started > before NIS (or possibly at exactly the same time). > > Jan 01 00:49:41 jessie-test systemd[1]: Inserted module 'autofs4' > Jan 01 00:49:43 jessie-test nis[435]: Setting NIS domainname to: > local.diamand.org. > Jan 01 00:49:43 jessie-test autofs[436]: Starting automount.... > Jan 01 00:49:44 jessie-test nis[435]: Starting NIS services: ypbind. > > 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.socket > ypbind.service nslcd.service slapd.service > > But nothing in the nis.service file mentions ypbind, and so the dependency > never gets setup, and the ordering isn't reliable. > > $ grep ypbind nis.service > -- nothing -- > > Probably this means that if you're lucky, the timing will work out, and if > you're not, it won't! > > I'm using systemd-syv version 218-3 from experimental on top of Jessie. >
Please attache the output of "reportbug --template systemd" (run as root) and also please attach the "journalctl -alb" output, ideally with debugging enabled via systemd.log_level=debug on the kernel command line. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature