Bill Freeman <ke1g...@gmail.com> writes: > > The sticky bit probably doesn't fly since it isn't "my" box. It's just > somewhere that folks will want to install my "app". So I shouldn't be > requiring global (effecting every /tmp user) system changes. (I'm only > requiring an app specific user and init.d scripts.)
Not that I'm objecting, but more for my own edification: are there actually systems out there that don't set the sticky bit on /tmp? That just seems... insane.... > A subdir in /tmp can certainly have my ownership and permissions. And I guess > they can't delete the directory because it isn't empty, but with permissions > on the parent directory, can't they move it? > > Does anyone see significant issues with the approach that the daemon keeps the > PID file open, with a flock() advisory lock on it? (Deployed and seems to > work.) > > Bill > > > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ -- "Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))." _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
