New util suggestion: timeout

What: timeout, executes the sub-command a-la GNU time/nice, but takes arguments to control the amount of wallclock time the process is allowed. Why: - ulimit for real time - No current util (GNU or otherwise) widely distributed (AFAIK) - Useful in scripting, particularly with network apps I was s

Re: coreutils bug with "ln x d/"

[EMAIL PROTECTED] (Paul Jarc) writes: > http://lists.gnu.org/archive/html/bug-coreutils/2004-02/msg00037.html> > The main difference is that --syntactic/--as-is still lets you have > the convenience of omitting the target basename if it's the same as > the source, by providing a target that ends w

Re: coreutils bug with "ln x d/"

Paul Eggert <[EMAIL PROTECTED]> wrote: > While looking at cp, ln, and mv and thinking about how to implement > the -D/--no-destdir option I proposed in > , I think this would be more useful (you suggested calling it --as-is): h

Re: coreutils bug with "ln x d/"

Paul Eggert <[EMAIL PROTECTED]> wrote: > OK, I split the patch into two. This takes a more conservative > approach than what I wrote above: the first patch fixes the bug, and > the second patch (which I'll send in my next message) is the cleanup > patch. > > These two patches supersedes the long p

Re: coreutils bug with "ln x d/"

Here's the second (cleanup) patch; it assumes the first (bugfix) patch has already been applied. 2004-06-27 Paul Eggert <[EMAIL PROTECTED]> Use more-consistent rules among cp, ln, and mv when dealing with last operands that are (or look like) directories. * src/cp.c (ta

Re: coreutils bug with "ln x d/"

Jim Meyering <[EMAIL PROTECTED]> writes: >> If you like, I think I can split >> up the patch into two parts: a code- and diagnostic-cleanup only, and >> a bug fix. (I would do this by modifying my version to have the >> bug :-) > > I would indeed appreciate that. OK, I split the patch into t