Re: [IPCop-devel] setreservedports after restore

On 28 May 2010 21:06, Udo <li...@ur...> wrote:
> Hi all,
>
> have a problem with command setreservedports for the GUI in combination
> with the restore process during installation. I will explane.
>
> Before I backup my Cop 1.9.15-r4603, i modified the secureport for the
> GUI to port
> 33445 and it worked. Then I created the backup set and exported the
> backup key.
>
> During installation of my new build 1.9.15r4608 I restored this backup
> set and tried to use
> the GUI with port 33445 but nothing happend. 8443 the same.
>
> I thought that I could fix this by using the setreservedports --gui
> 33445 command
> but the port is still occupied, so setreservedports failed.
>
> Ok, I found this!
>
> In the /var/ipcop/main/settings file wthe port was set to 33445 but in
> httpd.conf the Listen Port
> and the Vhost Port are still set to 8443.
>
> Created a new backup set but this time on floppy medium to see the
> backup files list.but the
> httpd.conf was not listed.
>
> I don´t know if the httpd.conf should be stored in the backup file and
> failed
> in this case, or if a script finally reads the /var/ipcop/main/settings
> and push
> it into httpd.conf
>
> I had the same problem with the latest builds before.
>
> Udo

Presumably, we don't want to restrict ourselves by including
httpd.conf in a backup file. It may need to be overwritten in a future
update?

setreservedports.pl currently reads the existing gui port number from
/var/ipcop/main/settings, and uses that to change the apache port.
That is why the script is failing for you, as the oldport/existing
port in httpd.conf is different, and the sed command is failing.

Perhaps setreservedports.pl could be altered so that $oldport is read
from httpd.conf, or the $oldport regex is replaced by something more
general, such as [0-9]+, or \d{2,5}, or similar/better?

Eric