If the processor is only at 20%, then they should have no problem sitting at the console and adding a line.
But, Windows IIS was nice enough to lock pages, while I was editing pages over smb at a clients site. So unless they've updated IIS behaviors, you need to stop it in order to update the status page.
Log in Response, or actual web page. Both came back.
It was just really really confused. Probably a big cache problem. Some sent a request with a password, bad password. send back reply. keep sending reply back until server realizes it is not the right one, cache new one... now someone sends a password...
* AOL provides the servers, and makes money off the advertising. * MS makes money off the OS. * If MS OS users use MSN Mess, then AOL does not make any money, and for some strange reason, MS still does.
MS pleads, open-source, open-source, but do you see MSN mess source posted anywhere? Do you see MSN mess for other OS's? No MS makes money off the OS.
The yahoo and prodigy made money, but they don't make money from the OS. And at least yahoo's client is not a exact clone of IM 1.0. Hey I tried yahoo's out, and it is really good, and there is a java version for those who want it.
And MSN mess, is a mess. If you install MSN mess, it INTEGRATES ITSELF, by default. Open outlook, and you have opened up MSN mess, without realizing it. Even after you kicked it off the damn taskbar, it still fires up when you fire up outlook. Talk about forcefull.
I have not been able to sign on using AIM for over 30 minutes. I have "not waited long enough to sign back on" (and "had attempted to sign on too many times recently").
Ok, Ok, I was using both programs to see what the fuss was about, but then AIM was the one complaining while both were running.
Re:speculation on why AOL ripped out so much stuff
on
AOLServer Open Sourced
·
· Score: 2
Date: Thu, 24 Jun 1999 22:24:53 -0400 From: Philip Greenspun Subject: speculation on why AOL ripped out so much stuff It is fun to speculate on why AOL ripped out so much stuff from 3.0. Here are my favorites from recent mailing list:
features. I wonder if there are third party licensing concerns or security issues behind these ommisions? Any one of these ommisions would provide a good reason not to move to 3.0 and yet they provide a whole list!
I suspect a lot of code was removed because AOL didn't want it to become Open Source.
I've been working with AOL since December to open-source the thing. Thetruth is much simpler than some of you guys might suppose:
1) they waited for 3.0 to open source the server because they were a bit embarrassed by some of the cruft that had accumulated over four years in Navi/GNN/AOLserver
2) they ripped out a bunch of features because (a) they don't use them on AOL's high-volume sites (like DigitalCity), (b) they complicate maintenance and extension of the server code base, and (c) they think they could be done in modules outside of the server core
This is actually pretty common in the world of complex software. It eventually gets too complex for anyone to understand so people do a leaner meaner rewrite.
Don't cry too hard for your lost feature bloat. Be assured that four years from now AOLserver will be just as bloated with new and even weirder features.
I also know that AOL itself is working on making Tcl 8.1 part of the server. They just couldn't get it done in time and sensibly decided to release an improvement. Jim Davidson, the original NaviServer architect, worked a lot on 3.0. He is a tasteful thoughtful guy and 3.0 is the best Web server for his needs (i.e., heavy and reliable support for Tcl, databases, ADP; clean and fast static file serving; easyconfiguration).
kriston, I thought well of you until I read your reply. You may not have noticed, but I've been advocating AOLserver. Don't flame your advocates.
As I said, it reads like a removed feature list. (config:13 dropped, vs 6 changed, 3 new; DB all removed) You point out that these things can be done, but new things say removed.
I am clueless about the latest version of AOLserver. I handed off the admin tasks to someone who installed apache, because everyone uses it.
Even though AOLpress/AOLserver combination is dead, lets get real. It showed the real potential of the web. In concept, it was the best of breed. In implementation, well...
And creating SSI equvilents in ADP may be basic, but it need to be shown, and not left up to the potential users. Or you will have no users (as will flaming advocates)
Ah, come on, he likes high reliability, and is willing to pay for support. Something that was not available for linux until a couple of months ago (You don't say in a newsgroup, telnet to my site, and see if you can fix it). He'd rather do the apps and hack the web backend.
His writing is never like a manual. It's always flowing. It's more of a diary, than a manual.
First Multithreaded, DB-backed, PUBLISHING SYSTEM
on
AOLServer Open Sourced
·
· Score: 3
Dynamic Page scripting (using a tested language, TCL), Autoindexing, Archiving, with a c-API.
Oh, yea, and the first to use HTTP PUT to create web pages. Using version 2 of AOLpress, the publishing of material to the server was/is transparent. A web server was treated just like a local directory.
Best designed server/web publishing system. It just lost out to money, and bigger development budgets (and a slow browser/publisher). Most of the admin interface was done in TCl, so you could modify it.
I know. The new features reads like a removed features. They dropped the web admin, and the ability to handle page permissions via aolpress (great for novices), and the server-side includes.
And dropped, java servlets, the virtual ftp, aliases And the autodatabase forms.
Damn, what's left. I guess the high load server.
Now the question becomes does it serve STATIC pages fast with its new FASTPATH module?
Programmers have been getting lazy. Digital assistants have no hard drives and they have programs that are functional. They programs are not as bloated as the ones on the desptop.
A nice laptop with 64 magabytes of memory, and half a gig of solid state disk would be enough. Espsically, if the VM scheme just mapped programs to the memory. And need a game, pop in a 64 meg solid state floppy with the game on it.
Now all we need is for reasonalbly prices flashdisk memory.
Slashdot Mirror
Never said that it was the version on the latest CD.
Enable the guest account.
Oops wrong OS.
Brute force a jcarr is a better solution.
Services froze.
For three hours this morning. 6:04-9:20. No guest page entries.
Not delivering web pages when all it does is deliver web pages is pretty close to a crash.
Seems to ignore the real problem. How much is it not serving pages?
And if the logs can be sent to another computer (perhaps over a second interface), why does one need to stop the computer to analyze logs?
If the processor is only at 20%, then they should have no problem sitting at the console and adding a line.
But, Windows IIS was nice enough to lock pages, while I was editing pages over smb at a clients site.
So unless they've updated IIS behaviors, you need to stop it in order to update the status page.
Nope, it's you must have a high availabilty, because you need to come and reboot the server when it is not responding.
MSN Web Communities
Anyone want to open up the /. community, and have Everybody load up on a free 30 megabytes, courtesy of MSN.
a good filter and firewall
But /. is dogging it too.
No response,
slow response.
You can hit the MS box?
I have not been able to since this morning (PDT)
9:46 PDT
Seems to have dissappeared.
Tried to see what the first messages in the guest book were (end>). Have not heard from it since.
It sent a response back. Must have been running.
Log in Response, or actual web page. Both came back.
It was just really really confused. Probably a big cache problem. Some sent a request with a password, bad password. send back reply. keep sending reply back until server realizes it is not the right one, cache new one... now someone sends a password...
No, the custom user pages are just broken, over simplified.
I've got 174 comments showing. If you click on the item, you get the real count.
No explanation for the failed user log in messages from the WEB SERVER.
Actual message returned in netscape:
Logon failure: user not allowed to log on to this computer.
(Some router loops happening and when I did hit the server in the 'appropriate" browser)
- --------------------------------
The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.
-----------------------------------------------
Please try the following:
Open the www.windows2000test.com home page, and then look for links to the information you want.
Click the Refresh button, or try again later.
Click Search to look for information on the Internet.
You can also see a list of related sites.
HTTP 500 - Internal server error
Internet Explorer
* AOL provides the servers, and makes money off the advertising.
* MS makes money off the OS.
* If MS OS users use MSN Mess, then AOL does not make any money, and for some strange reason, MS still does.
MS pleads, open-source, open-source, but do you see MSN mess source posted anywhere? Do you see MSN mess for other OS's? No MS makes money off the OS.
The yahoo and prodigy made money, but they don't make money from the OS. And at least yahoo's client is not a exact clone of IM 1.0. Hey I tried yahoo's out, and it is really good, and there is a java version for those who want it.
And MSN mess, is a mess. If you install MSN mess, it INTEGRATES ITSELF, by default. Open outlook, and you have opened up MSN mess, without realizing it. Even after you kicked it off the damn taskbar, it still fires up when you fire up outlook. Talk about forcefull.
I have not been able to sign on using AIM for over 30 minutes. I have "not waited long enough to sign back on" (and "had attempted to sign on too many times recently").
Ok, Ok, I was using both programs to see what the fuss was about, but then AIM was the one complaining while both were running.
http://photo.net/bboard/q-and-a-fetch-msg.tcl?msg_ id=000Vt4
Date: Thu, 24 Jun 1999 22:24:53 -0400
From: Philip Greenspun
Subject: speculation on why AOL ripped out so much stuff
It is fun to speculate on why AOL ripped out so much stuff from 3.0.
Here are my favorites from recent mailing list:
features. I wonder if there are third party licensing concerns or security issues behind these ommisions? Any one of these ommisions would provide a good reason not to move to 3.0 and yet they provide a whole list!
I suspect a lot of code was removed because AOL didn't want it to become Open Source.
I've been working with AOL since December to open-source the thing. Thetruth is much simpler than some of you guys might suppose:
1) they waited for 3.0 to open source the server because they were a bit embarrassed by some of the cruft that had accumulated over four years in Navi/GNN/AOLserver
2) they ripped out a bunch of features because (a) they don't use them on AOL's high-volume sites (like DigitalCity), (b) they complicate maintenance and extension of the server code base, and (c) they think they could be done in modules outside of the server core
This is actually pretty common in the world of complex software. It eventually gets too complex for anyone to understand so people do a leaner meaner rewrite.
Don't cry too hard for your lost feature bloat. Be assured that four years from now AOLserver will be just as bloated with new and even weirder features.
I also know that AOL itself is working on making Tcl 8.1 part of the server. They just couldn't get it done in time and sensibly decided to release an improvement. Jim Davidson, the original NaviServer architect, worked a lot on 3.0. He is a tasteful thoughtful guy and 3.0 is the best Web server for his needs (i.e., heavy and reliable support
for Tcl, databases, ADP; clean and fast static file serving; easyconfiguration).
Philip
kriston, I thought well of you until I read your reply. You may not have noticed, but I've been advocating AOLserver. Don't flame your advocates.
As I said, it reads like a removed feature list. (config:13 dropped, vs 6 changed, 3 new; DB all removed) You point out that these things can be done, but new things say removed.
I am clueless about the latest version of AOLserver. I handed off the admin tasks to someone who installed apache, because everyone uses it.
Even though AOLpress/AOLserver combination is dead, lets get real. It showed the real potential of the web. In concept, it was the best of breed. In implementation, well...
And creating SSI equvilents in ADP may be basic, but it need to be shown, and not left up to the potential users. Or you will have no users (as will flaming advocates)
too bad the story wasn't posted in the middle of the day. Could have asked to have the web logs looked at.
Ah, come on, he likes high reliability, and is willing to pay for support. Something that was not available for linux until a couple of months ago (You don't say in a newsgroup, telnet to my site, and see if you can fix it). He'd rather do the apps and hack the web backend.
His writing is never like a manual. It's always flowing. It's more of a diary, than a manual.
Dynamic Page scripting (using a tested language, TCL), Autoindexing, Archiving, with a c-API.
Oh, yea, and the first to use HTTP PUT to create web pages. Using version 2 of AOLpress, the publishing of material to the server was/is transparent. A web server was treated just like a local directory.
Best designed server/web publishing system. It just lost out to money, and bigger development budgets (and a slow browser/publisher). Most of the admin interface was done in TCl, so you could modify it.
I know. The new features reads like a removed features. They dropped the web admin, and the ability to handle page permissions via aolpress (great for novices), and the server-side includes.
And dropped, java servlets, the virtual ftp, aliases
And the autodatabase forms.
Damn, what's left. I guess the high load server.
Now the question becomes does it serve STATIC pages fast with its new FASTPATH module?
How about a test where half the load is web serving, and half the load is file sharing?
Better yet, how about a test which runs for 1, 2, 4, 8 and 24 hours, with these test bed loads. And say 1000 random static web pages.
Let's see how long it takes for each web server to decrease due to memory leaks, and other problems.
Programmers have been getting lazy. Digital assistants have no hard drives and they have programs that are functional. They programs are not as bloated as the ones on the desptop.
A nice laptop with 64 magabytes of memory, and half a gig of solid state disk would be enough. Espsically, if the VM scheme just mapped programs to the memory. And need a game, pop in a 64 meg solid state floppy with the game on it.
Now all we need is for reasonalbly prices flashdisk memory.