Ask Question
How can I find out why cmdaemon is controlling (generating) /etc/resolv.conf on a non headnode? I used cm-list-managed-files to identify that cmd is in fact managing /etc/resolv.conf for a single node but I can't find what setting, role, etc. is controlling this as no other "regular" node has /etc/resolv.conf managed this way.
How can I find out why cmdaemon is controlling (generating) /etc/resolv.conf on a non headnode? I used cm-list-managed-files to identify that cmd is in fact managing /etc/resolv.conf for a single node but I can't find what setting, role, etc. is controlling this as no other "regular" node has /etc/resolv.conf managed this way.
Where am I?
In Bright Computing, Inc. you can ask and answer questions and share your experience with others!