Custom Query (894 matches)

When running bcfg2 -I, the package installation questions should be more verbose. For example, now bcfg2 asks:

Would you like to install Package: screen? (y/N):

It could ask something like this:

Upgrade package 'screen' (1.2.3 => 1.2.4)? (y/N):

DOWNGRADE package 'screen' (1.2.4 => 1.2.3)? (y/N):

Re-install package 'screen' due to changed files? (List the files with 'debsums -as screen') (y/N):

Similarly, ConfigFile? installation questions could offer a choice to see a diff of the file.

OTOH, while these enhancements would be nice, there is the reporting system that should give this information anyway.

Suppose that a config file belonging to a .deb package is changed, eg. /etc/screenrc. Running bcfg2 without -q notices this change and re-installs the 'screen' package. However, config files are not overwritten when re-installing packages (and they shouldn't be). So bcfg2 ends up re-installing 'screen' every time it is run, and still claiming "All entries correct." even though they are not.

The best fix I can think of for this problem (and other similar problems - I think these exist!) would be to re-run bcfg2 with -n whenever bcfg2 made choices and thought that everything was fixed. This should be done internally in bcfg2, and by default.

This will slow down the bcfg2 client, but only when there is something to fix.

bcfg2-server seems to allow multiple instances to be listening on the same port. (I didn't know this was even possible!) This might cause confusion.

How to reproduce (at least on my debian etch with svn build 2531):

1. Start bcfg2-server: # /etc/init.d/bcfg2-server start

2. Start bcfg2-server manually: # bcfg2-server &

3. See netstat output:

# netstat -plunt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 x.x.x.x:6789          0.0.0.0:*               LISTEN     3909/python
tcp        0      0 x.x.x.x:6789          0.0.0.0:*               LISTEN     3906/python
(...)

How to fix: bcfg2-server should detect the situation where someone is already listening on the port and refuse to start.