public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: tail/head not working with a pseudoterminal
Date: Fri, 25 Nov 2011 14:32:00 -0000	[thread overview]
Message-ID: <20111125142152.GK23778@calimero.vinschen.de> (raw)
In-Reply-To: <CAEYw_q=jHbGUB66fwxtnVJ1A9THAoi+FehOLXNYD3_UxRydjLw@mail.gmail.com>

On Nov 25 16:03, Costin Caraivan wrote:
> Hello,
> 
> I'm trying to tail a file through SSH. I'm launching ssh through
> Python, like this:
> ssh -t user@vm-admin.corp.com "tail
> /cygdrive/c/ctier/ctl/var/logs/ctlcenter/STAGING/Administration/\[Staging\]\
> Sleep/7.txt"
> 
> And I get this:
> Pseudo-terminal will not be allocated because stdin is not a terminal.
> TAIL: lseeki64() failed 22

This is not Cygwin's tail.  The error message looks pretty weird.

Try ssh -tt.

> This works from the command line :(
> 
> Also head fails with:
> Pseudo-terminal will not be allocated because stdin is not a terminal.
> bash: /cygdrive/c/apps/activeperl/bin/head: /usr/bin/perl: bad
> interpreter: Permission denied

You're running the wrong head command.  This is some activestate perl
script, not the Cygwin head tool from coreutils.  Change your $PATH
to find the Cygwin apps first.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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-25 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 14:22 Costin Caraivan
2011-11-25 14:32 ` Corinna Vinschen [this message]
2011-11-25 14:48   ` Csaba Raduly
2011-11-25 15:48     ` Costin Caraivan

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=20111125142152.GK23778@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).