next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects
Hello John,
=09I haven't seen a response to this note, so just a preliminary
comment, and we'll get followup from others.
=09One of our goals from very early on was to limit the
"invasiveness" of the CSuite Package, in just exactly the ways you
describe, both as to existing functionality, and as to things like
passwords. =20
=09As development has proceeded a long way beyond our original
design, we have discovered that many systems lacked some of the features
we had taken for granted, and so we have had to include in the
installation, provision to update systems just to get the package to work.
Except for simple additions, however, I understood that the installation
was careful about replacing existing functions without the install
operator's permission. [I say this only from discussion, as I have not
personally run the installation yet. My role on the team is currently as=
=20
scribe.]
=09I'm not sure what has happened here, whether the instalation
script failed to recognize your existing mail system, or whether the
confirmation (which was added for some "external" changes) failed in this
case. Or perhaps a test for certain features failed and caused a branch
directly to the zmailer install.
=09It is my understanding that CSuite would work quite successfully
with sendmail, although we must admit to not having tested it. One of
zmailer's claimed features is sendmail compatibility.
=09On behalf of the CSuite development team, our apologies for=20
this event. Thanks for bringing it to our attention, and hopefully we
will be able to resolve this and other problems while we are still in this
extended Beta phase.
Ed Dyer aa146@chebucto.ns.ca (902) H 826-7496 CCN Assistant Postmaster
http://www.chebucto.ns.ca/~aa146/ W 426-4894 CSuite Technical Workshop
P.S. As to sharing the server with other functions, in general we have not
made much in the way of assumptions, except that sufficient capability be
available to CSuite. Up until recently, we ran our development operation
on our production system, so we certainly expected the system to be doing
other things. Now we are trying to see how to split the load, in order to
boost performance enough to permit adding additional lines above our
current 72. - E.D.
Le Sam, 19 Avr 1997, John Nemeth =E9crivait :
> Date: Sat, 19 Apr 1997 21:39:42 -0300
> From: John Nemeth <jnemeth@cue.bc.ca>
> Reply-To: csuite-tech@chebucto.ns.ca
> To: csuite-tech@chebucto.ns.ca
> Subject: system invasiveness
>=20
> I realise that CSuite is intended to be a do everything package,
> but in some ways it is a little too invasive in the changes it makes
> to the system. The biggest problem is installing things outside of
> $CS_ROOT (i.e. /etc/zmailer.conf,
> /usr/local/{include/libintl.h,lib/libintl.a), and replacing
> /usr/lib/sendmail). I've seen talk about zmailer.conf on the list,
> and I've already covered libintl in another note.
>=20
> I have a carefully tuned custom sendmail setup. I have no
> intention of running zmailer, since I've invested a fair bit of time
> in learning the ins-and-outs of sendmail, and it is one most important
> parts of the system (there are very few things that will make the
> users yell louder then mail problems). My sendmail binary was
> replaced with a link to an incompatible program without asking or
> informing me, completely messing up mail on my system (luckily it
> isn't my production system); this is not good. CSuite should be
> prepared to work with sendmail, since that is by far the most used
> MTA. As far as I can tell, it really only needs to know the location
> of the sendmail binary, the location of the aliases file, and how to
> rebuild the aliases database; however, some work may be needed for
> VCN's.
>=20
> CSuite should not assume it is the only thing running on a
> machine, nor should it make make invasive changes without asking the
> operator. It should inform the operator of all standard things it
> wishes to replace (i.e. httpd, ftpd, and sendmail). Even a README
> would be better then just doing it. As a space saving measure, it
> shouldn't install things which are already present and of a
> sufficiently reason version which aren't modified (i.e. gawk, perl,
> etc.). The README should list all standard services which it wishes
> to replace with modified versions and why.
>=20
>=20
next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects