You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2019. It is now read-only.
I definitely have configurations that have been fetched with # in them, which vendor router is it? I can then hopefully trace it within that specific rancid script.
Same behavior seen on a Quagga router running FreeBSD. There was an octothorpe in the default FreeBSD MOTD (/etc/motd) causing Rancid to hang up. We're changing all of our MOTDs.
Simple fix but we were scratching our heads for a few days.
That's not really a fix.. That's restricting what I can have in my configs, rather than fixing RANCID.
Maybe this is something I should open with upstream?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If there's an octothorpe (# symbol) in a router's config, or in the login banner the router doesn't get its configuration pulled.
The text was updated successfully, but these errors were encountered: