On 8 Feb 2008 at 10:31, Devin Meade  wrote:

> Just remember it's not a secure solution. The user must be able to edit 
> this file.

Good point.  I forget, can users interrupt the login xcript with Ctrl-C/Ctrl-
Break or is that not allowed?

FWIW here's a batch I've used for a while to log reboot history on client 
machines.  Could be tweaked trivially to create a login log.

@echo off
:: BootHist.CMD ... stores boot history on Win2000
  if not exist c:\backups\nul md c:\backups
  For /F "Tokens=2" %%I in ('Date /T') Do Set dd=%%I
  For /F "Tokens=*" %%I in ('Time /T') Do Set tt=%%I
  echo %dd% %tt%: %1 %2 %3 %4 %5 %6 %7 %8 %9 >> c:\backups\boothist.log
  set tt=
  set dd=

If you need to email logins to prevent users from editing the login log, just 
use BLAT (command line mailer).

--
Angus Scott-Fleming
GeoApps, Tucson, Arizona
1-520-290-5038
+-----------------------------------+




~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to