Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!vtserf!creatures!davism
From: davism@creatures.cs.vt.edu (Mat Davis)
Newsgroups: comp.unix.aux
Subject: Re: Mac OS Viruses under A/UX 2.0
Message-ID: <403@creatures.cs.vt.edu>
Date: 30 May 90 18:46:01 GMT
References: <402@creatures.cs.vt.edu> <26640B70.A8A@intercon.com>
Sender: usenet@creatures.cs.vt.edu
Reply-To: davism@creatures.cs.vt.edu (Mat Davis)
Organization: Virginia Tech Computer Science, Blacksburg, VA
Lines: 14

In article <26640B70.A8A@intercon.com> amanda@mermaid.intercon.com (Amanda Walker) writes:
>In article <402@creatures.cs.vt.edu>, davism@creatures.cs.vt.edu (Mat Davis)
>writes:
>> As a last resort, we *could* create a new, clean system folder each time the
>> 'guest' user logs in, but that will slow the login process considerably.
>
>You could do it when the previous person logs off, which would move the time
>consumed to the relatively "invisible" period between users...

The problem with cleaning out /users/guest when someone logs off is that 
people occasionally forget to copy files to diskette before logging out.
By only deleting the files when 'guest' logs in, an operator can log in and
save files if someone realizes that they have just logged out without saving
them.