freebsd bad droplet.conf symlink after 10.3 upgrade

August 13, 2016 174 views
Networking FreeBSD

After upgrading to 10.3 (freebsd-update style), my /etc/rc.digitalocean/droplet.conf is symlinked to ".conf" instead of "<droplet>.conf". the quick fix was to copy my "<droplet>.conf" to ".conf" and reboot.

Why isn't /etc/rc.d/digitalocean grabbing my droplet id from and creating the symlink? it times out such that DROPLET_ID is an empty string and thus the ".conf" symlink.

i compared my /etc/ files with a brand new 10.3 droplet and i didn't see any noticeable differences.

Be the first one to answer this question.