
- Make sure both the "netplan" and "pland" daemons are running.

- If SyncPlan still complains that it could not open the plan socket,
  your netplan daemon might listen on a different port. Try 12000 for
  SuSE Linux or do a "strace netplan -d" and watch the value of sin_port
  in the bind() call.

- Make sure you have clicked the "Server" checkbox from the File List
  dialog in plan, and that the Server Host lists the machine where netplan
  is running.  Otherwise you won't see any of your appointments after the
  sync!

- In order to setup SyncPlan you have to run a first sync which will fail,
  but it sets up the control file.  After the first sync you must edit
  the file ~/.pilotmgr/SyncPlan/control and tell it where your plan calendar
  is.  The line in the control file should be:
<pilotuser>_<pilotid> <user>@<host>
  The pilot tags will be filled in for you.  You must add "user@host" where
  user is your username and host is the machine netplan is running on.

- Once you have done the above do another sync and it should all work!
  Note that this setup process could be improved in the future, but so
  far no modification has been done beyond the original command line
  sync-plan script...

- The Output Levels are: 0 = Quiet, 1 = Notify of changes in Plan / Pilot,
                         2 = Notify of each record found, 3 = full debug.
  For more debug info, uncomment some print statements in the module source.

