From: Thomas Goirand <thomas@goirand.fr>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] mlmmj-maintd recursively
Date: Mon, 11 Oct 2010 13:59:14 +0000 [thread overview]
Message-ID: <4CB31832.5020006@goirand.fr> (raw)
In-Reply-To: <AANLkTi=7mc394VyH4j19zW_+jzpiCH7UXShb3supRJS9@mail.gmail.com>
Ben Schmidt wrote:
> On 11/10/10 9:35 PM, Florian Effenberger wrote:
>> Hi,
>>
>> 2010/10/6 Ben Schmidt<mail_ben_schmidt@yahoo.com.au>:
>>
>>>> Use the -maxdepth option then!
>>>>
>>>> find /var/spool/mlmmj/ -mindepth 1 -maxdepth 1 -type d \
>>>> /usr/bin/mlmmj-maintd -F -d {} \;
>>>>
>>>> the -mindepth 1 will remove /var/spool/mlmmj/ itself that would be
>>>> otherwise listed...
>>>
>>> Wonderful! I should work on my find(1) voodoo.
>>>
>>> I have integrated this into the README for future releases. It will show
>>> up in version control once I get around to pushing it.
>>
>> 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"
:)
So yes, the correct way was:
find /var/spool/mlmmj/ -mindepth 1 -maxdepth 1 -type d \
-exec /usr/bin/mlmmj-maintd -F -d {} \;
Thomas
next prev parent reply other threads:[~2010-10-11 13:59 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 [this message]
2010-10-11 22:13 ` Ben Schmidt
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=4CB31832.5020006@goirand.fr \
--to=thomas@goirand.fr \
--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.