Giuseppe Scrivano wrote:
However, while looking at it, I discovered another problem.
When tail-F'd files may be renamed, tail may fail to track
the target of a rename.
good catch and very useful test case! I am going to like the test
driven development we we had today :-)
This patch
Joey Hess wrote:
Package: coreutils
Version: 8.1-1
I run tail -q --follow=name --retry -n 2 , tailing all log files
in /var/log.
Starting I think with version 8.0, this has began to die approximatly
once a week.
Thanks for the report.
The tail -F may abort bug has just been fixed
Does anyone have pending changes that belong in coreutils-8.3?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 12/30/2009 4:13 AM:
Does anyone have pending changes that belong in coreutils-8.3?
Yes. utimensat still needs help before touch(1) will work on ntfs-3g.
Now that I have feedback from 3trn3e8 (I guess he/she prefers to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to ctrn3e8 on 12/29/2009 10:38 PM:
I couldn't find where UTIME_NOW etc. is defined, so I just pulled the
values off the internet.
They are defined in sys/stat.h. I keep forgetting that while many
systems implicitly include sys/stat.h as
Hi,
I can't correctly format the tail help message because the string
src/tail.c:316 (git master) is split in two parts. The first part is at
line 316 and the second part (without new line between) is line 312.
Could you join the messages together or add a new line at the end of the
first?
Eric Blake wrote:
According to Jim Meyering on 12/30/2009 4:13 AM:
Does anyone have pending changes that belong in coreutils-8.3?
Yes. utimensat still needs help before touch(1) will work on ntfs-3g.
Now that I have feedback from 3trn3e8 (I guess he/she prefers to remain
behind a
Stéphane Raimbault wrote:
I can't correctly format the tail help message because the string
src/tail.c:316 (git master) is split in two parts. The first part is at
line 316 and the second part (without new line between) is line 312.
Could you join the messages together or add a new line at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 12/30/2009 5:50 AM:
So in general, the problem can be characterized precisely by the presence
of UTIME_OMIT, and can be worked around with a mere stat() (no gettime()
is needed, since UTIME_NOW still works). Do you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 12/30/2009 7:07 AM:
I have tested this on Linux, with xfs. I will provide a followup patch
for the coreutils NEWS file.
Here's what I'm considering for coreutils (modified to hide email addresses).
- --
Don't work too
Eric Blake wrote:
According to Eric Blake on 12/30/2009 7:07 AM:
I have tested this on Linux, with xfs. I will provide a followup patch
for the coreutils NEWS file.
Here's what I'm considering for coreutils (modified to hide email addresses).
...
Subject: [PATCH] touch: work around ntfs-3g
Update of bug #28113 (project coreutils):
Status:None = Fixed
Open/Closed:Open = Closed
___
Follow-up Comment #1:
This was fixed in
Original Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/498212
The default dircolours for an others writable directory is set as blue
over green:
STICKY_OTHER_WRITABLE 30;42 # dir that is sticky and other-writable (+t,o+w)
OTHER_WRITABLE 34;42 # dir that is other-writable
C de-Avillez wrote:
Original Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/498212
The default dircolours for an others writable directory is set as blue
over green:
STICKY_OTHER_WRITABLE 30;42 # dir that is sticky and other-writable (+t,o+w)
OTHER_WRITABLE 34;42 #
On 12/30/2009 01:04 PM, Jim Meyering wrote:
I don't see the problem: it's readable for me when using
roxterm as my terminal emulator.
(snip)
That final line is rendered with a blue background and
with green foreground text, other-writable.
You meant green background with blue
Update of bug #28308 (project coreutils):
Severity: 3 - Normal = 1 - Wish
Status:None = Wont Fix
Open/Closed:Open = Closed
Follow-up Comment #2, bug #28308 (project coreutils):
Please elaborate the bar. The information displayed, when needed, is used
many times in other shell context and the used quoted do not support
interoperability.
___
Reply to this
alias dir='ls --color=auto --format=vertical'
The above alias doesn't distinguish the color for a symbol link
pointing to a file and a symbol link pointing to a dir. I'm wondering
if there is a way to configure it to do so?
On 30/12/09 23:09, Peng Yu wrote:
alias dir='ls --color=auto --format=vertical'
The above alias doesn't distinguish the color for a symbol link
pointing to a file and a symbol link pointing to a dir. I'm wondering
if there is a way to configure it to do so?
How about adding a -L ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peng Yu on 12/30/2009 4:09 PM:
alias dir='ls --color=auto --format=vertical'
The above alias doesn't distinguish the color for a symbol link
pointing to a file and a symbol link pointing to a dir. I'm wondering
if there is a way to
On Wed, Dec 30, 2009 at 7:34 PM, Eric Blake e...@byu.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peng Yu on 12/30/2009 4:09 PM:
alias dir='ls --color=auto --format=vertical'
The above alias doesn't distinguish the color for a symbol link
pointing to a file and a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peng Yu on 12/30/2009 7:30 PM:
Use dircolors (as in adding the line:
eval `dircolors path/to/preferences`
http://linux.die.net/man/5/dir_colors
According to the above page, can I put the line 'LINK target' in
~/.dir_colors
On Wed, Dec 30, 2009 at 8:47 PM, Eric Blake e...@byu.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peng Yu on 12/30/2009 7:30 PM:
Use dircolors (as in adding the line:
eval `dircolors path/to/preferences`
http://linux.die.net/man/5/dir_colors
According to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peng Yu on 12/30/2009 7:51 PM:
Then that is probably a feature request that has not yet been implemented.
Would you like to try your hand at coding it?
Do you mean that I modify the source code of coreutils? I'd like to
take a look
On 31/12/09 02:30, Peng Yu wrote:
On Wed, Dec 30, 2009 at 7:34 PM, Eric Blakee...@byu.net wrote:
LINK target
I don't want the color of the link the same as the color of the
target. I want the color of the link that points to a file different
from the color of the link that points to a dir. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peng Yu on 12/30/2009 8:34 PM:
I wouldn't be on for adding more color combinations to handle
cases like this. Perhaps a combination of LINK target with the
-F option would suffice. That would use the color of the target
while also
26 matches
Mail list logo
