[bug #20970] Trailing slash on directory arguments breaks -name
Follow-up Comment #6, bug #20970 (project findutils): The Austin Group interpretation was issued/approved today. http://www.opengroup.org/austin/interps/uploads/40/14959/AI-186.txt ___ Reply to this item at: http://savannah.gnu.org/bugs/?20970 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: ls: write error: Broken pipe
Dan Nicolaescu [EMAIL PROTECTED] wrote:
Jim Meyering [EMAIL PROTECTED] writes:
Dan Nicolaescu [EMAIL PROTECTED] wrote:
...
I have installed Fedora 8 on another 32bit x86 system, and the problem
appears there too.
(I moved /etc/csh* out of the way, used a freshly created account that
uses /bin/tcsh. I also deleted all the ~/.* files)
I straced the mingetty process corresponding to VT 1, and logged on
there.
The only mention of SIGPIPE is this:
4549 rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
...
Maybe it is done in some library? Here's the part of the strace log that
includes the SIGPIPE handling
I've tracked it down.
mingetty exec's /bin/login, which calls pam stuff, which in turn uses
libdbus. And that is the culprit:
./dbus/dbus-sysdeps-unix.c-_dbus_disable_sigpipe (void)
./dbus/dbus-sysdeps-unix.c-{
./dbus/dbus-sysdeps-unix.c: signal (SIGPIPE, SIG_IGN);
./dbus/dbus-sysdeps-unix.c-}
That function is called by default.
The change that introduced this behavior dates back to 2003:
http://www.redhat.com/archives/message-bus-list/2003-February/msg1.html
Perhaps dbus-the-daemon needs this behavior, but the library code must not
ignore SIGPIPE. Since it's a library, it shouldn't modify process state
at all, but if portability dictates that it ignore SIGPIPE temporarily,
it should be careful to restore the preceding handler asap. The dbus
library can avoid the problem altogether when a system supports sendto's
new POSIX-specified MSG_NOSIGNAL flag (just test #ifdef MSG_NOSIGNAL):
MSG_NOSIGNAL
Requests not to send SIGPIPE on errors on stream oriented
sockets when the other end breaks the connection. The
EPIPE error is still returned.
I'm filing a bug report to the dbus folks.
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: seq .1 .1 would mistakenly generate no output on FreeBSD 6.1
Jim Meyering [EMAIL PROTECTED] writes: It seems to have exposed a problem in gnulib's vasnprintf.c: I think this is because the revised (core-dumping) 'seq' is calling vasnprintf with the equivalent of printf (%.1Lf, 0.8L), whereas due to the strange compiler settings on FreeBSD the original (non-core-dumping) 'seq' called vasnprintf with the equivalent of printf (%.1Lf, (long double) (double) 0.8L). I guess that the bug lies in the printing of a long double value that is not exactly representable as a double. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: seq .1 .1 would mistakenly generate no output on FreeBSD 6.1
Paul Eggert [EMAIL PROTECTED] wrote:
...
I looked at the revised print_numbers function and found what I think
is one or two other instances of similar problems. I hope the
following code will have a better chance of surviving similar problems
in the future. (The proposed code is a tad shorter and avoids some
code duplication and IF_LINT stuff; that's a good sign...)
2007-11-18 Paul Eggert [EMAIL PROTECTED]
* src/seq.c (print_numbers): Rewrite in an attempt to avoid the
more-general rounding issues exposed by the previous patch.
It looked ok, so I built and ran tests on freebsd6.1.
Unfortunately, it provokes several new failures:
Abort trap (core dumped)
-: test float-1 failed: exit status mismatch: expected 0, got 134
Abort trap (core dumped)
-: test float-5 failed: exit status mismatch: expected 0, got 134
Abort trap (core dumped)
-: test float-6 failed: exit status mismatch: expected 0, got 134
Abort trap (core dumped)
-: test wid-1 failed: exit status mismatch: expected 0, got 134
Abort trap (core dumped)
-: test wid-2 failed: exit status mismatch: expected 0, got 134
Abort trap (core dumped)
-: test eq-wid-4 failed: exit status mismatch: expected 0, got 134
It seems to have exposed a problem in gnulib's vasnprintf.c:
freebsd6$ gdb --args ./seq 0.8 0.1 0.9
GNU gdb 6.6
(gdb) r
Starting program: /tmp/coreutils-6.9.89.27-a9805-dirty/src/seq 0.8 0.1 0.9
0.8
Program received signal SIGABRT, Aborted.
0x28136363 in kill () from /lib/libc.so.6
(gdb) up
#1 0x28136300 in raise () from /lib/libc.so.6
(gdb)
#2 0x28135014 in abort () from /lib/libc.so.6
(gdb)
#3 0x0804d8f1 in decode_long_double (x=0.8001084202172485504,
ep=0xbfbfe1e0, mp=0xbfbfe1d8) at vasnprintf.c:877
877 abort ();
(gdb) l
872 if (!(y = 0.0L y 1.0L))
873 abort ();
874 m.limbs[--i] = (hi (GMP_LIMB_BITS / 2)) | lo;
875 }
876 if (!(y == 0.0L))
877 abort ();
878 /* Normalise. */
879 while (m.nlimbs 0 m.limbs[m.nlimbs - 1] == 0)
880 m.nlimbs--;
881 *mp = m;
(gdb) p y
$1 = 0.60009765625
(gdb) p ep
$2 = (int *) 0xbfbfe1e0
(gdb) p *ep
$3 = -858993460
(gdb) up
#4 0x0804e3ca in scale10_round_decimal_long_double (
x=0.8001084202172485504, n=1) at vasnprintf.c:1205
1205 void *memory = decode_long_double (x, e, m);
(gdb) p x
$4 = 0.8001084202172485504
(gdb) dow
#3 0x0804d8f1 in decode_long_double (x=0.8001084202172485504,
ep=0xbfbfe1e0, mp=0xbfbfe1d8) at vasnprintf.c:877
877 abort ();
(gdb) l
872 if (!(y = 0.0L y 1.0L))
873 abort ();
874 m.limbs[--i] = (hi (GMP_LIMB_BITS / 2)) | lo;
875 }
876 if (!(y == 0.0L))
877 abort ();
878 /* Normalise. */
879 while (m.nlimbs 0 m.limbs[m.nlimbs - 1] == 0)
880 m.nlimbs--;
881 *mp = m;
(gdb) p m
$5 = {
nlimbs = 2,
limbs = 0x805c050
}
(gdb) p *(m.limbs)@m.nlimbs
$6 = {2576980377, 1677721}
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: seq .1 .1 would mistakenly generate no output on FreeBSD 6.1
Paul Eggert [EMAIL PROTECTED] wrote: Jim Meyering [EMAIL PROTECTED] writes: It seems to have exposed a problem in gnulib's vasnprintf.c: I think this is because the revised (core-dumping) 'seq' is calling vasnprintf with the equivalent of printf (%.1Lf, 0.8L), whereas due to the strange compiler settings on FreeBSD the original (non-core-dumping) 'seq' called vasnprintf with the equivalent of printf (%.1Lf, (long double) (double) 0.8L). I guess that the bug lies in the printing of a long double value that is not exactly representable as a double. FYI, this happens with both gcc-3.4.3 and gcc-4.2-20070307. The latter reports freebsd6$ gcc -v Using built-in specs. Target: i386-unknown-freebsd6.1 Configured with: ../gcc-4.2-20070307/configure --enable-decimal-float --enable-languages=c,c++ --with-gmp=/usr/local --with-mpfr=/usr/local Thread model: posix gcc version 4.2.0 20070307 (prerelease) ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
hello
hello, how I can correct the time in RedHat Linux? with command time or date and how? I wait for your answer... if you want... thanks a lot... ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Zend Core 2.5 installation
I have followed the installation instructions for Zend Core 2.5 on Linux (RHEL 4). I successfully unzipped the files, but when I issue the commands in the guide install -y or install -n , I get an invalid option error and when I use install -g, I get an error for too few arguments. Please tell me where to go to find proper installation instructions (preferably GUI, I'm a linux newbie). Thanks, Andre Augustus Application Developer T (919) 463-7240 Global Knowledge LEARNING. To Make a Difference http://www.globalknowledge.com http://www.globalknowledge.com ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Leopard Compile Error...
When compiling coreutils for MacOS X 10.5.x Leopard, I get the following error after a minute or two of compiling: gcc -std=gnu99 -I. -I../lib -I../lib -I/usr/local/include -g -O2 - MT date.o -MD -MP -MF .deps/date.Tpo -c -o date.o date.c mv -f .deps/date.Tpo .deps/date.Po gcc -std=gnu99 -g -O2 -o date date.o ../lib/libcoreutils.a -L/usr/ local/lib -lintl -liconv -lc -Wl,-framework -Wl,CoreFoundation ../lib/ libcoreutils.a Undefined symbols: _rpl_putenv$UNIX2003, referenced from: _main in date.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [date] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 This, of course, is after executing the standard: $ ./configure $ make It appears that Leopard's UNIX 2003 compliance libraries are interfering with a macro in coreutils, but I don't have the time or energy to figure out what everything does and trusting that I did it right. I can provide more information on request. -Jeff R - Jeffrey Reinecke [EMAIL PROTECTED] cell: 509-714-2396 blog.paploo.net ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: hello
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ginis.com wrote: hello, how I can correct the time in RedHat Linux? with command time or date and how? Yes, date can do that. To make the change persistent, you probably also need the hwclock commands. Both will require root privileges to effect the change. See the documentation for those commands for further information. The time command is for timing how long a program runs; not for setting the system time. In the future, please try to choose a more descriptive line for your subject; many people choose whether or not to read (and answer) a message based on the subject line. It helps people to know what the topic of the message is, and how likely they are to have something to say. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHQ2I67M8hyUobTrERCGNVAKCObmUEWDa+pGv9e1QbF83lmfAgoQCfY880 rj3gMa21J8SJonWzUbvDeN4= =S36I -END PGP SIGNATURE- ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: Zend Core 2.5 installation
On Tue, 20 Nov 2007, Andre Augustus wrote: I have followed the installation instructions for Zend Core 2.5 on Linux (RHEL 4). I successfully unzipped the files, but when I issue the commands in the guide install -y or install -n , I get an invalid option error and when I use install -g, I get an error for too few arguments. Please tell me where to go to find proper installation instructions (preferably GUI, I'm a linux newbie). This mailing list is for reporting problems in GNU coreutils only. It sounds like in this case the documentation for the product you're installing is incorrect. The best course of action would be to seek help from the organisation which supplied you with Zend Core; I see that their website has a support forum. Cheers, Phil ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
What is the difference to Gnu UnxUtils ?
Hello *.* there is another collection of unix utilities very, very similar to the CoreUtils one: GNU UnxUtils available from here: http://sourceforge.net/projects/unxutils/ What is the difference ? Is e.g. one for Solaris the other more Linux oriented? Which one has more capabilities ? Which one is more stable ? Thank you for the answers Ben ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: What is the difference to Gnu UnxUtils ?
Ben Stover wrote: there is another collection of unix utilities very, very similar to the CoreUtils one: GNU UnxUtils available from here: http://sourceforge.net/projects/unxutils/ What is the difference ? The summary on that project page says it all. Port of the most important GNU utilities to Windows It is not _another_ collection. It _is_ GNU software which has been ported and compiled for MS-Windows. The GNU Project includes many components such as the coreutils project which are part of the GNU Operating System. The GNU System is an operating system created entirely from free software. Because it is free software people are free to study the source code and to port it to other systems. The unixutils on SourceForge appears to be one of the (many) ports of GNU software to MS-Windows. But remember that GNU is designed to be a full operating system and is not related to MS-Windows. You can learn about the GNU Project here: http://www.gnu.org/ Is e.g. one for Solaris the other more Linux oriented? GNU software is, of course, GNU System oriented. The UnxUtils on SourceForge appears to be specifically MS-Windows. If you are looking for Solaris code then the latest stable source code release should be the best available source for you. GNU is all about the freedom provided by the source code and therefore all about the source. GNU does not usually make precompiled binaries available. However many different individuals and organizations do. If you are looking for precompiled binaries for Solaris I am sure that some could recommend something if you asked. Which one has more capabilities ? Which one is more stable ? They appear to be a port of selected GNU utilities to MS-Windows. When I looked at the source bundle and I see this list of source files from the GNU Project and other sources. bc-1.05 flex-2.5.4 help ncompress-4.2.4 sh-utils-1.13 bison-1.28 fsplit id-utils-3.2d patch-2.5sharutils-4.1 bzip2-0.9.0bgawk-3.0.4 indent-2.2.0 plotmtv-1.4.1shellutils-1.9.4 bzip2-1.0.1 grep-2.4 indent-2.2.6 recode-3.5 tar-1.12 diffutils-2.7 grep-2.5.1 jwhois-2.4.1 recode-3.6 textutils-2.0 file-4.02 groff-1.11 less-340 rman-3.0.7 textutils-2.1 fileutils-3.16 gsar110 m4-1.4 sed-3.02 which-2.4 findutils-4.1 gzip-1.2.4a make-3.78.1sed-4.0.7zsh Some of those versions are really quite old! I would definitely recommend that you look elsewhere for your MS-Windows programs. For MS-Windows the Cygwin tools are a often recommended location for precompiled binaries. http://cygwin.com/ Bob ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
