Re: SyncCM

[Marty.Hess@xxxxxxxxxxx (Marty Hess)]

>From owner-pilotmgr@xxxxxxxxxxxxxxxxxxxx  Mon Oct 25 16:10:47 1999
>To: "Kevin Kryzda x1310" <kevin@xxxxxxxxxxxx>
>Cc: <pilotmgr@xxxxxxxxxxxxxxxxxxxx>
>Subject: Re: SyncCM
> 
> "Kevin Kryzda x1310" <kevin@xxxxxxxxxxxx> wrote:
>>  Can Pilotmanager be installed in a client server mode (one executable
>>  set with many different clients)?
> 
> Pilotmgr's default data directory is ~/.pilotmgr, so using different
> unix users will accomplish this.
> If you want multiple users under a single unix user account you can
> user the -rcdir flag to specify different data directories for different
> users.

  To clarify: Each user-instance has to have a separate running instance
  of the (possibly singly-installed set of) executables.  (Of course you
  do NOT want any of them to be left running a HotSync daemon!  That would
  lock out any others from using the serial device.)
  
  To complicate things, any or all of the per-user installations (in each
  ~$USER/.pilotmgr) can be NFS-mounted, so you can also do roaming (within
  a WAN, and only on machines that allow you to logon locally and that have
  their serial ports or /dev/pilot properly configured) and sync, too.  (I
  do this from my home system via remote access sometimes and it works
  just fine.  In fact, you could just walk up to any unused sytem [with no
  one logged in to it] throughout the WAN and plug in your cradle and
  HotSync.  Domain-restrictions aside....)
  
  So you can have X * Y * Z user-instances from one set of executables.
  (Where "X" == different users with different ~/.pilotmgr dirs;
         "Y" == any of them having multiple PilotManager data dir's;
         "Z" == any machines from which a user can access X or Y and
                a set of matching PilotManager executables.)
  But any instance of (X,Y,Z) is a unique execution instance of
  PilotManager (possibly from that one, single set of executables.)
  
  							>Whew!<,
  								Marty