reopen 369287 thanks Sergio Gelato <[email protected]> writes:
>> Greetings, and thanks for your report! Given the followup comment in >> the log, I'm assuming this was a device protection problem, and am >> closing. Please reopen if problems persist. > > For the record, I don't think this is a valid reason for closing the bug. > The following points have not been addressed: Fair enough. > > * the default permissions on the tty[0-9]* devices are still 0600 > (cf. /lib/udev/rules.d/91-permissions.rules) > * the documentation does not mention the need to change these permissions > * there may well be security implications in allowing universal write > access to these devices; I'm not convinced that the workaround in the > followup comment is the correct fix to the problem (although it may > be useful as a hint to where the problem lies) > > That said, I'm not going to reopen at this time because I'm no longer > interested in verifying that the problem persists. Our clusters no longer > run Debian, and our users have mostly moved on to OpenMPI (we don't even > install lam4-dev any more). It is conceivable, though not exactly obvious > from reading the HISTORY file, that this bug was fixed in 7.1.2. Had you to what entry are you referring? > written that you tried and failed to reproduce the problem in the latest > release, that would have been a more convincing reason for closing the bug. > Alas, I no longer have cluster access, and never did to an amd64 cluster. But I'd be happy to forward this upstream to see if the HISTORY entry you cite should have fixed the issue. This said, its awfully difficult to maintain open bug reports without a live test case at hand demonstrating the problem. Take care, -- Camm Maguire [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
