F15: NIS, NFS mounts and systemd

Michał Piotrowski mkkp4x4 at gmail.com
Tue Apr 5 19:48:21 UTC 2011

2011/4/5 Orion Poplawski <orion at cora.nwra.com>:
> On 04/05/2011 01:21 PM, Severin Gehwolf wrote:
>> After a reboot the service is not brought up and I have to start it
>> manually :(
>> I managed to get NIS working manually. Perviously, I was missing a "nis"
>> in /etc/nsswitch and changed it to:
>> passwd: files nis
>> Once systemd will be able to bring up my ypbind, I'll be happy :) On
>> that note, I'd be happy to assist in any debugging. Just let me know.
> Probably an ordering issue - ypbind being started before network is ready.

Try to add some informations about ordering to ypbind script

# Provides: ypbind
# Required-Start: $local_fs $remote_fs $network
# Required-Stop: $local_fs $remote_fs $network
# Short-Description: Starts the ypbind daemon
# Description: The Apache HTTP Server is an extensible server

or better - rewrite this POS
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind to
native systemd service

> I
> have the same problem with LDAP hosted automount maps.  Tough nut to crack for
> all cases.
> I think using a NM dispatcher script to (re)start the needed daemons is the
> way to go though.
> --
> Orion Poplawski
> Technical Manager                     303-415-9701 x222
> NWRA/CoRA Division                    FAX: 303-415-9702
> 3380 Mitchell Lane                  orion at cora.nwra.com
> Boulder, CO 80301              http://www.cora.nwra.com
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel

Best regards,


More information about the devel mailing list