Comment 7 for bug 221737

I agree to Mathias, this is a strange behavior. In my opinion a newly installed service should autostart, or at least give a hint during installation that a configuration is needed before it is able to start up, and a short description how to accomplish that.

I am running Ubuntu 8.04 server (amd64) and nut version 2.2.1-2.1ubuntu7.1 and experience this same behavior.
A fix for this bug/behavior could be one of the following:
1) Change the default behavior to autostart the service and change the startup/init-script to signal "No configuration file is found" during boot, if that is the case, and return "Failed".
2) Leave a message in the end of the installation that nut needs to be configured before it can be started, and include the "START_UPSD=yes" options in the config-files so you do not have to edit /etc/defaults/nut
3) Change the default behavior to autostart and try to autoconfigure nut during post-installation, as described in Bug #129523

Note, the following is just a cross-reference to my duplicate: Bug #231212

Regards
Anders