>> So I'd rather not abuse the sticky bit for that kind of thing, >> especially as there's no good reason to do so. >> We can very simply create a separate state file that's removed on >> shutdown, or just use the one we already have (rootfs.hold). > >I have to also concur with this. I would be appalled and adamently >opposed to overloading the stick bit with that sort of functionality >that could have untold side effects. It would end up being poorly >documented, confusing and very misunderstood. We've seen that sort of >thing in the Samba project. A state file (similar to the .hold file) in >the container's management directory makes vastly more sense.
Oh, I tapped on a mine ;) No problem for me to use a separate file for this. It's much more portable to any kind of platform, too. Or even better the one we already have, if this will also then fulfill "separation of concerns" and don't use it to support two features. Guido ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
