[quoted lines by Jason White on 2007/07/06 at 20:26 +1000] >The first problem could be solved by searching for other BRLTTY processes >before removing/unmounting the resources, or maybe creating a file (e.g., >in /var/run) which contains a reference count, such that resources are removed >when this is decremented to 0 by the last remaining BRLTTY process.
Searching for processes is very unportable, piddling around with locking files is, in my opinion, needlessly complicated, and, last but not least, kill -KILL will stop brltty cold in its tracks without giving it an opportunity to clean up. Then there's the increase in code size, which, in this case, is significant because one of the main uses for the resource creation feature is boot images. >As for the second problem, at least on Linux, doesn't umount(2) suffice? Well, yes, spawning a umount command would do it, and, in fact, would be portable. >Notwithstanding the above, I agree that this feature may be more difficult to >implement than it is worth. Thus my comments should not be taken as an >argument for implementing it. That's how I feel about it. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. http://FamilyRadio.com/ | http://Mielke.cc/bible/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
