$site_db

• Date: Mon, 1 Jan 1996 17:49:53 PST
• From:
  Judy Anderson <yduj@cs.stanford.edu>
• cc: moo-cows.PARC@xerox.com
• In-Reply-to: "Jacqueline Hamilton's message of Sun, 31 Dec 1995 22:14:53 PST <Pine.HPP.3.90.960101001307.2411A-100000@fohnix.metronet.com>"
• Posted-Date: Mon, 1 Jan 1996 17:49:53 -0800 (PST)

   Date: Sun, 31 Dec 1995 22:14:53 PST
   From: Jacqueline Hamilton <kira@metronet.com>

   Is there any real purpose for $site_db?  It's like, using up over 400K in 
   my MOO, and I want to recycle it.  Or at least, dump it out, since memory 
   is at such a premium right now.  Wondering what all really uses it.

$site_db is used to track all logins by all users---"@@who from" uses
the information herein.  This can be useful in helping to identify
crackers and other troublemakers.  The one on LambdaMOO is kind of
huge but I'm loathe to destroy the information.  $site_db is superior
to player.all_connect_places in that it never forgets, so even when
someone manages to destroy their .all_connect_places, the information
is not lost forever (though it is no longer neatly indexed by user
object number.)  If you're neither paranoid nor fascist, $site_db can
be cleared ($site_db:clearall()) and $login:record_connection can be
changed to stop recording.

On LambdaMOO in the registration office there are a couple of verbs
useful for extracting information from the $registration_db, another
potentially large db.  (Notably @registered---@email also uses some of
this info).  This info can be helpful in tracking users who leave and
come back under a different object number.

      Judy Anderson yclept yduJ          'yduJ' rhymes with 'fudge'
 yduJ@cs.stanford.edu (personal mail)   yduJ@harlequin.com (work-related)
	Join the League for Programming Freedom, lpf@uunet.uu.net

• $site_db
• From: Jacqueline Hamilton <kira@metronet.com>

• Prev: Re: $site_db
• Next: $string_utils:explode()
• Index: MOO-cows
• Thread: MOO-cows