different shells

[Andrew Perrin - Demography]

Actually, we have perl-win32 loaded on a samba share (\\population\perl),
and it works fine for each NT machine to run perl scripts; that keeps us
from having to install perl on each pc.  Also, perl's include structure is
flexible enough that it finds installed modules in the same hierarchy -
very clean.

Cheers-
Andy

---------------------------------------------------------------------
Andrew J. Perrin - aperrin at demog.berkeley.edu - NT/Unix Admin/Support
Department of Demography    -    University of California at Berkeley
2232 Piedmont Avenue #2120  -    Berkeley, California, 94720-2120 USA
http://demog.berkeley.edu/~aperrin --------------------------SEIU1199

On Wed, 1 Sep 1999, Stephen Waters wrote:

> Joel Miles wrote:
> > 
> > > Well, with some REALLY complex scripting, you might be able to accomplish
> > > that.  You know, parse win.ini, check to see what the value of the SHELL
> > > line is, compare that to what it should be for that user.  If it's
> > > different, replace it and reboot, if it's the same, then just log them in.
> > > Greg
> > 
> > Do you know where I could get some help in writing this (also, what language
> > would I use, Perl?)?
> 
> if you have perl for win32 on all of your workstations, this might be
> workable. otherwise, you should probably use a .bat file with some
> decent text manipulation utilites (kind of a "cat win.ini |grep shell"
> bash comparison thing), though i'm not a .bat genius.
> 
> just a thought,
> 
> -stephen
>