On Mon, Jun 10, 2002 at 08:11:25AM +1200, Juha Saarinen wrote:
> On Sun, 9 Jun 2002, Courier User wrote:
>
> > Upgrading the OS's on the servers used by an entire ISP that serves
> > many users is not a trivial task. It cannot be done quickly.
>
> Nevertheless, it should be done as quickly as possible. Otherwise, you'll
> waste heaps of time working around obscure bugs like the one you
> described, and patching for security holes. ;-)
Agreed. For example, we are working on our OS upgrade, and it's
likely to take place within the next few weeks.
And as for this sh bug: there are other sh bugs that people have
happily been coding around for years. For example: using ...
${1+"$@"}
... instead of ...
"$@"
... due to an ancient bug that still exists in some versions of sh
that are floating around.
Of course people should upgrade their OS's. But I don't see why it
is so important to avoid making a small and effective change to
share/courierctl.start that will prevent this bug from biting people
in the future.
And as I mentioned before, I'm not convinced that pre 4.5 freebsd
versions are the only OS versions which have this sh bug. It seems
likely to me that many sh's that stemmed from the original BSD
4.[1-4] code could also have this problem.
So why not just put the parens around '${libexecdir}/courier/courierd &'
in the final line of share/courierctl.start and be done with it?
It took less than a minute to do that on my system, and I'm sure
that it would take no longer than that to do the same thing in the
Courier code base.
> --
> Juha Saarinen
--
Courier User
[EMAIL PROTECTED]
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
