Description of problem: Ypbind does not start up automatically Version-Release number of selected component (if applicable): ypbind-1.35-2.fc17.i686 How reproducible: Always - at least on the one machine so far affected Steps to Reproduce: 1.Turn off SELinux 2.Issue the command: systemctl enable ypbind.service 3.Reboot the machine Actual results: After the boot, ypbind is not running Expected results: Ypbind should be running Additional info: Although ypbind does not start up after booting, it starts just fine if started manually with the "systemctl start ypbind.service" command. No error message appeared in /var/log/messages. I did not observe this problem on a 64 bit Fedora 17 install. So far I have only seen this problem on this one 32 bit machine.
(In reply to comment #0) > Although ypbind does not start up after booting, it starts just fine if > started manually with the "systemctl start ypbind.service" command. No error > message appeared in /var/log/messages. I did not observe this problem on a > 64 bit Fedora 17 install. So far I have only seen this problem on this one > 32 bit machine. If there is no message in /var/log/messages at all, I'd say ypbind is disabled. What about if you boot with verbose systemd (log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg)?
You were correct, ypbind was in fact disabled. Perhaps I had a typo when I enabled it initially, but after enabling it this time, the service started up properly following a reboot. Please remove this bug report.
Closing on reporter's request.