> Indeed I hadn't understood the problem. What if the process wrote its > PID to the port file besides just opening it? Opening the file ensures > nobody else can open it and writing your PID there allows usage > of ioctls etc. The semantics of close will be that the file is emptied. > > We will probably have to come up with something better than that though. Just realized that this wouldn't allow sharing the port with forking, unless both sides of the fork had written their pid and writes are atomic. Thanks, Pantelis -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
