Il giorno 02/ago/06, alle ore 22:48, Steve Langasek ha scritto:
On Wed, Aug 02, 2006 at 11:56:45AM +0200, Luigi Gangitano wrote:
Could user application 'deal somehow' with 2.4 kernels making the
administrator aware that they will need a 2.6 kernel to work at all?

When will you make the administrator aware of this that won't make the
upgrade path ugly?

- if you error out in the preinst, the old version of squid continues
  running, but the dist-upgrade will break in the middle
- if you error out in the postinst, the dist-upgrade completes, but the administrator may then be looking at unexpected downtime related to trying
  to upgrade the kernel before squid will run again

Could it be stated in the Release Notes? Something like 'Upgrading from sarge with a 2.4 kernel expect some daemons to stop working until a new kernel is installed'.

Squid has a comm interface with different modules (poll, select and
epoll on linux, kqueue on freebsd, etc) choosen at build time. I
agree with upstream that compiling more than one comm module takes a
big change in one of the critical section and they are not willing to
make such a change to a stable release.

I dunno, the 538 line patch I have here to support runtime selection between kqueue, epoll, and select (as enabled) doesn't seem like such a big change
to me. :)

In alternative a new comm module based on libevent could be added.
libevent would support both epoll() and poll() and is in debian as of
now. I don't have the skills to create such a patch, but would
happily propose it upstream and include in the debian package.

Well, unlike the patch I just created, writing this would require
understanding the APIs of both libevent and squid's internal comm interface. That would take a bit longer to write & debug, compared with just providing
a basic plugin interface. <shrug>

I simply gave you the answer I got from upstream when asking for the same question. libevent was easier and preferred.

Can I have a look at your patch and, if you will, permission to submit it upstream?

Regards,

--
Luigi Gangitano -- <[EMAIL PROTECTED]> -- <[EMAIL PROTECTED]>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to