Mike Gerdts wrote: > > On 11/6/06, Darren J Moffat <Darren.Moffat at sun.com> wrote: [snip] > I am not at all opposed to this proposal, I just suspect that a > standard /tmp cleaner utility would have more impact. That is, do for > /tmp cleaning what logadm has done for log rotation.
Erm... I am STRONGLY opposed to something which crawls around in /tmp and deletes data on "random" basis. Yes, tmpfs is like a ramdisk and not persistent but deleting user data there is almost a gurantee that sooner or later someone opens the door of your office and start screaming&&wailing... ;-( > If this is a problem that is restricted to the case of a handful of > situations related to particular applications, it may be useful to > have /etc/profile process files in a directory named /etc/profile.d. > This way the Sun Ray software could add a file into that directory > that sets TMPDIR without performing the risky task of modifying > /etc/profile as a postinstall script. Having /etc/profile.d (and > similar for *csh users) would certainly simplify local customization > of environments without having to worry about patches or upgrades > whacking them. Actually I was thinking about something like /etc/env.d/ (env.d == environment setup/control scripts) which works like /etc/profile.d/ but takes care about items like: - login profile, e.g. /etc/profile - interactive shell profile: /etc/ksh.kshrc - Logout scripts (e.g. similar to /etc/profile but called at logout) - Shell session exit scripts (e.g. similar to /etc/ksh.kshrc but called when the interactive shell exists) - Allow future extensions - Allow priorisation (AFAIK /etc/profile.d/ does not allow any priorisation) - Allow conditional execution based on primary group id (e.g. if someone switches egid via /usr/bin/newgrp etc.). This should NOT be used for "roles" etc. - that would be an overkill ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
