From: Richard Mortimer <richm@oldelvet.org.uk>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] mlmmj-maintd recursively
Date: Tue, 12 Oct 2010 07:29:04 +0000 [thread overview]
Message-ID: <4CB40E40.30208@oldelvet.org.uk> (raw)
In-Reply-To: <AANLkTi=7mc394VyH4j19zW_+jzpiCH7UXShb3supRJS9@mail.gmail.com>
On 12/10/2010 04:35, Ben Schmidt wrote:
> On 12/10/10 1:33 PM, Thomas Goirand wrote:
>>
>> ----- Original message -----
>>>> 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.
>>
>> Using the shell, you add a \
>> to tell that you want to go to the line but \
>> you haven't finished your sentence... :)
>>
>> Thomas
>
> No, I meant the forward slash at the end of /var/spool/mlmmj/. With it,
> on my system, find gives things such as
>
> /var/spool/mlmmj//test-list
>
> to the command it executes. Note the double slash. It's arguably a bug
> in my find command, probably doesn't happen in other implementations,
> and doesn't affect the interpretation of the path, at least on my
> system, but it's more usual not to have the double, and removing the
> trailing slash and just using /var/spool/mlmmj achieves this.
>
> I left the backslash in. That's perfectly common shell syntax that
> anyone competent should recognise.
>
The trailing \; is generally required too. Without it the shell can/will
treat the ; as a command separator rather than a command argument. Some
versions of find may be happy without the ; at the end of exec but not
all are.
Regards
Richard
next prev parent reply other threads:[~2010-10-12 7:29 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
2010-10-12 2:33 ` Thomas Goirand
2010-10-12 3:35 ` Ben Schmidt
2010-10-12 7:29 ` Richard Mortimer [this message]
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=4CB40E40.30208@oldelvet.org.uk \
--to=richm@oldelvet.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox