The creation of the quagga user was not the only place
to add the quagga user to the quaggavty group. If
we are reinstalling quagga over a old version of
code then we need to check to see if the quagga
user is in the quaggavty and do the right thing.
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Reviewed-by: Dave Olson <olson@cumulusnetworks.com>
--gecos "Quagga routing suite" \
--shell /bin/false \
quagga >/dev/null
- usermod -a -G quaggavty quagga >/dev/null
+fi
+
+# We may be installing over an older version of
+# quagga and as such we need to intelligently
+# check to see if the quagga user is in the quaggavty
+# group.
+if ! /usr/bin/id quagga | grep &>/dev/null 'quaggavty'; then
+ usermod -a -G quaggavty quagga >/dev/null
fi
# Do not change permissions when upgrading as it would violate policy.