-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Sun, 16 Jun 2013 17:25:04 +0400 Andrey Borzenkov <arvidjaar@gmail.com> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
В Sun, 16 Jun 2013 14:54:21 +0200 (CEST) "Carlos E. R." <robin.listas@telefonica.net> пишет:
Jun 16 14:43:23 Telcontar.valinor famd[8826]: can't register with portmapper. Please start a portmapper (for example rpcbind), then try again to start famd.
please show
systemctl show fam.service systemctl show rpcbind.service
Forget it. systemd translates initscript dependencies to ordering dependencies (After/Before) which means, if rpcbind is enabled, fam will be started after it, but it will not be required (i.e. it will not be started when you start fam). So there is nothing wrong here. You need to enable rpcbind, that's all. If it fails to start even when rpcbind is enabled, that deserves attention.
systemd fails to start famd
Why to you start every e-mail with "systemd fails ..."? It has absolutely nothing to do with systemd. You would have exactly the same problem in case of "chkconfig rpcbind off" with sysvinit. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9vlUACgkQR6LMutpd94zzZACeLpiC218GQLgNF3fnUzOe+H+r YOoAniz9WibWY/OIjiWDBSstH1k/kUxC =cg2W -----END PGP SIGNATURE----- N▀╖╡ФЛr╦⌡yИ ┼Z)z{.╠О╝·к⌡╠йБmЙ)z{.╠Й+│: ╒{Zrшaz▄'z╥╕j)h╔ИЛ╨г╬ё ч╝┼^·к╛z┼Ю