Description of problem:
Have to reconfig and restart the nis server after every reboot
Version-Release number of selected component (if applicable):
Cauldron
How reproducible:
Every reboot
Steps to Reproduce:
1. Install ypserv and config
2. Check client for service.
3. reboot server and check clients
Reproducible:
Steps to Reproduce:

I installed ypserv without configuration just to test if the service start with boot on Mageia5 beta2.
Just after the installation the service is not started which seems normal because there is no need to run it without first configuration.
But after a reboot the service is running.
Can you do a new test with Mageia5 beta2 ?
These output after the reboot :
# systemctl status ypserv.service
â ypserv.service - LSB: The ypserver daemon (for a NIS/YP server)
Loaded: loaded (/etc/rc.d/init.d/ypserv)
Active: active (exited) since mar. 2015-01-27 22:06:39 CET; 1min 0s ago
Process: 932 ExecStart=/etc/rc.d/init.d/ypserv start (code=exited, status=0/SUCCESS)
janv. 27 22:06:39 localhost ypserv[932]: Lancement du serveur YPÂ : [ OK ]

Unfortunately this package has no dedicated maintainer. Adding 2 packagers who updated the package at some point in the past, and also Colin who might want to give some insight about the systemd issue.

So I have configured ypserv on mga 5, and it appears the settings are persisting:
[root@localhost nerdsville]# service ypserv status
â ypserv.service - LSB: The ypserver daemon (for a NIS/YP server)
Loaded: loaded (/etc/rc.d/init.d/ypserv)
Active: active (exited) since Tue 2015-08-11 23:37:28 EDT; 54s ago
Process: 954 ExecStart=/etc/rc.d/init.d/ypserv start (code=exited, status=0/SUCCESS)
Aug 11 23:37:28 localhost.localdomain ypserv[954]: Starting YP server services: [ OK ]
One thing I do notice, however, is that the default settings are never copied into their appropriate directories, could this be the issue we are looking at? The settings as I configured them seem to persist through reboot as it stands, but I did need to copy over the files manually, the package installation did not do this.
Regards

(In reply to Robert Courtright from comment #6)
> here some more information as to why it won start. From the boot log.
>
> SKIP ^[[0m] Ordering cycle found, skipping LSB:...ver daemon (for a NIS/YP
> server)
> SKIP ^[[0m] Ordering cycle found, skipping LSB:...frd daemon (for a NIS/YP
> server)
Do you think you could please provide a list of the services that are running under systemd so that I could mock the environment?
This command should provide this information: systemctl list-units