... and this is exactly why I personally _hate_ all those "nice packaging systems". in the case of any minor change/problem, they might turn into nightmare, which needs deeper user's knowledge anyway (and thus, saves NOTHING, and makes things 10x worse than tarball-driven install).
those problems, in general, can be solved simply by manually-creating those files that are claimed as inaccessible, just to get the automatic script tainted and satisfied. echo "blahblah" >/etc/sysconfig/avastd should be enough
.
first, the package IS correct - /etc/default/avastd is there. And yes, during install, it IS extracted. But, this file is so called "config file", and will stay here and/or won't be refreshed, after package removal or with new reinstall.
just use dpkg --purge avast4server, and then, make a fresh install, and things would be OK.
well, /etc/init.d/avastd should be prepared also for this inconsistency, not claiming defaults to be present/readable, we'll add this check too, thanks for report,
pc