Yannick Lecaillez wrote:
> José Luis Tallón wrote:
> 
>> Yannick Lecaillez wrote:
>>  
>>
>>> We have to change this behaviour : no more store user settings into 
>>> their respective home directory
>>>    
>>>
>> This was probably a very good idea. It might need some thoughts in order
>> to try to keep it. It is IMVHO the best approach
>>  
>>
> I think too. But there is, at least, one disadvantage with that : its
> usual for Linux users to have a "system" partition and a home partition.
> This way, you could change/upgrade your distribution while keeping your
> home partition intact (containing your datas and your settings). That
> mean user have to backup himself its user's specifc settings using kdb
> -export otherwise these could simply be lost during
> reinstallaion/upgrading ...
> 
> But the still good advantage is that permit to run daemon as user
> everytime. So, i think that need discution

I hope I'm not misunderstanding you, but the daemon cannot be run as the 
user: It will not have the necessary access to system configuration 
settings -- unless it happens to use the filesys backend which works by 
virtue of the file system ACLs being identical with the Elektra ACLs.

The backup issue is interesting though... If the user settings are to be 
stored in the user's home directory then the daemon could spawn a 
subprocess (which could setuid) for each user that is connected to it, 
and direct all requests for user keys to the appropriate sub-process and 
handle system keys itself.

I definitely think user settings should be stored in the user's home 
directory. If the user wants to share settings across multiple machines 
this is pretty much the only option. (There is technically another 
option, namely only running a single daemon and letting the user specify 
  which daemon to use for user: settings. However, I think this 
complicates matters even further by requiring the daemon to be 
accessible over the network, etc.)

Of course sharing across multiple machines may be complicated and messy 
depending on the backend, but at least the user has the option of trying 
to...

[--snip--]
> 
> Hmm ... just got an idea .... Why not store system settings into
> /etc/<somewhere> (or /var/lib/<somewhere>) and user's specific into
> /home/elektra ? This way users keep their settings if they
> change/upgrade their distros and we don't have to run kdbd as root.
> 

This doesn't really work with setups where users are spread out over 
multiple physical volumes. For anything like that is is equivalent to 
just storing the user keys in the same place as the system keys.

-- 
Bardur Arantsson
<[EMAIL PROTECTED]>

- I'm anaspeptic, phrasmotic even compunctuous to have caused you
such... pericombobulation.
                               Edmund Blackadder, 'Blackadder III'


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Registry-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/registry-list

Reply via email to