Hi
A new version of 'multitail' has been uploaded to a server near you.
o Update to latest upstream release
o Build for cygwin 1.7.34 with gcc-4.9.2
o Added Oracle WebLogic and Oracle GoldenGate logfile highlightning
multitail NEWS:
===
- status line fixes (some info was missi
On 6/20/2014 10:32 AM, Eli Zaretskii wrote:
Date: Fri, 20 Jun 2014 15:27:14 +0100
From: Ken Brown
Why did you need to step through the Glib code? AFAIU, the file
monitor did trigger, so what I would first look at is the data it
delivers back to Emacs, not how the monitor works internally. Did
, but I'm not able to test
>>>> it on other OS, so here are the steps to reproduce:
>>>>
>>>> emacs -Q
>>>> C-x C-r
>>>
>>> You mean C-x C-f
>>>
>>>> M-x auto-revert-tail-mode
>>>> wait for few sec
re are the steps to reproduce:
> >>
> >> emacs -Q
> >> C-x C-r
> >
> > You mean C-x C-f
> >
> >> M-x auto-revert-tail-mode
> >> wait for few seconds -> emacs crashes
> >
> > I can confirm this, but on 32-bit Cyg
On 19/06/2014 17:11 +0400, Ken Brown wrote:
> On 6/18/2014 1:46 PM, Ken Brown wrote:
> I'm afraid I ran into a brick wall trying to debug this. I wanted to
> see what gfile-add-watch was doing, so I ran emacs under gdb with a
> breakpoint at Fgfile_add_watch and then a breakpoint at g_file_monito
Ken,
On 18/06/2014 21:46 +0400, Ken Brown wrote:
> On 6/18/2014 11:06 AM, Filipp Gunbin wrote:
>> C-x C-r
>
> You mean C-x C-f
I did C-x C-r but that should not matter.
>
>> M-x auto-revert-tail-mode
>> wait for few seconds -> emacs crashes
>
> I can
On 6/18/2014 1:46 PM, Ken Brown wrote:
> On 6/18/2014 11:06 AM, Filipp Gunbin wrote:
>> I'm not sure whether this is Cygwin-specific, but I'm not able to test
>> it on other OS, so here are the steps to reproduce:
>>
>> emacs -Q
>> C-x C-r
>
>
On 6/18/2014 11:06 AM, Filipp Gunbin wrote:
I'm not sure whether this is Cygwin-specific, but I'm not able to test
it on other OS, so here are the steps to reproduce:
emacs -Q
C-x C-r
You mean C-x C-f
M-x auto-revert-tail-mode
wait for few seconds -> emacs crashes
I can conf
I'm not sure whether this is Cygwin-specific, but I'm not able to test
it on other OS, so here are the steps to reproduce:
emacs -Q
C-x C-r
M-x auto-revert-tail-mode
wait for few seconds -> emacs crashes
Filipp
--
Problem reports: http://cygwin.com/prob
Hi
A new version of 'multitail' has been uploaded to a server near you.
o Update to latest upstream release
o Build for cygwin 1.7.18 with gcc-4.5.3
multitail NEWS:
===
o No NEWS file available
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
If you want t
Hi
A new version of 'multitail' has been uploaded to a server near you.
o Update to latest upstream release
o Build for cygwin 1.7.16 with gcc-4.5.3
multitail NEWS:
===
o Added -N which sets the initial tail lines count for all following inputs
o Configuration file
Hi
A new version of 'multitail' has been uploaded to a server near you.
o Update to latest upstream release
o Build for cygwin 1.7.16 with gcc-4.5.3
o Uses cygport-0.11.0 for .hint files generation
o debuginfo package included
multitail NEWS:
===
o No NEWS available
CYGWIN-A
PACKAGE DESCRIPTION
===
Homepage: http://freshmeat.net/projects/xtail
License : BSD
Watch the growth of files. It's like running a tail -f on
a bunch of files at once. It notices if a file is
truncated and starts from the beginning. You can specify
both filenames and direct
> It's HEAD from lwp-request:
> http://search.cpan.org/~gaas/libwww-perl-6.03/bin/lwp-request
>
> Found unfortunately due to case-insensitive NTFS.
>
> Costin, try /usr/bin/head explicitly.
>
> Csaba
Thanks, that should do it.
I see one path when connecting manually with SSH, and another one when
On Fri, Nov 25, 2011 at 3:21 PM, Corinna Vinschen wrote:
> On Nov 25 16:03, Costin Caraivan wrote:
...
>> 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 den
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 u...@vm-admin.corp.com "tail
> /cygdrive/c/ctier/ctl/var/logs/ctlcenter/STAGING/Administration/\[Staging\]\
&
Hello,
I'm trying to tail a file through SSH. I'm launching ssh through
Python, like this:
ssh -t u...@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 be
' Please Unsubsribe My Name '
John Boyd
On Thu, Nov 17, 2011 at 12:09 PM, Dr. Volker Zell
wrote:
> Hi
>
> A new version of 'multitail' has been uploaded to a server near you.
>
> o Updated to latest upstream release
> o Build for cygwin 1.7.9 with gcc-4.5.3
>
>
> multitail NEWS:
> ===
Hi
A new version of 'multitail' has been uploaded to a server near you.
o Updated to latest upstream release
o Build for cygwin 1.7.9 with gcc-4.5.3
multitail NEWS:
===
o No NEWS available
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
If you want to unsubs
Am 17.02.2011 23:50, schrieb Jari Aalto:
>
> PACKAGE DESCRIPTION
> ===
>
> Homepage: http://freshmeat.net/projects/since
That would be http://welz.org.za/projects/since
--
Matthias Andree
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://c
PACKAGE DESCRIPTION
===
Homepage: http://freshmeat.net/projects/since
License : GPL-3+
Program remembers how much of a file you have viewed and displays only
what's new when you next view that file. Ideal for viewing log files
(it'll only show what's new in the file since the las
Eric Blake redhat.com> writes:
> And can this possibly be related to the previously reported issue where
> bash's choice of terminal control functions would cause execution of
> gitk as a background process to exit bash?
>
If I start mintty with vt100 as the termtype, then the problem seems to
On 12/08/2010 10:28 AM, Christopher Faylor wrote:
>> After ctrl+C during a grep which is redirecting output to a file:
>>
>> $ speed 38400 baud; line = 0;
>> start = ; stop = ; lnext = ; min = 1; time = 0;
>> -icrnl -imaxbel
>> -icanon -echo -echoe -echok -echoctl -echoke
>
> Can anyone duplicate
On Wed, Dec 08, 2010 at 04:06:35PM +, TJ Anthony wrote:
>Andy Koppe gmail.com> writes:
>
>>
>> On 2 December 2010 20:28, Heath Kehoe wrote:
>> >> FWIW, I can't reproduce this, even if I kill the tail or less with
>> >> SIGKILL, thus givi
Andy Koppe gmail.com> writes:
>
> On 2 December 2010 20:28, Heath Kehoe wrote:
> >> FWIW, I can't reproduce this, even if I kill the tail or less with
> >> SIGKILL, thus giving them no chance to do any cleanup. (I assume you
> >> use 'less -K'
On 2 December 2010 20:49, Illia Bobyr wrote:
> On 12/2/2010 2:28 PM, Heath Kehoe wrote:
>> [...]
>> Also, the OP said the problem was happening on pipelines like 'tail | grep'.
>> Neither tail nor grep muck with tty settings (that I know of), so if the tty
>
On 2 December 2010 20:28, Heath Kehoe wrote:
>> FWIW, I can't reproduce this, even if I kill the tail or less with
>> SIGKILL, thus giving them no chance to do any cleanup. (I assume you
>> use 'less -K' to allow it to be ctrl-c'ed?)
>>
>> Which
.
>> >>>
>> >>> Would you, please, elaborate on this a little bit?
>> >>> Maybe a link or a reference that explains why this is happening?
>> >>
>> >> I'm sorry, I can't. I don't know why it is happening. I just know h
gt;> Would you, please, elaborate on this a little bit?
>>>>> Maybe a link or a reference that explains why this is happening?
>>>>
>>>> I'm sorry, I can't. I don't know why it is happening. I just know how
>>>> to recover from it
On 12/2/2010 2:28 PM, Heath Kehoe wrote:
> [...]
> Also, the OP said the problem was happening on pipelines like 'tail | grep'.
> Neither tail nor grep muck with tty settings (that I know of), so if the tty
> is ending up with echo disabled, it's got to be the s
; Maybe a link or a reference that explains why this is happening?
>>>
>>> I'm sorry, I can't. I don't know why it is happening. I just know how to
>>> recover from it as a user.
>>
>> I've noticed that this misbehavior occurs more freque
;m sorry, I can't. I don't know why it is happening. I just know how to
>> recover from it as a user.
>
> I've noticed that this misbehavior occurs more frequently these days:
> ctrl-c'ing some tasks (tail, less, maybe a few others) ends up with the
> terminal
link or a reference that explains why this is happening?
>>>
>>> I'm sorry, I can't. I don't know why it is happening. I just know how
>>> to recover from it as a user.
>>
>> I've noticed that this misbehavior occurs more frequently these days
bit?
> >>> Maybe a link or a reference that explains why this is happening?
> >>
> >> I'm sorry, I can't. I don't know why it is happening. I just know how
> >> to recover from it as a user.
> >
> > I've noticed that this mis
m sorry, I can't. I don't know why it is happening. I just know how
>> to recover from it as a user.
>
> I've noticed that this misbehavior occurs more frequently these days:
> ctrl-c'ing some tasks (tail, less, maybe a few others) ends up with the
> terminal settings
er from it as a user.
I've noticed that this misbehavior occurs more frequently these days:
ctrl-c'ing some tasks (tail, less, maybe a few others) ends up with the
terminal settings all scrogged up, and requires you to "blindly" type in
'reset' (or stty sane) to fix it
Illia Bobyr wrote:
> On 12/1/2010 8:53 PM, David Rothenberger wrote:
>> orbita wrote:
>>> hi,
>>> I've been experiencing this problem for quite some time. Whenever I do a
>>> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the ta
On 12/1/2010 8:53 PM, David Rothenberger wrote:
> orbita wrote:
>> hi,
>> I've been experiencing this problem for quite some time. Whenever I do a
>> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
>> can't type in new co
On 12/1/2010 8:53 PM, David Rothenberger wrote:
> orbita wrote:
>> hi,
>> I've been experiencing this problem for quite some time. Whenever I do a
>> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
>> can't type in new co
orbita wrote:
>
> hi,
> I've been experiencing this problem for quite some time. Whenever I do a
> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
> can't type in new commands to the command prompt anymore.
>
> All I could
hi,
I've been experiencing this problem for quite some time. Whenever I do a
tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
can't type in new commands to the command prompt anymore.
All I could do is close that window and open another cygwin s
Alpha Fighter yahoo.com> writes:
>
> I've run into an issue with bash-completion v1.2-1. After I tail -f a file
and then press ctrl-c to stop
> tailing I can no longer see any text I type. My text is being entered, just
not being ... echoed back.
>
> This does not ha
Alpha Fighter yahoo.com> writes:
>
> I've run into an issue with bash-completion v1.2-1. After I tail -f a file
and then press ctrl-c to stop
> tailing I can no longer see any text I type. My text is being entered, just
not being ... echoed back.
>
> This does not ha
I've run into an issue with bash-completion v1.2-1. After I tail -f a file and
then press ctrl-c to stop tailing I can no longer see any text I type. My text
is being entered, just not being ... echoed back.
This does not happen after uninstalling 1.2-1. It also does not happen
I've run into an issue with bash-completion v1.2-1. After I tail -f a file and
then press ctrl-c to stop tailing I can no longer see any text I type. My text
is being entered, just not being ... echoed back.
This does not happen after uninstalling 1.2-1. It also does not happen
difference-only' (which works at character level)
- --retry added to tail when --retry is requested
- suppress_empty_lines did not work
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
If you want to unsubscribe from the cygwin-announce mailing list, please
use the autom
>> Note that the +N notation is specific to --lines=, not the '-n'
>> shorthand.
>
> Wrong - the +N notation also works with -n:
>
> ps -a | tail -n +5
Ah, I was confused since 'tail -5' still works, but:
> This is a side affect of the change to the
This is a side affect of the change to the newer POSIX standard. For instance,
to use the old standard:
503:$ _POSIX2_VERSION=199209
504:$ export _POSIX2_VERSION
505:$ ps -a | tail +5
2864 12864 2864 con 718399 19:26:01 /usr/bin/rxvt
76122864
According to Chris Sutcliffe on 3/2/2010 8:01 PM:
>> The "tail +4" commands does not work as advertised. When given such command
>> (advertised in man command), it complains it can't open the file. With the
>> command "tail +5 -", it produces the d
> The "tail +4" commands does not work as advertised. When given such command
> (advertised in man command), it complains it can't open the file. With the
> command "tail +5 -", it produces the desired output with some junk on
> standard output.
As per th
The "tail +4" commands does not work as advertised. When given such
command (advertised in man command), it complains it can't open the
file. With the command "tail +5 -", it produces the desired output with
some junk on standard output.
See examples:
$ ps -a | ta
Marco Atzeri wrote:
> --- Mer 28/10/09, Roland Schwingel ha scritto:
>> I get an error:
>> tail: cannot open '+3' for reading: No such file or
>> directory.
>>
>> Is this on purpose or an accident?
> probably, the last
>
> $ tail --vers
tto:
>>
>> the manual says
>> tail -N +3 /path/to/some/file
> You mean
> tail -n +3 /path/to/some/file
> If I do that it will work fine.
>
> I just wonder it this change was on purpose or not, because the other form
> (without -n) still work on other syste
well,
> > but I encountered a problem with the tail command. Obviously
> > the + syntax does no longer work in 1.7
> >
> > In 1.5 when I call eg.
> > tail +3 /path/to/some/file
> >
> > I get the whole file printed starting with line 3 (the
> > first 2
--- Mer 28/10/09, Roland Schwingel ha scritto:
> Hi...
>
> At present I am using cygwin 1.5 mainly, but I have also
> started to migrate over to 1.7. Everything works quite well,
> but I encountered a problem with the tail command. Obviously
> the + syntax does no longer work
Hi...
At present I am using cygwin 1.5 mainly, but I have also started to
migrate over to 1.7. Everything works quite well, but I encountered a
problem with the tail command. Obviously the + syntax does no longer
work in 1.7
In 1.5 when I call eg.
tail +3 /path/to/some/file
I get the whole
Hi
A new version of 'multitail' has been uploaded to a server near you.
DESCRIPTION:
MultiTail lets you view one or multiple files like the original tail
program. The difference is that it creates multiple windows on your
console (with ncurses). It can also monitor wil
Gustavo Seabra wrote on 29 October 2008 17:39:
>> The "-NNN" form is an abbreviation for "-n NNN". If you write it out
>> in full, it works:
>>
>> $ tail -n 2 *.dat
>>
>
> OK, I see that now. Thanks. But is there a reason why the abb
Gustavo Seabra gmail.com> writes:
> >> $ tail -2 *.dat
>
> OK, I see that now. Thanks. But is there a reason why the abbreviation
> is not working in cygwin? It works just fine in a different system...
It may be due to how many files that glob expands to, as the obsole
On Wed, Oct 29, 2008 at 11:12 AM, Dave Korn <[EMAIL PROTECTED]> wrote:
> Gustavo Seabra wrote on 29 October 2008 14:33:
>
>> I just noticed this one thing when using 'tail' in cygwin. For some
>> reason, when using a '*' so as to 'tail' mult
Gustavo Seabra wrote on 29 October 2008 14:33:
> I just noticed this one thing when using 'tail' in cygwin. For some
> reason, when using a '*' so as to 'tail' multiple files at once, the
> '-n' option to tail doesn't work anymore.
> $
Hi All,
I just noticed this one thing when using 'tail' in cygwin. For some
reason, when using a '*' so as to 'tail' multiple files at once, the
'-n' option to tail doesn't work anymore. Note that I tried without
the '-n', and it works just a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to smr on 4/16/2008 6:29 PM:
Please don't top-post: http://cygwin.com/acronyms/#TOFU
| Hi Christopher, is there currently an ETA for a release that would
| include this fix (whether that's 1.5.25-xx, or 1.6/1.7)?
In the classic open
Hi Christopher, is there currently an ETA for a release that would
include this fix (whether that's 1.5.25-xx, or 1.6/1.7)? I've been
out of the loop for a long time, so apologies if this is a question
you've been badgered with recently.
Thanks,
Steven
On Wed, Apr 16, 2008 at 4:44 PM, Christoph
On Wed, Apr 16, 2008 at 03:04:12PM -0700, smr wrote:
>Thanks very much Eric and Corinna for the responses -- glad to hear
>it's already fixed.
FYI, this will even be fixed in the 1.5.25 series eventually.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports
mr on 4/14/2008 11:56 AM:
> > > | Hi, I've just rebuilt my machine and done a clean install of the
> > > | latest Cygwin, and am having a problem with tail. I'm wanting to know
> > > | whether this is a known issue before digging deeper.
> > &g
On Apr 16 14:49, Corinna Vinschen wrote:
> On Apr 16 06:23, Eric Blake wrote:
> > According to smr on 4/14/2008 11:56 AM:
> > | Hi, I've just rebuilt my machine and done a clean install of the
> > | latest Cygwin, and am having a problem with tail. I'm wanting
On Apr 16 06:23, Eric Blake wrote:
> According to smr on 4/14/2008 11:56 AM:
> | Hi, I've just rebuilt my machine and done a clean install of the
> | latest Cygwin, and am having a problem with tail. I'm wanting to know
> | whether this is a known issue before digging
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to smr on 4/14/2008 11:56 AM:
| Hi, I've just rebuilt my machine and done a clean install of the
| latest Cygwin, and am having a problem with tail. I'm wanting to know
| whether this is a known issue before digging deeper.
file_lines(...);
>}
>else
>{
> pipe_line(...);
>
>}
>
>
> On Mon, Apr 14, 2008 at 10:56 AM, smr xxxx <[EMAIL PROTECTED]> wrote:
> > Hi, I've just rebuilt my machine
{
pipe_line(...);
}
On Mon, Apr 14, 2008 at 10:56 AM, smr <[EMAIL PROTECTED]> wrote:
> Hi, I've just rebuilt my machine and done a clean install of the
> latest Cygwin, and am having a problem with tail. I'm wantin
Hi, I've just rebuilt my machine and done a clean install of the
latest Cygwin, and am having a problem with tail. I'm wanting to know
whether this is a known issue before digging deeper. For other
reasons, I've rebuilt my machine clean twice this weekend and have had
this pro
Hi
A new version of 'multitail' has been uploaded to a server near you.
DESCRIPTION:
MultiTail lets you view one or multiple files like the original tail
program. The difference is that it creates multiple windows on your
console (with ncurses). It can also monitor wil
PACKAGE DESCRIPTION
===
Homepage: http://welz.org.za/projects/since
License : GPL
Program remembers how much of a file you have viewed and displays only
what's new when you next view that file. Ideal for viewing log files
(it'll only show what's new in the file since the last time
iew one or multiple files like the original tail
program. The difference is that it creates multiple windows on your
console (with ncurses). It can also monitor wildcards: if another file
matching the wildcard has a more recent modification date, it will
automatically switch to that file. That way you
u view one or multiple files like the original tail
program. The difference is that it creates multiple windows on your
console (with ncurses). It can also monitor wildcards: if another file
matching the wildcard has a more recent modification date, it will
automatically switch to that file. That w
more parameters configurable
- error messaging is more uniform
- added -kS which, like sed, can select parts of strings to keep. e.g.
-kS "^.*(TCP[^ ]*).*$" would keep the string matched by what is between ( and )
- fixed 2 memory leaks
- replaced 2 strcat()s
ternating colors
4.3.7: - added case insensitive toggle to searchfields
5.0.0: - merge with developmentversion 4.3.7
- default linewrap mode in configurationfile was incorrectly parsed
- added colorscheme for motion
DESCRIPTION:
MultiTail lets you view one or multiple
Hi
The package multitail is now available with the Cygwin distribution:
o http://www.vanheusden.com/multitail/ (Homepage)
DESCRIPTION:
MultiTail lets you view one or multiple files like the original tail
program. The difference is that it creates multiple windows on your
console
Hi,
I noticed there was a new version of readline. Does it fix this issue?
On 3/31/06, Eric Blake <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to William Xue on 3/29/2006 11:06 PM:
> Hi,
> Please let me describe the issue for you:
Issues like this have be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to William Xue on 3/29/2006 11:06 PM:
> Hi,
> Please let me describe the issue for you:
Issues like this have been reported in the past, but this is the first
report against readline-5.1-5.
> After set the PS1 in .bashrc to :
> ---8<---
Hi,
Please let me describe the issue for you:
After set the PS1 in .bashrc to :
---8<->8---
PS1="\[\e]2;\w -- [EMAIL PROTECTED]@\H hangsps:\j\d
\t\a\]\[\e[31;1m\][\[\e[36;[EMAIL PROTECTED]
\[\e[33;1m\]\W\[\e[31;1m\]]\[\e[34;1m\]\[\e[32;1m\]\$
On 19/05/05, Igor Pechtchanski wrote:
> On Thu, 19 May 2005, Dave Korn wrote:
> > Amusingly enough, those were still both legitimate email addresses even
> > after he X'd them out!
oops.
> That's why one ought to X out the top-level suffix too. I don't believe
> .XXX is a valid suffix. Or
On Thu, 19 May 2005, Dave Korn wrote:
> Original Message
> >From: Lev Bishop
> >Sent: 12 May 2005 23:56
>
> > On 12/05/05, Lev Bishop wrote:
> >> On 11/05/05, Peter Ekberg wrote:
> >
> > Sorry, sorry, sorry.
> >
> > 'kin
Original Message
>From: Lev Bishop
>Sent: 12 May 2005 23:56
> On 12/05/05, Lev Bishop wrote:
>> On 11/05/05, Peter Ekberg wrote:
>
> Sorry, sorry, sorry.
>
> 'kin gmail.
>
> Lev
Amusingly enough, those were still bo
Lev Bishop wrote:
> Try "grep --line-buffered" to get grep to flush output after every
> line. There is a performance penalty for doing this. I don't know why
> you don't see the buffering when grep's stdout isn't redirected.
> Perhaps grep (or the std library) removes/reduces buffering in the
> ca
Try "grep --line-buffered" to get grep to flush output after every
line. There is a performance penalty for doing this. I don't know why
you don't see the buffering when grep's stdout isn't redirected.
Perhaps grep (or the std library) removes/reduces buffering in the
case the output is a terminal.
Lev Bishop wrote:
> On 11/05/05, Peter Ekberg wrote:
>> What is going on here?
>
> My guess: "tail frame.log" closes its stdout as soon as it has read
> the requested lines from the file, "tail -f frame.log" keeps its
> stdout open, since it is waiting f
On 12/05/05, Lev Bishop <[EMAIL PROTECTED]> wrote:
> On 11/05/05, Peter Ekberg <[EMAIL PROTECTED]> wrote:
Sorry, sorry, sorry.
'kin gmail.
Lev
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
On 11/05/05, Peter Ekberg <[EMAIL PROTECTED]> wrote:
> What is going on here?
My guess: "tail frame.log" closes its stdout as soon as it has read
the requested lines from the file, "tail -f frame.log" keeps its
stdout open, since it is waiting for new lines to be
Hello!
What is going on here?
~$ ps -f | grep $$
peda2316 1 con 20:21:51 /usr/bin/bash
peda31802316 con 21:51:47 /usr/bin/ps
peda31642316 con 21:51:47 /usr/bin/grep
[I use bash, if that matters]
~$ tail -f frame.log | grep Antenna
2005-05-11,21:51:07
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Krisztian Fekete on 3/31/2005 2:22 AM:
> Hi,
>
> GNU tail has an option to output the last n bytes:
>
> $ tail --help
> ...
> -c, --bytes=Noutput the last N bytes
> ...
>
> In the current c
Hi,
GNU tail has an option to output the last n bytes:
$ tail --help
...
-c, --bytes=N output the last N bytes
...
In the current coreutils version (5.3.0-3) the short option version
stopped working:
$ tail -c 30
tail: cannot open `30' for reading: No such file or directory
Hi,
In bash, I'm doing:
some_process >& output &
Then, repeatedly doing:
tail -f output
And aborting the operation eventually crashes some_process.
The problem seems to be general; it happens when using other processes, e.g.
the bash script:
while ((1)); do date; sleep 0.
Alexander Geraldy wrote:
> I've seen the following problem and don't know how to handle it.
>
> Configuration: Cygwin 1.5.11-1, tail (textutils) 2.0.21, strace (cygwin)
> 1.21
Unfortunately, it looks like the textutils package has gone
unmaintained. The last release of
Hello!
I've seen the following problem and don't know how to handle it.
Configuration: Cygwin 1.5.11-1, tail (textutils) 2.0.21, strace (cygwin)
1.21
I noticed that various utilities (including grep and tail) have problems
with the following textfile (let's call it test.txt):
Larry Hall wrote:
> the file deleted by "rm" isn't deleted really until it's closed, which
> won't happen until 'tail' ends. This is the way Windows works. There's
> not much to be done about it (at least not in Cygwin). Believe me,
> we&#x
At 01:08 PM 5/18/2004, you wrote:
>I can't change the application unfortunately, if I
>could I'd have it only log interesting stuff rather
>than the garbage it does.
>
>Is it worth trying maybe to link the file and tail the
>link ? or mess with a tee command ??
I gues
I can't change the application unfortunately, if I
could I'd have it only log interesting stuff rather
than the garbage it does.
Is it worth trying maybe to link the file and tail the
link ? or mess with a tee command ??
--- Larry Hall <[EMAIL PROTECTED]> wrote:
> re tail a
At 09:31 AM 5/18/2004, you wrote:
>I am sorry if this has been covered before, but I was
>wondering if there is work around (probably not ;-(
>
>In unix you can do the following
>tail -f /somefile
>in another session
>rm -f /somefile
>echo OK > /somefile
>
>of c
1 - 100 of 113 matches
Mail list logo
