========================================================================= Date: Sat, 30 Nov 1996 00:16:11 -0500 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: "Diaa m . mohamoud Ali , MD" Subject: Re: AOLSERVER Digest - 24 Nov 1996 to 29 Nov 1996 hi folks : it seems to me that i am the only computer ignorant among all of you since this is the case , well ineed your assistance. i have a page address is : http://members.aol.com/hebahd/index.html now this page id for my office overseas i have no idea how to tell if some one is visiting this page or not .?????????? then the second thing is there away to have a sort of counter to let me now what is going on ? i thank you all for your future reply Diaa M ========================================================================= Date: Sat, 30 Nov 1996 12:58:58 +0100 Reply-To: ray@carpe.net Sender: Web Development with AOLserver From: Ray Davis Subject: Re: AOLSERVER Digest - 24 Nov 1996 to 29 Nov 1996 In-Reply-To: Automatic digest processor's message <199611300503.AAA09138@services.web.aol.com> of Sat, 30 Nov 1996 00:02:42 EST. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii > On Wed, 27 Nov 1996, Marco Coletti wrote: > > AOLserver 2.1 on Windows NT 3.51 sp4 on P166 64 MB RAM > > > > Every midnight my virtual server eurofin21 attempts to rename access.log and > > open a new access.log. > > > > Excerpt from server.log: > > > > [27/Nov/1996:00:00:00 +0100][96.105][-Scheduler-] Error: > > AccessLog(eurofin21): > > rename(e:/AOLserver/servers/eurofin21/modules/nslog/access.log, > > e:/AOLserver/servers/eurofin21/modules/nslog/access.log.96-11-27-00:00) > > failed: Invalid argument(22) > > > > I'm pretty sure that ":" is an invalid character for filenames on NT > > filesystem, so this appears to be a bug in AOLserver. > > > > Can someone confirm that? > > Yes, it does appear to be a bug in the server, and I have reported it as > such. The extension that is used for the log file rolover is configurable in http://:9876/NS/Setup/Module/server1/nslog in the variable "RollFmt". At least in the Unix version of 2.1... Cheers, Ray ========================================================================= Date: Sat, 30 Nov 1996 02:30:47 -0600 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: Vojislav Lalich-Petrich Subject: Re: AOLSERVER Digest - 24 Nov 1996 to 29 Nov 1996 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hello Marco, Not sure if it is a bug but the way to fix it is to go to your log module and change the format you want the log file to be (re)named on rollover (i.e. take out the time part). The name will then be valid Best regards, Voja. Date: Wed, 27 Nov 1996 13:32:46 +0100 > From: Marco Coletti > Subject: BUG in renaming access.log > > AOLserver 2.1 on Windows NT 3.51 sp4 on P166 64 MB RAM > > Every midnight my virtual server eurofin21 attempts to rename access.log and > open a new access.log. > > Excerpt from server.log: > > [27/Nov/1996:00:00:00 +0100][96.105][-Scheduler-] Error: > AccessLog(eurofin21): > rename(e:/AOLserver/servers/eurofin21/modules/nslog/access.log, > e:/AOLserver/servers/eurofin21/modules/nslog/access.log.96-11-27-00:00) > failed: Invalid argument(22) > > I'm pretty sure that ":" is an invalid character for filenames on NT > filesystem, so this appears to be a bug in AOLserver. > > Can someone confirm that? > > > -= MarCo =- ========================================================================= Date: Wed, 4 Dec 1996 15:51:56 -0500 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: Dave Alden Subject: Re: Recursion in shtml (followup question) ---Eric Klein wrote... >For the time being at least, AOLserver doesn't support recursive >server parsed html. Are there plans to support this in the (hopefully near) future? I've got several users who use this feature throughout their pages, and they're fighting our switchover to AOLserver. :-( ...thnx, ...dave alden ========================================================================= Date: Sat, 30 Nov 1996 13:37:18 -0500 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: John Baldwin Subject: Re: Unrelated to AOLServer, but a real nightmare Comments: cc: Wendy Liu - Infowave Customer Support Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi Wendy, The problem you have is an anoying one and may require a bit of legwork to track down. Put on your infinite patience cap and have a go. Before tracking down an admin, be prepared. Organize all of your information carefully. Keep _detailed_ records. Save your server and security logs, if your system makes them. Save the offensive meesages! If this situation really gets out of hand and you have to resort to law enforcement agencies, or legal recourse, this will be invaluable. Also check your system's time of day clock very carefully. If it is off by more than a few seconds, make note of that. I run a SNTP client to keep my servers accurate to about one second. Doing this makes it much easier to coordinate my logs against those of another system. There are a couple of tools to attempt to track down a system administrator, given only an IP number. The most useful one I have found is nslookup, a tool for making pointed inquries af DNS servers. The second one is the registration information at InterNIC (the USA agency handling top level DNS registration info; other countries have similar agencies.) There is at least one DNS entry, and probably two for the culprit. The first is the reverse lookup record for the offending IP number. If the IP number were 199.22.33.44, ask your normal DNS server to do a lookup on 44.33.22.199.in-addr.arpa. This gets you NS records pointing to the machine(s) holding the records for that IP# and also a PTR record (we hope) that gives the name of the machine used in the crime. Now make an inquiry of the first machine mentioned in the NS records. Ask for all records for 33.22.199.in-addr.arpa. The first item in the SOA record there will contain an e-mail address of someone responsible for that ip# (if it says administrator.foo.bar.com, the e-mail is administrator@foo.bar.com.) If you got a PTR record for the culprit, there is more to do. Ask your normal DNS server to do a lookup on the name in the PTR record (if things are not screwed up, you should also get an A record with an IP number that matches your orginal info.) This gets you NS records pointing to the machine(s) holding the records for that DNS zone. Now make an inquiry of the first machine mentioned in the NS records. Ask for all records for the culprit's machine name, leaving off the very first name (if the name was culprit.foo.bar.com, ask for foo.bar.com.) The first item in the SOA record there will contain an e-mail address of someone responsible for that machine (if it says administrator.foo.bar.com, the e-mail is administrator@foo.bar.com.) The last thing is to ask InterNIC about the offender. http://rs.internic.net/cgi-bin/whois will give information about the second level domain. If the offender is culprit.foo.bar.com, ask about bar.com. This will give you a technical or zone contact who can direct you further. I hope these points will come in handy to other members of the list. If anyone has general comments about this procedure, please post to the list. If you have a specific question about your particular situation, feel free to contact me off the list. Good luck, John Baldwin Eastview Media Group Westchester's Web Weavers 350 Main Street Suite 202 White Plains, NY 10601-3607 USA Phone 1-914-684-2468 Fax 1-914-684-2469 http://w-w-w.com At 06:57 PM 11/22/96 -0800, you wrote: >Hi, >I've received good responses from this community before, so I thought I post >a question here, though unrelated to the AOLserver itself. > >Recently, we have a person coming to our website's chat room and started >using really nasty languages, offending everyone. We had stated our ground, >even to the extent of removing this person's comments and usernames time >after time. However, the person keeps coming back using different username. >This person even threatens to put out virus on our system. We know this >person's IP address, and was able to know it's coming off from a school. I >know AOLserver provides ability to block an IP. But that's only a >preventive measure. We want to take a more severe action, such as sending >an email to this school's administration for investigation. Anyone has any >idea how we should handle this? > >Thank you very much, >Wendy Liu >InfoWave Communications Corp. > ========================================================================= Date: Sun, 1 Dec 1996 18:26:18 +0100 Reply-To: ray@carpe.net Sender: Web Development with AOLserver From: Ray Davis Subject: http:///NS/Db/GetCustomizeTableForm2 I do not see a column for Create/Drop index on each column. Where is it and/or how can I create an index on certain columns? Yes, ExtendedTableInfo: On. Thanks, Ray ========================================================================= Date: Mon, 2 Dec 1996 16:49:24 -0700 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: Thorn Roby Subject: Invalid Verisign Certificate Requests ? In-Reply-To: <199612010502.AAA18180@services.web.aol.com> from "Automatic digest processor" at Dec 1, 96 00:01:38 am Content-Type: text I'm having no luck generating a certificate request for Verisign. Solaris 2.5/ AOLserver 2.1 with nsssl.so 1.3. I'm generating a key, then a certificate request. Verisign says they don't care about the capitalization of the Begin New Certificate Request line, just the encoded portion (unlike SSLeay, I think). They also say they've gotten at least one AOLserver 2.1 request that they could decode. Has anyone on the list gotten this to work (or not) ? I used a key length of 1024. -- Thorn Roby troby@carl.org CARL Corporation 3801 E. Florida Ave.,Suite 300,Denver CO 80210 (303) 758-3030 x125 ========================================================================= Date: Tue, 3 Dec 1996 11:12:43 +1100 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: Ben Day Subject: Illustra 2.4 & AOLServer 2.1 on Solaris Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi, I have Solaris x86 runnning with AOLServer 2.1, I am trying to setup the Illustra db.. but it doesn't appear to be able to find a license key. When you run nsql it comes up with: XVL011:license manager: SERVER FEATURE MI_LIB_USAGE: Can't login to miserver can't login to template1 on server default, host jupiter Not currently connected to a database I am using Illustra 2.4 because it isn't supported anymore on x86 solaris, but last I heard AOLServer for solaris x86 was still being made to connect to the illustra 2.4 db... is it something simple I am doing wrong?? I have Solaris 2.5 with all recommended patches from sun, in the license.log file it seems to startup OK, but as soon as you use nsql (the aol version) it says: miadmin@jupiter [0]: No key file "00" in /export/home/miadmin/adm it says anywhere from 2 to 20 of these then: miadmin@jupiter [0]: No key file "11000" in /export/home/miadmin/adm and then back to the first message a few more times Any help would be greatly appreciated! - Ben :) ========================================================================= Date: Tue, 3 Dec 1996 10:27:48 +0100 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: Stefan Arentz Organization: Luna Internet Subject: Building Custom Database Modules Mime-Version: 1.0 Hi, Is there a description available of all the methods that a database driver should support? I got most things working by looking at the postgres example, but a formal definition of result codes and structures that are used by a database module would be very helpful. Regards, - Stefan ========================================================================= Date: Tue, 3 Dec 1996 09:14:59 +0100 Reply-To: dormanns@kzs.hu Sender: Web Development with AOLserver From: Dormanns Marcel Organization: Kossuth Zsuzsanna Tech. Highschool Subject: Re: virtual server stopping also on NT Comments: To: Valter Quenda Valter. We are also running AolServer on NT 3.51 and faced the same problems, virtual servers stopping when reaching the max. number of threads. When I put this question to the list, I got several emails suggesting turning off DNS lookup, and turned out this really solves the matter. Our server is running for quite a while now without any problems and thread cleanup takes place as it is supposed to be. DNS lookup can take place on a number of places, you might have overlooked some. The following is a short list of where I found DNS lookup to take place. I don't assume it's complete, but it will get you started. - Most obviously, nslog. This would be called most frequently so turning this off seems an important measure. - Nsperm, checking access rights based on hostname or domain name. - TCL-scripts and maybe C-modules. This will be a hide and seek job if you have many scripts or custom C-modules. As an example, I wrote a guestbook entry script which adds the form data to an Illustra DB, supplemented with client IP-address and hostname. This will also cause a DNS-lookup. Other examples are things like the sendmail script. IMHO turning off DNS-lookup is not a solution, but a workaround. One would expect that if DNS-lookup times out, the thread would be terminated instead of waiting ad infinitum for a reply. And unfortunately by avoiding DNS-lookup you'll miss a lot, like readable logs for instance, or flexible permissions based on names instead of numbers (that's why they created DNS in the first place). Hopes this info helps you to keep your server running. --------------------------------------------------- Marcel Dormanns, system manager Kossuth Zsuzsanna Technical and High School 6800 Hodmezovasarhely, Kaszap u 29, Hungary Tel. +36-62-341811 Fax +36-62-344884 ========================================================================= Date: Tue, 3 Dec 1996 09:28:25 +0100 Reply-To: dormanns@kzs.hu Sender: Web Development with AOLserver From: Dormanns Marcel Organization: Kossuth Zsuzsanna Tech. Highschool Subject: Re: BUG in renaming access.log Comments: To: Marco Coletti Marco. The problem you described sounds very familiar to me, trapped me too a while ago. You might want to take a look at the setup of your virtual server in http://yourserver:9876/NS/Setup/Module/eurofin21/nslog _or_ NSD.INI - [ns/server/eurofin21/module/nslog] You'll find there a field called RollFmt, which contains a formatting specification for the filename of the renamed logfile. Very well possible that the invalid characters are there. The solution is to change the format specification to something legal for the OS you are running. In my case (NT 3.51) I changed RollFmt to %y%m%d%H%M and everything works fine now. Yesterdays access.log is called access.log.9612020000 Hope this solves your problem too. --------------------------------------------------- Marcel Dormanns, system manager Kossuth Zsuzsanna Technical and High School 6800 Hodmezovasarhely, Kaszap u 29, Hungary Tel. +36-62-341811 Fax +36-62-344884 ========================================================================= Date: Wed, 4 Dec 1996 14:02:22 +0000 Reply-To: Web Development with AOLserver Sender: Web Development with AOLserver From: Reinhard Henning Organization: TCH - Technologie Centrum Hannover Subject: Problem: nsd is allway being killed MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello AOlserver Admins and Developers my first problem: I have a page with a select box and the form is being submited whenever someone clicks on an option. I am using JavaScript: