Stan Horwitz wrote:
>
> On Sun, 6 May 2001, Roger Fajman wrote:
> >
> > LCMD puts a command in LISTSERV's queue and the result is emailed back
> > to the userid that LCMD ran under.  You probably want the LCMDX command
> > that's described in the LISTSERV Developer's Guide.
>
> Thanks Roger. I compiled lcmdx as per the directions in the Developer's
> Guide. I was then able to get an interactive response by sending the
> Listserv here some rudimentary commands such as "list", but its still not
> what I am looking for. The lcmdx utility is a big step in the right
> direction, but what I also need to do is get back an interactive response
> from a command such as
>
>   lcmdx cronkite address passwd query listname for *@*
>
> when I issue this command, I get something like a "no match" message, but
> when I issue a slightly different command such as:
>
>   lcmdx cronkite address passwd query listname for *
>
> I think what happens is that the Unix shell on our Listserv is replacing
> the asterisk with the name of every file in our Listserv's home directory
> then trying to query that list for a subscription for the "address" field
> in the lcmdx command rather than just querying the particular "listname"
> for all of its subscriptions.

Hmm, try this

lcmdx "cronkite address passwd query listname for *"
or
lcmdx 'cronkite address passwd query listname for *'
or
lcmdx cronkite address passwd query listname for \*

If it's just a shell substitution issue one of those ought to fix it....

Best,
Al Iverson
--
Al Iverson -- [log in to unmask] -- Minneapolis, Minnesota
Support Jazz in Minnesota! -- http://www.mnjazz.com/
All opinions are mine alone unless I state otherwise.