[erlang-questions] Could not open pty master
Fri Sep 26 12:12:05 CEST 2014
I have done chmod 777 to /dev, /dev/pty*, /dev/pts and /dev/pts/* and it
didn't help. Must be something different from file access permits. Anybody
has a clue of what run_erl does and requires?.
2014-09-25 10:41 GMT+02:00 Iván Martínez <ivan.martinez@REDACTED>:
> Thank you. Looks like SELinux has nothing to do with the issue:
> $ setenforce 0
> setenforce: SELinux is disabled
> 2014-09-25 3:21 GMT+02:00 zxq9 <zxq9@REDACTED>:
>> On Wednesday 24 September 2014 21:00:32 Iván Martínez wrote:
>> > Hello all,
>> > Does anyone know why I'm having the following issue with a CentOS 7
>> > with kernel 3.10.23?:
>> > $ run_erl priv/ log "erl"
>> > run_erl:187  Wed Sep 24 18:42:39 2014
>> > errno=1 'Operation not permitted'
>> > Could not open pty master
>> > It works as super user. It also works in a Fedora 20 system with kernel
>> > 3.16. I couldn't find any difference in user groups or /dev file permits
>> > between both systems. Starting with a user with UID above or below
>> > doesn't make any difference. I don't think it matters, but the only
>> > difference I could find is that the CentOS has many /dev/pty* files
>> > created, while the Fedora doesn't have any.
>> You might be running into SELinux permission issues. To find out try doing
>> "setenforce 0" and then running it again. If that works, use a tool like
>> audit2allow or audit2why to create a policy that will permit the actions
>> require to run your program. I haven't kept up with the Fedora/RHEL world
>> since 7 came out, but Dan Walsh's blog and Red Hat's SELinux docs have
>> good resources on this in the past.
>> Of course, you might have a totally different issue, but SELinux booleans
>> audit logs are the first thing I check on a Fedora-type distro when
>> doesn't work but looks like it should.
>> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions