Re: [SM-STABLE] Slow performance and timeouts

[JBT <sm...@ju...>]

> The uid of the user owning the files is irrelevant.

Like hell it is. If you don't know why it isn't irrelevant,
you need to learn some unix-basics.

> When untarring, you can - and should - apply your own umask.
> If not changing the files often, you should use root:root
> for the owner, so that crackers will have a harder time
> defacing the site.

Well then, release the so-called stable files as root:root,
so that one needs to change those files to something less safe,
instead of having to do it the other way around.
Also: It is NOT mentioned anywhere in the stable release
install or readme files that users need to uid all of them.

Most users that I know would simply overwrite their
old files whilst unpacking, and replace them with
the new versions that way. Many of them will
use managers like midnight commander for that.

>> Also, looking around the code a little shows you
>> it is absolutely filled with huge amounts of comments
>> and slack-space. If it were to be released as a final/stable
>> production level code, then this needs to be deleted from the
>> code.
>
> How can one improve on the open-source code without comments? How
> can one read the code without whitespace?

This has been discussed before so many times;
It is quite simple: You create two releases,
one for production server-level installation,
another for looking around in the code by potential
(new) coders and the GPL.

>> You will get a performance gain of at least 30%, from loading
>> half the size as needed now.
>
> This is FUD. Where did you hear this?!

It's PHP we're using here, right? For god's sake,
learn something about it before you bash it like this.
You can notice the difference even when using a simple
test.php file with some random processing code in it.

> If you want to speed up your php engine, simply use a
> cache/accelerator.

Now there's some logic; Buy larger harddisks because
you want to stack your drives with shit you'll never use.
Buy more memory because you use software that needs it
because it's being released with huge amounts of useless
code in it. Use extra software and cache memory if you
want to have speed.
Man, this so lacks the historic knowledge of essentials
of good computer code. The more software you will use
to accomplish a task, the more chances you will have
that things will go wrong. The more software you need
to stack on top of each other, the faster your
security and stability will go down the drain.

Last but not least, as mentioned before by others,
this 1.2.7 is not to be released as a stable version.
It simply blows, as far as I've experienced thus far.
read_body.php is full of erratic code now, and
that's to name just one. Please, if you want to
come across as people caring for good coding
(which can be achieved with the GPL system),
then wait for a stable release until it deserves
the title. The way it is done with SM is not
very professional in my opinion. Not even close
to how they do it with FreeBSD stable releases.
-- 
J