Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - RobertM

Pages: 1 ... 119 120 [121] 122 123 ... 126
1801
General Discussion / Re: Norman No Longer Supports OS/2
« on: 2007.09.06, 03:36:05 »
In addition, it might be able to be (easily) linked to the network subsystem. It does support scanning streams coming in/going to a port and then providing the mechanism to route the scanned data to the port.

1802
True... but I dont know how his network is segregated or set up...

1803
Hmmm... or a cable looped on a hub/switch... forgot about that.

I've seen this problem besides on the first TCPIP32 stack... it was caused by having two (or more) switches with 2 cables going to them (effectively creating a sort of infinite loop)... eventually the stack bogs or shuts down...

1804
General Discussion / Re: Norman No Longer Supports OS/2
« on: 2007.09.04, 23:29:34 »
Have you/can you compare ClamAV to Trend Micro PC-CILLIN and Windows Defender?
Also, how easily does ClamAv work under OS/2? Is there a PM interface, or only command-line?

I dont know of a PM interface for ClamAV, but one would be pretty easy to write... perhaps not a neat solution, but doable.

I don't know how it compares to Windows Defender (as I am not sure what SpyWare detection/protection ClamAV has), but Windows Defender is frequently rated as one of the worst for Windows (even by magazines that MS has large financial interests in). ClamAV's ratings seem to vary from OK, to really good...

1805
Awesome!

As you said, I would prefer to implement the script first as a quick fix so we don't have to monitor these OS\2 boxes after hours. But it sounds like you are up for a challenge and it may be. I will setup a time to work with you on the fix and maybe we can solve the riddle.

Keep in mind that we are not able to provide consulting fees other than a six pack and some cheetoes. LOL.

Thanks again

Dave

Don't worry Dave, like you will find of many of my brethren (and sisthren... ;) ) here, we just like to help out when we can... I've been very fortunate to be on the receiving end of that help numerous times, so I try to pay it forward where I can! Also, after experimenting with other Operating Systems - and sticking with Warp because of how it compares as a server... it frustrates me seeing problems like what you are experiencing (and like I have sometimes experiences as well) when I know the OS is capable of faaaar more - with less issues than anything else I have tested. Heck, after 15 years of running OS/2, I am still learning about what it CAN do, and finding that in the networking world, there is little it CANT... I just found out recently that it can be set up to do NAT - along with DHCP, DDNS and so much more... sometimes figuring it out or fixing an issue can be kinda daunting (still trying to figure out how to properly do NAT - and IBM's manual on it is toooooo thorough... a whopping 600 pages if memory serves.

So, to sum it up... not a problem at all... we'll get your machine automatically dealing with the issue first, then we'll get the issue resolved so it never happens again.

Oh... as a side question... are you running NetBIOS, or NetBIOS over TCPIP on the machine? If you aren't sure, I can tell you how to check...

-Robert

1806
Update, apparently a group of IBM experts could not narrow down this problem. All of the lastest IP stacks were upgraded to the latest version. The final statement was "Just reboot."

It IS possible that if JUST the TCP/IP stacks were upgraded, it could either make the situation worse or do nothing to alleviate it... IIRC some of the TCP/IP fixes had pre-requisites (such as updating MPTS, and/or installing fixpacks BEFORE updating the TCP/IP stack).

1807
Hi Dave,

I will work on completing the script... though if you and your team are willing, I'd also like to try to resolve this problem. I've sent you a private message with my direct email address with requests for more information if you want to try to resolve this.

Basically, the problem you are having shouldn't be happening. I've run many servers on different OS's and found OS/2's stack to be one of the most reliable - even under horrendously heavy load. I just completed another load test on my Netfinity machine and shoved 100 simultaneous connections down it's throat totaling 140,000 connections when the test was done... neither the machine nor the TCP/IP stack cared in the least bit. All of the servers my company installs are running OS/2 or eCS, and after gigabytes worth of TCP/IP traffic and months of uptime, the only thing I have to go out to do at the clients' are clean dust from the machines. Some of my older machines were as "underpowered" as PII 300's that handled over 200,000 TCP/IP requests a day without issue.

So... basically what I am saying is (as far as TCP/IP is concerned) you should probably never have to reboot your machine. Ever.

So, what I propose is the following... I'll get the script done as a short term fix, and if you are willing, help you track down and resolve the issue so the script later becomes a non-issue.

-Robert

1808
Hey Dave,

OK... for the REXX thing (you definitely HAVE Rexx... it's just a matter of which one you are using - though on Warp 4 I dont think it matters)... all you need to do is open a command window and type the following:

Quote
switchrx [ENTER]

It will come up with a few lines of info... hit "N" [ENTER] when it asks you to type yes or no... but read the screen... it will say something like this:

Quote
This program will now replace the current Classic REXX interpreter of OS/2
with the Object REXX interpreter.

Enter 'Y' to continue, any other input will cancel this procedure.

The first line is the relevant one... tell me what that says...


Now, as for the machine and setup itself... you can grab OS/2 Warp 4 disks pretty cheap when you can find them on eBay... you are apparently running standard Warp 4.

There are a bunch of fixes for it, including a new TCP/IP stack... they are mostly all rolled into one package. You can grab Warp 4 FixPack 15 various places on the Internet and installing it is as easy as following the instructions. Then you can upgrade the TCP/IP stack as well - also pretty easily. I can help you through that process if you like - it will probably alleviate all of your issues... and as a backup I can write something to reboot the machine (and even do fail/fallover to another if you have a second machine that can take over). Keep in mind that if you try using a second machine as a backup, you have to be mirroring the data to it so that both machines keep current... without knowing more about your setup, the method of doing that would vary.

Let me know, and I will come up with something... I have a test script in the works. I'll adjust it as necessary.

1809
Applications / Re: MySQL5 and RxSQL Test
« on: 2007.09.01, 05:29:37 »
Hey all (and especially Paul Smedley):

I've done some testing using RexxSQL and MySQL v5...

Doing a load test on reads at 22 queries per second via the following method:
  • Netfinity 7000 M10 Quad 550 XEON 4GB RAM
  • Lotus Domino GoWebserver v4.6.2.8
  • MyDB with 74,000 plus records
  • wGet controlled via REXX script on another machine.

The REXX script reads in from the local MySQL copy all 74,000 records to search (20 different processes each retrieving different subsets of the DB). Each of the 20 processes then uses wGet to call a script on the server with parameters for the query and then writes the response on the workstation. Thus I am doing 20 concurrent calls to Domino Go, which is then running the web script and calling the database 20 times at once to read the results. Since each of the 20 is pulling from different places in the DB (Process 1 is getting record 1, then 2, then 3; while simultaneously process 2 is getting record 1,000 then 1,001 etc) MySQL needs to be jumping back and forth 20 times for each set of simultaneous requests.

Absolutely no problems (with CLASSIC Rexx).

The only issue I have had is that ORexx crashes if I try this (but there are a lot of other issues with ORexx as well - so I am 100% sure the issue is entirely ORexx).

I will do further testing:
- Running 50 queries simultaneously
- Using inserts and updates simultaneously during this test at a later time... but so far so good...


Thanks Paul! Nice job!  :)

-Robert

1810
Sorry Dave,

I got a little busy with some work projects, but am looking into it.

Can you please provide me with the following info...
  • What version of OS/2 are you using on the machine (and test machines) in question?
  • Have you uprgraded or installed fixes for any of the following... TCPIP, REXX, networking in general?

OS/2 (as of WSeB) had a "bug" in the original TCP/IP stack (which was fixed in later releases such as WSeB CP2 and CP2PF) that would cause the stack to lock and no longer route or respond to TCP/IP traffic if the machine received a certain type of attack/packets (I dont remember the specifics of the cause, but this might be your issue).

I run WSeB CP2PF (and have run the earlier releases) and once I switched to CP2 and CP2PF (or applied the TCPIP fixes to WSeB original) never ran into the problem you are describing again. I've run multiple websites from the same box - which handles ooodles of traffic (lots too! ;) ) and not experienced any issues since applying the fix or switching to a later release of WSeB.

I *had* a reboot tool I used to use (but can't find it - will rewrite it for you)  that I used for that and other situations... what I did was assign a machine an IP like this... XX.XX.XX.100, and then an alias on the same card for XX.XX.XX.150 - my second machine was XX.XX.XX.101 with no alias. If the second machine saw no response (via pinging the first) on IP XX.XX.XX.150, it would alias itself to that address and assume the functions of the first machine. The first machine, when rebooted would tell the second machine "I'm up... un-alias that IP" and then check to see when the 2nd machine dropped the alias. It would then alias itself to the .150 address and resume handling traffic.

I should be able to re-write that script so that it checks any other machine or location on the net, and failing a response, initiates a reboot. This can be handled a few different ways... either a simple ping utility that times out properly (some dont seem to, and just hang waiting for a ping response) or using something like wGet or Curl to retrieve a small page from someplace with a timeout - and if that timeout occurs, initiate a reboot.

So that brings up the next question... do you have a webserver on another machine that has a small page (or that you can create a small page on) that the script can attempt to access? If so, I can have a script written pretty quickly... it would use some custom stuff in REXX and the GetHTTP library (or wGet) from Hobbes.

But that brings up one final question... what version of REXX are you using? (ObjectREXX or Classic REXX)? ObjectRexx eventually crashes the REXX.DLL after an app is running for a long time using Stem Arrays - there is a better version on Hobbes that doesn't crash as quickly - but you may not need it depending on what version of Warp you are using (WSeB CP2PF and eCS 1.X DO show this problem - but unless you are using lots of REXX scripts that create a lot of Stem Arrays, you should have that problem... and if you are running CRexx and not ORexx, you wont run into the problem at all).

-Robert

1811
I could... but I am not telling you how!!!

No, just kidding... give me a few (hours) and I will try to put together something for you and post it...

-Robert

1812
Applications / Flash 9 Player for OS/2?
« on: 2007.08.27, 08:09:07 »
Hey all, I just noticed that Flash9 came out for Linux...

http://labs.adobe.com/downloads/flashplayer9.html


So, I was wondering if maybe some people could comment on this:

How difficult is it to port Linux apps to OS/2?

If it isnt usually that difficult, do you think that perhaps with a little guidance Adobe might be convinced to port Flash9 from their Linux version to OS/2 - or that they might let someone here (like Paul) port it for them?

-Robert

1813
From some of the ALSA project Docs:
Quote
Intro to dmix

The dmix virtual sound mixing device is a plugin to ALSA which takes multiple sound streams and mixes them into one virtual stream which a lower-end card can handle. Any card which does not support multiple streams or hardware mixing of sounds must use this plugin to take full advantage of ALSA and its capabilities.

In most cases, dmix will be automatically configured for ALSA 1.0.9 RC2 and above. There is no need to adjust the default configuration for the basic user and it should work transparently with your system.

Which means, outputting multiple streams that is supported in hardware seems to be supported by the drivers... using DMIX seems to be the method for older sound cards that dont support it - but requires DMIX-aware-apps... or in OS/2 perhaps by registering DMIX as the WAVOUT device intercept or mixer...

So... I dunno...


1814
Well, and possibly a third (at least for later)... for cards that only support one audio stream - now that CPUs have become far more powerful, it seems that eventually we (the OS/2 community/developers) will hopefully be able to have a driver solution that allows mixing of any sound streams (as some or most Windows drivers do - using the CPU to do the mixing via the driver before the mixed, single sound stream is sent to the card).

I'm guessing the MMOS2 subsystem should be able to handle that as well... but with a little more work... there are already programs - and DLLS,  that do similar things... for instance, the CrossFade plugin for PM123 (used to) do that (dont think it is compatible with the newest PM123 release - but that is really irrelevant) - and there are also apps that did multiple WAV file - single output stream mixing.

Well, one step at a time I guess... though I am curious if for the sound cards that dont support multiple streams, if the answer would be simply to create another sound device instance that uses such technology, and then outputs the stream to the main (real) sound device instance... much like some of the virtual device drivers that intercept keyboard input, play with it, and then pass it on to someplace else...

-Robert

1815
There seems to be a GenMac driver for the Marvell chipset, but I dont know which chipsets it supports (and personally would prefer a native driver anyway)... it seems to be in GenMac v2.04rc1

-Robert

Pages: 1 ... 119 120 [121] 122 123 ... 126