![]() I don’t remember this being one of requirements for passwordless logins. ![]() ![]() So I hacked that script by adding a line "echo “192.168.1.3 wanker” > “$” to the /etc/hosts file and that fixed the problem… But this doesn’t really seem like the right way to fix it… If WD is rewriting the hosts file it seems to me like “the Debian way” would be to have a configuration file for it someplace that gets used by whatever script builds it… Or Something.ĭoes anybody know if there’s some “canonical” way to fix this? (I trolled through all the posts I could find and it seemed like there were some discussing no-login ssh and /etc/hosts but they were all in some sort of state where I couldn’t post to them, so I’m posting this new thread…)īut in order to make rsync work from a script I had to get no-password SSH working, which required (among a lot of other things of course) creating an entry in “/etc/hosts” for each machine I’m backing up with rsync.Įrmm, why do you need to add the remote ip host in the hosts file ? Just use the host or ip. I discovered it craps out after every reboot because “/etc/hosts” is getting rewritten by this script “/etc/network/if-up.d/genHostsConfig” which is a link to “/usr/local/sbin/genHostsConfig.sh” which actually *builds* a new /etc/hosts file on reboot, almost unconditionally. But in order to make rsync work from a script I had to get no-password SSH working, which required (among a lot of other things of course) creating an entry in “/etc/hosts” for each machine I’m backing up with rsync.īut then I ran into the “control panel goes out to lunch and keeps asking for an admin password when there isn’t one” bug, so I had to do a power-off reset to fix that, and when it came back up my no-login ssh was dead. OK, so, I basically got my new 2TB “M圜loud” hacked into doing rsync etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |