also, re: times two - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - re: # 1 Posted by: Rick Faurot In reply to: IH Admin [Matt] My theory is there is a scheduled task set up in SI's software that kicks in at 10:15 EST every day. Could be a mistake by someone at INSP or it could be a sabotage effort or a trojan. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - re: # 2 Posted by: Rick Faurot Solution is to read every line of code and look for references to time of day. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Matt,
Everytime Si's source code was added, deleted, or modified to, there should be a record in a log book as to the who & why.
If not then backup copies of Si's source code saved on tape or disk months prior to when the iHub initiative to buy Si and most likely fire & terminate all Si employees can be loaded so that each and every source code module can be comparied to what now exist and locate as Rick Faurot pointed out, a possible sabotage that i think is very possibe using as he noted, a time reference to kick in after a date like June of now.
I'am sure Rick didn't mean "read every line of code" since he should be very aware that many available programs have existed since the beginning of computers to accomplish in seconds what would takes BobZ a zillion hours and days or weeks to physically look at.
My approach is as stated above, get a backup copy of the sources to build Si, run a program to identify differenced for each module used in the build, and then look at what was changed. This can be done inside a 24 hour day and i have already assumed that BobZ already did this last week when the slowness started and keep on occuring. If not, poor.
The other possibility i think you mentioned: re: Unix has all kinds of quirky processes... Is that the operating system was hacked. If so then a binary compare to a saved one that represents what is run prior to the execution of Si is needed. Windows 3.1 has something call .dll dynamic link libraries that are not build into the operating system, but are run real time when needed. This allows changes to the OS be made after it is build and running, and one can actually debug a user program and enter and make changes to the memory version of this .dll in the debugger i think, as its been a long time since i did that, but know i can go inside it and look at the code. I have heard that UNIX can be hacked, and you and BobZ have been foolish if not already requested the help of your members in a public manner. Sure, you both are extra too busy, but a solution might already been had if another like Profile for echarters http://www.investorshub.com/boards/profile.asp?User=17760 was brought into this as a public Q & A about help needed.