Dear there,
This is happening on our cusomters' server. I don't know when this started but when our program began to have problem I got to notice that. Our program fails because it has to delete some temp files under /var/tmp, and those files have sticky bit "t" set, so our program can't delete it becasue the users to create it and delete it are different. This is somehow our design but my question is why the sticky bit "t" was suddenly got to set? while before it didn't.
By "fuer /var/tmp" I can find some snmp processes are using this directory, should any of them are setting sticky bit "t"??
Setting the sticky bit on tmp directories is a security measure, a good thing (TM). So any program like bastille could be doing it.
Also, if the bit isn't set on /var/tmp/, you'll get a nasty message in syslog.log from ld or a compiler.
>SNMP processes are using this directory, should any of them be setting sticky bit?
Probably not.
There is nothing automatic in HP-UX to change the permission bits on /var/tmp. Perhaps some security expert has added a job to crontab to make sure the permissions are safe. If you change /var/tmp to 777 (no sticky bit) then everyone on your computer can remove or rename any files, and even create directories and subdirectories to hide your files. If these files are important, then /var/tmp is not the right place. There are many different ways to control the content of files as well as their existence (the permissions are separate and independent of each other).
>There is nothing automatic in HP-UX to change the permission bits on /var/tmp
Possibly someone doing "swverify -F" on filesets that mention /var/tmp/.
Thanks everybody.
Should swverify set this bit? I will try to find out
>Should swverify set this bit?
Only if you order it to do so with -F, on the right (or all) filesets.