F15: NIS, NFS mounts and systemd
 

Hi,

2011/4/5 Severin Gehwolf <sgehwolf@redhat.com>:
> Hi,
>
> I am trying to get NIS and /home NFS mounts working on F15. In essence,
> the dependency chain of services I need on my computer is as follows:
>
> Â* Â* 1. Bring up the network interface
> Â* Â* 2. Mount /home via NFS (maybe this should be done last?)
> Â* Â* 3. Make sure NIS is available (I also need Kerberos for validating
> Â* Â* Â* Â*passwords of NIS users)
>
> On F14 I managed to do this by using the network service, which is
> brought up first, then NFS shares are mounted and finally the ypbind
> service is started. How would I do something similar using systemd?
>
> I'm totally cool with using NetworkManager instead of network if that's
> preferred, but I'd like it to work for both runlevels 3 and 5.
>
> The immediate issue I am facing at the moment is that the network is not
> brought up automatically on boot (I have chkconfig'ed it on for
> runlevels 3 and 5). If I manually bring it up using ifup it works fine.

I'm using network and it works fine for me on updated F15. Try
systemctl enable network.service

> Another problem I am having is that NIS does not seem to work at all
> (service is started, SELinux properly configured), but cannot get any
> NIS accounts.
>
> Thanks for any pointers!
>
> --Severin
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>



--
Best regards,
Michal

http://eventhorizon.pl/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

On 04/05/2011 04:50 PM, Michał Piotrowski wrote:
> Hi,
>
> 2011/4/5 Severin Gehwolf <sgehwolf@redhat.com>:
>> Hi,
>>
>> I am trying to get NIS and /home NFS mounts working on F15. In essence,
>> the dependency chain of services I need on my computer is as follows:
>>
>> 1. Bring up the network interface
>> 2. Mount /home via NFS (maybe this should be done last?)
>> 3. Make sure NIS is available (I also need Kerberos for validating
>> passwords of NIS users)
>>
>> On F14 I managed to do this by using the network service, which is
>> brought up first, then NFS shares are mounted and finally the ypbind
>> service is started. How would I do something similar using systemd?
>>
>> I'm totally cool with using NetworkManager instead of network if that's
>> preferred, but I'd like it to work for both runlevels 3 and 5.
>>
>> The immediate issue I am facing at the moment is that the network is not
>> brought up automatically on boot (I have chkconfig'ed it on for
>> runlevels 3 and 5). If I manually bring it up using ifup it works fine.
>
> I'm using network and it works fine for me on updated F15. Try
> systemctl enable network.service
>
It doesn't worked for me either. There is bug about it [1] and it
doesn't looked fixed.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=692008

>> Another problem I am having is that NIS does not seem to work at all
>> (service is started, SELinux properly configured), but cannot get any
>> NIS accounts.
>>
>> Thanks for any pointers!
>>
>> --Severin
>>
>> --
>> devel mailing list
>> devel@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/devel
>>
>
>
>

--
Marcela Mašláňová
BaseOS team Brno
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

Hi,

On Tue, 2011-04-05 at 17:26 +0200, Marcela Mašláňová wrote:
> On 04/05/2011 04:50 PM, Michał Piotrowski wrote:
> > Hi,
> >
> > 2011/4/5 Severin Gehwolf <sgehwolf@redhat.com>:
> >> Hi,
> >>
> >> I am trying to get NIS and /home NFS mounts working on F15. In essence,
> >> the dependency chain of services I need on my computer is as follows:
> >>
> >> 1. Bring up the network interface
> >> 2. Mount /home via NFS (maybe this should be done last?)
> >> 3. Make sure NIS is available (I also need Kerberos for validating
> >> passwords of NIS users)
> >>
> >> On F14 I managed to do this by using the network service, which is
> >> brought up first, then NFS shares are mounted and finally the ypbind
> >> service is started. How would I do something similar using systemd?
> >>
> >> I'm totally cool with using NetworkManager instead of network if that's
> >> preferred, but I'd like it to work for both runlevels 3 and 5.
> >>
> >> The immediate issue I am facing at the moment is that the network is not
> >> brought up automatically on boot (I have chkconfig'ed it on for
> >> runlevels 3 and 5). If I manually bring it up using ifup it works fine.
> >
> > I'm using network and it works fine for me on updated F15. Try
> > systemctl enable network.service

Ok, network and NFS mounts work as expected now. For the network
configuration I did:

$ systemctl enable network.service
$ systemctl disable NetworkManager.service
plus added NM_MANAGED=no to /etc/sysconfig/network-scripts/ifcfg-ethX

Not sure if I had to do all of them, but works now :) Thanks!

> >
> It doesn't worked for me either. There is bug about it [1] and it
> doesn't looked fixed.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=692008

Hmm, seems to work for me

> >> Another problem I am having is that NIS does not seem to work at all
> >> (service is started, SELinux properly configured), but cannot get any
> >> NIS accounts.

A bit more feedback on the NIS front:

For whatever reason ypbind is not brought up by systemd on boot
(chkconfig lists ypbind as on for r3,r5; when I do
$ systemctl enable ypbind.service
ypbind.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig ypbind on

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.

Thanks,
Severin

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

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. 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@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

2011/4/5 Orion Poplawski <orion@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

### BEGIN INIT INFO
# 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
### END INIT INFO

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@cora.nwra.com
> Boulder, CO 80301 Â* Â* Â* Â* Â* Â* Â*http://www.cora.nwra.com
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>



--
Best regards,
Michal

http://eventhorizon.pl/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

W dniu 5 kwietnia 2011 21:48 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:
> 2011/4/5 Orion Poplawski <orion@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
>
> ### BEGIN INIT INFO
> # 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

Without apache part :)

> ### END INIT INFO
>
> 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@cora.nwra.com
>> Boulder, CO 80301 Â* Â* Â* Â* Â* Â* Â*http://www.cora.nwra.com
>> --
>> devel mailing list
>> devel@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/devel
>>
>
>
>
> --
> Best regards,
> Michal
>
> http://eventhorizon.pl/
>



--
Best regards,
Michal

http://eventhorizon.pl/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

W dniu 5 kwietnia 2011 21:49 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:
> W dniu 5 kwietnia 2011 21:48 użytkownik Michał Piotrowski
> <mkkp4x4@gmail.com> napisał:
>> Try to add some informations about ordering to ypbind script
>>
>> ### BEGIN INIT INFO
>> # 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
>
> Without apache part :)
>
>> ### END INIT INFO
>>
>> or better - rewrite this POS
>> http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind to
>> native systemd service

I am afraid that none of these scripts
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/yppasswdd
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypserv
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypxfrd
does have the correct ordering information.

I can help with rewriting to native sysetmd services, but I need a
tester - I do not use this service, so I'm not sure if I can correctly
configure and test.

--
Best regards,
Michal

http://eventhorizon.pl/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

On Tue, 2011-04-05 at 22:03 +0200, Michał Piotrowski wrote:
> W dniu 5 kwietnia 2011 21:49 użytkownik Michał Piotrowski
> <mkkp4x4@gmail.com> napisał:
> > W dniu 5 kwietnia 2011 21:48 użytkownik Michał Piotrowski
> > <mkkp4x4@gmail.com> napisał:
> >> Try to add some informations about ordering to ypbind script
> >>
> >> ### BEGIN INIT INFO
> >> # 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
> >
> > Without apache part :)
> >
> >> ### END INIT INFO
> >>
> >> or better - rewrite this POS
> >> http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind to
> >> native systemd service
>
> I am afraid that none of these scripts
> http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind
> http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/yppasswdd
> http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypserv
> http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypxfrd
> does have the correct ordering information.
>
> I can help with rewriting to native sysetmd services, but I need a
> tester - I do not use this service, so I'm not sure if I can correctly
> configure and test.

Is there documentation somewhere as to how to write a native systemd
service? Thanks!

--Severin

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

On 04/05/2011 04:08 PM, Severin Gehwolf wrote:

On Tue, 2011-04-05 at 22:03 +0200, Michał Piotrowski wrote:


W dniu 5 kwietnia 2011 21:49 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:


W dniu 5 kwietnia 2011 21:48 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:


Try to add some informations about ordering to ypbind script

### BEGIN INIT INFO
# 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



Without apache part :)



### END INIT INFO

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




I am afraid that none of these scripts
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/yppasswdd
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypserv
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypxfrd
does have the correct ordering information.

I can help with rewriting to native sysetmd services, but I need a
tester - I do not use this service, so I'm not sure if I can correctly
configure and test.



Is there documentation somewhere as to how to write a native systemd
service? Thanks!

--Severin



I thought that was the "GREAT" thing about
systemd - it would work with all the existing init scripts!



Sounds like it falls short.





--

StephenÂ*Clark

NetWolves

Sr.Â*SoftwareÂ*EngineerÂ*III

Phone:Â*813-579-3200

Fax:Â*813-882-0209

Email:Â*steve.clark@netwolves.com

http://www.netwolves.com




--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F15: NIS, NFS mounts and systemd
 

Steve Clark (sclark@netwolves.com) said:
> I thought that was the "GREAT" thing about systemd - it would work with all the existing init scripts!

It should. However, it parallelizes them based on the dependencies expressed
in the scripts, which means that it will expose issues where there were
implicit dependencies that weren't ever made explicit in the scripts.

Bill
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel