All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] mlmmj-maintd recursively
Date: Mon, 11 Oct 2010 22:13:35 +0000	[thread overview]
Message-ID: <4CB38C0F.6080909@yahoo.com.au> (raw)
In-Reply-To: <AANLkTi=7mc394VyH4j19zW_+jzpiCH7UXShb3supRJS9@mail.gmail.com>

On 12/10/10 12:59 AM, Thomas Goirand wrote:
>>> at least on Ubuntu, it has to read
>>>
>>> find /var/spool/mlmmj/ -mindepth 1 -maxdepth 1 -type d -exec
>>> /usr/bin/mlmmj-maintd -F -d {} \;
>>>
>>> (you were missing the -exec)
>>
>> Oops! Thanks. Fixed.
>>
>> Ben.
>
> When I wrote "hint", in meant:
>
> "I'm using something unchecked from the top of my head, please test
> anything before writing a doc, or using it in production"
>
> :)

Yeah, I did try it out; you actually got it right the first time anyway,
IIRC. The -exec just got lost when the -m..depth options were added and
I didn't notice. So it tested fine, but when I copy/pasted for the docs,
it wasn't. My oops, not yours!

:-)

> So yes, the correct way was:
>
> find /var/spool/mlmmj/ -mindepth 1 -maxdepth 1 -type d \
> 	-exec /usr/bin/mlmmj-maintd -F -d {} \;

Actually, on my system it looks like the trailing slash should be
omitted, too, or there is a double slash in the argument passed to
mlmmj-maintd. Probably doesn't matter, but is a little unconventional,
so I'll take the slash out of the docs.

Ben.






  parent reply	other threads:[~2010-10-11 22:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 22:09 [mlmmj] mlmmj-maintd recursively Florian Effenberger
2010-10-05  9:34 ` Thomas Goirand
2010-10-05  9:38 ` Mads Martin Jørgensen
2010-10-05 23:23 ` Ben Schmidt
2010-10-11 10:35 ` Florian Effenberger
2010-10-11 11:21 ` Ben Schmidt
2010-10-11 13:59 ` Thomas Goirand
2010-10-11 22:13 ` Ben Schmidt [this message]
2010-10-12  2:33 ` Thomas Goirand
2010-10-12  3:35 ` Ben Schmidt
2010-10-12  7:29 ` Richard Mortimer
2010-10-12 10:19 ` Ben Schmidt
2010-10-12 17:59 ` Franky Van Liedekerke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB38C0F.6080909@yahoo.com.au \
    --to=mail_ben_schmidt@yahoo.com.au \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.