Claudio,
WRT Eric's email:
> --rw-rw---- M 9 mach0 adm 2125 Dec 18 08:13 /adm/keys
> --rw-rw---- M 9 mach0 adm 1539 Dec 18 08:14 /adm/keys.who
I think he is onto somthing here, my permissions are a little different,
my CPU servers boot as the user 'bootes' - its like root on a unix box, its a
name which is used by convention for the owner of a machine but everything
still works if you use a different name, you just have to rembember to use the
same name as the owner of all your cpu and auth servers. It seems Eric uses
mach0 as the hostowner for his cpu server, and from your description
you have chosen glenda.
I also allow the world to read keys.who as this does not contain secrets, only
admin info (real name email address etc).
--rw------- M 17739 bootes sys 300 Jan 3 2006 /adm/keys
--rw-rw-r-- M 17739 bootes sys 166 Aug 17 2005 /adm/keys.who
As I rembember it I had to create these files using the
fossil console. This was years ago though and the distribution may
now create these correctly.
cpu% con -l /srv/fscons
prompt: fsys main create /active/adm/keys bootes sys 600
prompt: fsys main create /active/adm/keys.who bootes sys 664
ctrl-\ q
Note: ``prompt:'' is the default prompt printed by the fossil console
-Steve
