On Sat, 28 Nov 2009 14:51:58 -0500, Steven wrote:
> I am very interested in this question on multiple levels.
>
> Let's start at the first level:
>
> foo=$(< fn bar)
>
> apparently is functionally equivalent to
>
> foo=$( bar < fn )
True. File fn is opened for input on file descriptor 0 (stdi
On Sat, Nov 28, 2009 at 05:34:28PM -0500, Steven W. Orr wrote:
> Now you've jinxed it! I'll betcha a buck that Murphy is subscribed to this
> list and that's the next thing that's going to happen. It'll probably be a
> feature of ZFS. ;-)
I'm willing to bet up to *three* imaginary dollars that ZFS
On 11/28/09 15:05, quoth Matthew Miller:
> On Sat, Nov 28, 2009 at 02:51:58PM -0500, Steven W. Orr wrote:
>> Yes, I agree that if I see that script hanging on a regular basis then I
>> will provide trace data to Bugzilla for further analysis. But this begs
>> two questions:
>
> It's pretty importa
On Sat, Nov 28, 2009 at 02:51:58PM -0500, Steven W. Orr wrote:
> Yes, I agree that if I see that script hanging on a regular basis then I
> will provide trace data to Bugzilla for further analysis. But this begs
> two questions:
It's pretty important to know where it's hanging. I don't think it's
On 11/28/09 03:53, quoth Michael Schwendt:
> On Fri, 27 Nov 2009 23:20:23 -0500, Matthew wrote:
>
>> On Fri, Nov 27, 2009 at 10:55:17PM -0500, Steven W. Orr wrote:
>>> I can't believe this is a real bug. I'm submit it to bugzilla. It's in F10,
>>> 11
>>> and 12. I'd be curious to know just how ol
On Sat, Nov 28, 2009 at 09:53:47AM +0100, Michael Schwendt wrote:
> > Have you tried it? The code in the file isn't an error; it's just very
> > obscure bash syntax. That is, $(< /some/file ) is obscure, and $(<
> > /some/file filter-command ) is *really* obscure. Doesn't seem to be
> > documented
On Fri, 27 Nov 2009 23:20:23 -0500, Matthew wrote:
> On Fri, Nov 27, 2009 at 10:55:17PM -0500, Steven W. Orr wrote:
> > I can't believe this is a real bug. I'm submit it to bugzilla. It's in F10,
> > 11
> > and 12. I'd be curious to know just how old this bug is.
> > Contents of mlocate.cron is:
On Fri, Nov 27, 2009 at 10:55:17PM -0500, Steven W. Orr wrote:
> I can't believe this is a real bug. I'm submit it to bugzilla. It's in F10, 11
> and 12. I'd be curious to know just how old this bug is.
> Contents of mlocate.cron is:
> #!/bin/sh
> nodevs=$(< /proc/filesystems awk '$1 == "nodev" { p
I can't believe this is a real bug. I'm submit it to bugzilla. It's in F10, 11
and 12. I'd be curious to know just how old this bug is.
Contents of mlocate.cron is:
#!/bin/sh
nodevs=$(< /proc/filesystems awk '$1 == "nodev" { print $2 }')
renice +19 -p $$ >/dev/null 2>&1
ionice -c2 -n7 -p $$ >/dev
