-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elwin,
At this point, I'm not sure that vcld prefers one way over the other (I develop on the frontend). However, if it does prefer one, it would be for eth0 to be private and eth1 to be public. In the very early days of VCL, it was required to be that way. There are a number of times when vcld checks for the existence of various files to determine what commands are available for use. So, it is probably checking to see if /bin/systemctl exists, finding it does not, and then using another method. With differences between distributions and versions, there's really no other way of knowing which commands to use other than checking to see what is there. Josh On Friday, May 22, 2015 1:02:53 PM Elwin Litchfield wrote: > I have been reviewing my vcld.log and have seen some entries which concern > me. My private network is on eth0 & the public network is on eth1. It > looks like the Management Node prefers that the public network is on eth0 & > the private network is on eth1. I am wondering if I should make the > network swap. > > Also it looks like the Management Node is looking for /bin/systemctl which > is not implemented in Centos till Centos7, so should upgrade to Centos7? > > Thanks > Lewis - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVfcjIACgkQV/LQcNdtPQMhcgCcDLslJsBx0cuwMFKyqH7gvzpn PLsAoIAi/UlPtiWgTLaMCMkPVRuBfutf =FjFp -----END PGP SIGNATURE-----
