On 12.3.2014 3:42, Carsten Haitzler wrote:
there should be no resources outside a homedir. simple. if there is a
default system config - it is owned by the system. it stays because any
newly created user will copy/start with that config (and if
needed/desired write a copy of that to $HOME/somewhere). if there are
user resources outside the users homedir (other than temporary things
like /tmp or /var/run that can get nuked at a reboot etc.)... it's just
plain wrong™. :) it's the app's job to deal with loading a system config
if no user config is done, to deal with writing out user config,
handling config upgrades etc.
/etc/skel is supported by gumd.
Any files with userid ownership outside of $HOME should be cleaned up,
because once the /etc/passwd entry is gone, there is no guarantees how
soon the userid is reused. Waiting for next boot is not sufficient.
Don't forget at least /var/mail/<username> and possible entries in
/var/spool and /var/tmp. What to do with blocked cups print jobs?
I'm not sure what will happen to /dev/mqueue and named shared memory and
semaphore entries in case uid is reused and some app didn't clean up
it's things (call mq_unlink()/sem_unlink()/etc).
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
