public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: problem with GNU screen solved
Date: Wed, 23 Nov 2011 14:06:00 -0000	[thread overview]
Message-ID: <62lpc79v3s07q0fg0ecj6o8snhrl195ir6@4ax.com> (raw)
In-Reply-To: <20111123051000.GA3194@chomsky.local>

> I just wanted to pass this along...  I was having problems with screen
> a couple months ago.  I would get an error saying "chown tty: No such
> file or directory" and then it would fail (see
> http://cygwin.com/ml/cygwin/2011-06/msg00222.html).
> 
> Paul Hebble was kind enough to write me off-list with a fix.  After
> applying the patch that comes with the source package, I made the
> following simple change to config.h:
> 
>   #define PTYROFS
> 
> These comments come from config.h:
> 
>  * Note, screen is unable to change mode or group of the pty if it
>  * is not installed with sufficient privilege. (e.g. set-uid-root)
>  * define PTYROFS if the /dev/pty devices are mounted on a read-only
>  * filesystem so screen should not even attempt to set mode or group
>  * even if running as root (e.g. on TiVo).
> 
> This solved my problem.  Now I'm curious why some see this problem but
> others don't.  Some sort of privilege issue that is setup dependent?
> 
> Anyway, I hope the package maintainer will find this useful.

Thanks Jeff, for posting the solution.  I'll look at that when I can to
figure out whether it should be enabled by default.  I don't know much
about ptys though - maybe someone who knows more could comment?  Andrew.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2011-11-23 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23  8:12 Jeff Schenck
2011-11-23 14:06 ` Andrew Schulman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62lpc79v3s07q0fg0ecj6o8snhrl195ir6@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).