I have just tested this, and I still got "empty list" . I then restarted
the httpd-naat process seeing if that would help, and the same thing
occured. I would like to help as much as I can to assist in fixing this
problem. I am ready to test any updates you would like. Or if you like, you
can have access directly to my system if it will help.
Thanks,
Paul Smith
---------------------------------------------------
Paul W. Smith
Network Operations Analyst
MCP, CLA, CRA, BCCA
Enterprise Services
Metafore
T: 416-778-1300 x7366
F: 416-778-8917
[EMAIL PROTECTED]
http://www.metafore.ca
Anywhere, anytime. 360 degrees by 365 days.
----------------------------------------------------
|--------+---------------------------------------->
| | Renaud Chaillat |
| | <[EMAIL PROTECTED]> |
| | Sent by: |
| | cooker-firewall-owner@linux-ma|
| | ndrake.com |
| | |
| | |
| | 07/27/2001 07:48 AM |
| | Please respond to |
| | cooker-firewall |
| | |
|--------+---------------------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
|
| Subject: Re: [Cooker-firewall] Re: Why are update questions not being
answered? |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
On Friday 27 July 2001 12:27, you wrote :
> I think we can rule out the active/passive ftp. I opened up the bastille
> script to allow active ftp and the update still didn't work :-(
>
> I have also throu tcpdump noticed that I do get a response from the
> selected ftp-server so the error is probably later in the parsing of the
> data. I can send you a transcript from tcpdump of a session if it helps
you
> (I doubt it thou)
>
I've taken a look and found the problem.
This has nothing to do with the network configuration, but is due to
changes
made in the update policy at the final stage of the product : snf has now
its
own directory for updates, but since it's a 7.2 at its core, the updated
packages are the same and so are simple _links_ to the 7.2 updated
packages.
Being a link simply breaks a regular expression in the scripts that handle
the packages list, packages_to_update.pl, download_packages.pl and
show_description.pl. I think this had been tested only with real files :-(
Since they're small, I attach the modified files to this mail, tell me if
this fixes the problem. They must be placed in /usr/share/naat/scripts/
Regards,
Renaud
(See attached file: packages_to_update.pl)
(See attached file: download_packages.pl)
(See attached file: show_description.pl)
packages_to_update.pl
download_packages.pl
show_description.pl
