Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
When I telnet to zebra to configure the interfaces of my FC5 linux box, it allows me to do everything except the "write" operation. It always gives me an error message like " Can't open configuration file zebra.conf.Eyn4DP".
When I telnet to zebra to configure the interfaces of my FC5 linux box, it allows me to do everything except the "write" operation. It always gives me an error message like " Can't open configuration file zebra.conf.Eyn4DP".
As zebra save its configuration to "/etc/zebra/zebra.conf" & you are not able to do that, this could possibly be some rights & permission issue. And hence you got to use root credentials to modify & configure zebra.
Thanks for your suggestion, amitsharma_26! I did use root access to run zebra,and I even changed permission of the file (zebra.conf) to 777. It didn't resolve the problem. It got to be something else! Just wonder anyone out there experienced the same problem before and be able to resolve the problem?
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
It sounds like zebra is trying to write to a temp file before it copies it to the main config file name. Normal users do not have permission to create files in /etc. Even if the zebra process isn't running as root, and the config file isn't owned by root, you still won't be able to create files in /etc unless you are root. Do not change the write permissions on the /etc directory.
There must be some documentation for zebra that explains how to run as non-root and still be able to write the configuration. Probably there is some option to make the daemon use a different location for the config file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.