Mailinglist Archive: opensuse-bugs (10759 mails)

< Previous Next >
[Bug 540587] If Yast MUST NOT kill SQUID in middle of system update!
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 22 Oct 2009 02:07:48 -0600
  • Message-id: <20091022080748.18979245518@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=540587

User suse@xxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=540587#c11





--- Comment #11 from L. A. Walsh <suse@xxxxxxxxx> 2009-10-22 01:07:43 PDT ---
From first few of initial report...

I was doing a system update. Normally my web requests go through squid to take
advantage of a large local (6GB) disk cache for various downloaded objects.

However, >>>yast<< also pays attention to the global vars HTTP_PROXY and
friends,
and uses them during its operations. Normally not a problem.

--------

I was running the GUI version of YaST -- the same would likely happen with
zypper -- I mean they have to pay attention to the proxy, it just so happens if
they are updating the proxy package AND it is running on the same machine, ...
*cough*; *choke*.

Probably need to check if running through a proxy, does proxy addr reverse DNS
evaluate to the reverse DNS of the current machine?... That would have
prevented
my 'hiccup'..., but better would be to loop through all the interface addresses
and see if any match the proxy in case I was using a name associated with a
different interface ??

Is this the information you were looking for?

Should be able to download squid, run the install, then restart it, then
continue with downloading more packages....just have to be sure to not be
downloading while squid is restarting. Ideally closing the connection ...
doesn't usually take squid long to restart if there are no connections -- a few
seconds.

Should be able to update squid while it is running unless the update deletes
the cache directory or something.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >