Re: Modifiable NMERGE in sort

"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > + sort accepts a new option --merge-batch-size=NMERGE, where NMERGE > + represents the maximum number of inputs that will be merged at once. > + When more than NMERGE inputs are present temporary files are used. I've just realized that adding --merge-

Re: Modifiable NMERGE in sort

On Tue, Apr 1, 2008 at 4:11 AM, Jim Meyering <[EMAIL PROTECTED]> wrote: > So please see if you can find an option name that does not start with > --merge, and, ideally, that doesn't influence interpretation of any > other option abbreviations. > How about --batch-size. It doesn't have an initi

avoid failure of root-run "make check"

I've just pushed a few change sets. These two avoid failures that you'd see only when running "make check" as root. The second is even less likely in that to trigger the failure you'd have to be running "make check" as root on a system with SELinux in enforcing mode, but with mcstransd deactivate

FYI: bootstrap dangling symlink tweaks

I've just pushed a couple tweaks for the dangling symlink deletion part of bootstrap. I'll do the same in gnulib shortly. The first is because I found a few persistent dangling symlinks in lib/*.[ch] to be annoying. The second was because when I ran bootstrap's find command manually (without the

new snapshot available: coreutils-6.10.169-a1a0b

I expect to make a release as soon as autoconf-2.62 is released. As such, this snapshot was bootstrapped with the very latest autoconf and automake (and as usual, up-to-the-minute gnulib). There has been a little churn in gnulib, surrounding some nice new strtod tests from Eric Blake. Some of tho

install when used with -D, -o, and -g

When install is run with -D, -o, and -g, the directories created are owned by the user who spawned install, rather than the user specified in -o. Is this expected behavior? In my humble opinion, its reasonable to assume the intention of the user is that everything created by install gets the user

Re: [PATCH] Add timeout utility

On Tuesday 01 April 2008, Pádraig Brady wrote: > +  /* Setup handlers before fork() so that we > +   * handle any signals caused by child, without races.  */ > +  signal (SIGALRM, cleanup);    /* our timeout.  */ > +  signal (SIGINT, cleanup);     /* Ctrl-C at terminal for example.  */ > +  signal

Re: configure fails on Maemo/OS2008 (sed: no previous regexp)

Elbert Pol <[EMAIL PROTECTED]> wrote: > I've attach the log file This is the relevant part: checking for struct spwd.sp_pwdp... no^M checking for getspnam... no^M checking for library containing crypt... none required^M + c=./configure.ac^M + re=^gl_INCLUDE_EXCLUDE_PROG(.* \[\(.*\)\])^M + sed -n

[PATCH] Add timeout utility

attached >From e2c2d212bfea29540bb433bb8d00e1e9e9fd3ff6 Mon Sep 17 00:00:00 2001 From: =?utf-8?q?P=C3=A1draig=20Brady?= <[EMAIL PROTECTED]> Date: Fri, 28 Mar 2008 11:05:55 + Subject: [PATCH] Add new program: timeout * AUTHORS: Register as the author * NEWS: Mention this change * README: Add ti

Re: df error

jose antonio arjona garzon wrote: > When I run the application it shows me this error: > > df: `/var/cache/pbuilder/build/8394/dev/pts': No existe el fichero o el > directorio > > No existe el fichero o el directorio -> The file or directory doesn't > exists. Because pbuilder is a chroot projec

Re: FYI: bootstrap dangling symlink tweaks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 4/1/2008 9:25 AM: | The first is because I found a few persistent dangling symlinks | in lib/*.[ch] to be annoying. | +find "$m4_base" "$source_base" \ | + -name '*.m4' -depth -type l -xtype l -delete > /dev/null 2>&1 E

Re: FYI: bootstrap dangling symlink tweaks

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/1/2008 9:25 AM: > | The first is because I found a few persistent dangling symlinks > | in lib/*.[ch] to be annoying. > > | +find "$m4_base" "$source_base" \ > | + -name '*.m4' -depth -type l -xtype l -delete > /dev/null 2>&1 >

Re: FYI: bootstrap dangling symlink tweaks

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/1/2008 9:25 AM: > | The first is because I found a few persistent dangling symlinks > | in lib/*.[ch] to be annoying. > > | +find "$m4_base" "$source_base" \ > | + -name '*.m4' -depth -type l -xtype l -delete > /dev/null 2>&1

Re: cp -u vs. vfat's TWO seconds

[EMAIL PROTECTED] wrote: > Bad news fellows, regarding: > > `-u' > `--update' > Do not copy a non-directory that has an existing destination with > the same or newer modification time. If time stamps are being > preserved, the comparison is to the source time stamp truncate