> Le 12/12/2010 à 01:50, Witold Baryluk a écrit : > > > > Package: upgrade-reports > > Severity: normal > > Tags: squeeze > > > > Hi. > > > > Basically I had /var/cache/apt, linked to /home/root/apt, and /home was NFS > > mount. > > > I also discovered today that I have all users' TMP and TEMP env. var. pointing to /home/username/tmp which unfortunelty is also true for user root (i do not know how to add exception to pam_env.so and /etc/security/pam_env.conf for user root - it currently affects all users). So also interactive root session (used to upgrade) had TMP and TEMP pointing to /home/root/tmp, this directory obviously existed, but due to the problem on upgrade with nfs (probably portmap restart, or something like that), any access to TMP resulted in error (No such directory - which resulted in many packages upgrade/install errors), or uninteruptible lock (even worse). What is even stranger manually exporting TMP=/tmp TEMP=/tmp just before apt-get ...., due not changed this behaviour. This is of course my fault that root user had insecure and not robust enough TMP directory set. (but I unfortunelty do not know how to make it work and still have it configured for normal users). I do not know if also adding small warning somehow about this in upgrade notes can help someone. I know this is probably unusual configuration, but it is good to know all this strange situations where upgrade can fail and notify users about such possibility. PS. TMP/TEMP is setup into users home directory mainly due to the simpler quota managment. (and the fact that local /tmp had no quota and can easly fill up making some system services fail). Thanks. -- Witold Baryluk JID: witold.baryluk // jabster.pl
Attachment:
signature.asc
Description: Digital signature