Zhang Weiwu wrote:
Dear all
I was wondering is there a best practice or conventional suggestion that software should not write temporary files in user's home directory, but do it on /tmp/ or /var/tmp?
I ask this because when I want to backup a live user profile usually it fails thanks to file size change during backup. Most of them are temporary files. In my case it is a bit difficult to back it up by asking the user to log out, because I can only access their computers in working hour, and they are working in working our, especially backup takes perhaps 1 hour, and I don't want to interrupt them by 1 hour. After working hour they took back their notebooks. I start to think, that is it by design backup should be when user not logged in, or is there exist a convention of not using ~/.app as temp but software designers tends to ignore that?
Thanks.
Great question. But define fails? Does the backups software not offer the option to use advisory locks, ro simply ignore locks? Or are you saying that the backup reads everything fine, but it's never possible to get a clean verify since always some files have changed by the time the subsequent verify happens? I would say in this case that, under the conditions you are forced to work within, and if you can not change these conditions (arrange for dedicated backup time or change the software being used by the users), that you simply have to give up on being able to verify /home. I don't know of any especially official standard or practice that says a user mode app shall avoid using anything but one of the central */tmp directories for work files. There may be but I'm simply not addressing that part of the question since I have only my own opinion, not a definitive answer for it. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org