WildCajun: Look out :)

[Joel Kleppinger]

Figured it was fair enough to give you advance warning. No more will be said, but if all goes according to plan, good things will happen in a month or so.

I'm gunning for ya... there ain't no free ride at the top around here. http://sysopt.earthweb.com/forum/smile.gif (just ask Highlander or Cwizard)

Don't go getting complacent or.... http://sysopt.earthweb.com/forum/wink.gif

[WildCajun]

All RIGHT! Let's get ready to rumble! Joel, you wouldn't by anychance have an NT network where you could do some experimentations for me would you?

I would like to set the client to run in the config.pol file for win9x clients with local buffers and a shared .exe and pause file ( VERY IMPORTANT ) this would enable me to run the client on well... clients and maintain central control that could easily be reversed if problems were encountered.

If I can work through these issues, I may be able to produces blocks the likes of which DNET has never seen! Okay maybe that's a bit of a stretch, but from estimates 250K / day. And NO that is not a typo.

I just haven't found the time to test this method out yet.

WildCajun

[Joel Kleppinger]

Man... here I go hinting at making life interesting for you and you just have to go and blow me out of the water. http://sysopt.earthweb.com/forum/smile.gif

Well, I have a little 7 machine workgroup network set up for testing/work purposes.
2 Mandrake 7.0 machines
2 Windows 2000 machines
a WinMe box
and 2 Win98SE machines.
It's NOT on a domain, if that matters.

I think I understand the theory... except for the pause file. But yes, I'm willing to help with some testing if you need it.

[izzzy12k]

Please...

Simply flash your headlights once, and I will gladly move on over to the right lane so you guys can pass. http://sysopt.earthweb.com/forum/wink.gif

-Izzy

[WildCajun]

Not a done deal yet. I talked it over with Bhphantom before when I was with T.A. but the site is remote so the ability to shut it down if problems arise is a must.

It can't be nearly as difficult as trying to install the client on Chinese 95.

Eventually at stake would be 2200 P2-400 averageing 8-10hrs / day. Obvioulsy I am NOT going to go to each desktop to install the client.

But this is JOEL'S Thread and my post was not to steal his thunder but to incourage him to force me into the right lane also.

[This message has been edited by WildCajun (edited 09-22-2000).]

[This message has been edited by WildCajun (edited 09-22-2000).]

[Joel Kleppinger]

Hehe... I was just giving you a hard time. http://sysopt.earthweb.com/forum/smile.gif After all, I have endevored not to let you pass until at least New Years 2001... and that's WITHOUT doing things like kicking the network cable off your Net connection so you can't flush. http://sysopt.earthweb.com/forum/wink.gif

That is quite a site. Reminds me of when I used to work for Hoescht Marion Roussel.. we had about 1500 P2 266s and 800 P233MMX laptops. Oh, how I remember salivating over that. http://sysopt.earthweb.com/forum/wink.gif

But you want to control each individual client remotely, if necessary? That seems like it's going to be incredibly difficult. Or do I have you wrong?

[WildCajun]

Way Wrong! I would never want to control the clients individually. The plan is

put the .exe and .ini in the \netlogon$ share of the file server(s). Modify the Config.pol file to add runserves reg entry for the client. The client should then run with the ini settings. The pause file ( should have read quit file ) would be an emergency panic button should the help desk be flooded with calls say program X won't run anymore. Config.pol file should be easier than modifying login scripts.

[Joel Kleppinger]

Well, the panic button part will definitely be the hardest part of it. You really need some sort of way to have the server connect to every client and run "dnetc -shutdown" on each computer, and then pull the dnetc startup from the server. I'm not really sure how to do this remotely without some sort of telnet access.

If you do a panic kill, you may also want to do a flush first and then kill so all the blocks that have been done still count. That will also be challenging.

[LeBlatt]

The panic button should be easy to implement.
by default the client exits if the presence of a file named 'exitrc5.now' is detected in the client folder (takes a few seconds).
If the file is present when the client is to start, it just doesnt.
The name and location of the exit file can be overriden in the client config.

[Joel Kleppinger]

Interesting news. I wasn't aware of that feature. Thanks, LeBlatt.

Then if everyone has the same shared drive, just creat and exitrc5.now on that drive (assuming the client is pointed to look there) and all cracking ceases.

Mad props out to LeBlatt. http://sysopt.earthweb.com/forum/smile.gif