I can’t imagine it taking that long to do that no, although environment may
make a difference?
If you can come up with a reproduction, it might be worth creating a jira issue
with a reproduction template or something
> On Apr 20, 2021, at 07:09, James McMahon wrote:
>
> I opted to call a bas
I opted to call a bash script as Command Path. I felt the script approach
gave me a lot more flexibility to do just about anything I want without
worrying about syntax of arguments, quoting, etc etc in the
ExecuteScriptCommand itself. If anyone is interested this is my simple
example:
ExecuteStrea
Thanks very much. Will try it momentarily, this morning.
On Mon, Apr 19, 2021 at 9:30 PM Otto Fowler wrote:
> Piping is part of the shell I believe, so you can’t do it with arguments
> in that way.
>
> If you make your shell the executable however, you should then be able to
> pass things as sep
Piping is part of the shell I believe, so you can’t do it with arguments in
that way.
If you make your shell the executable however, you should then be able to pass
things as separate
arguments.
I would start with
"/bin/sh” as the executable and arguments of
"-c”
“ls | ws -l”
Or, you can wri
Good evening. I’d like to do a file count of ${directory}. I can use an
ExecuteStreamCommand processor with that as Command Arguments and ls as
Command Path. I’ll set Output Destination Attribute to be myFileCount, and
will drop Max Attribute Length to ten. That will be ample characters for my
coun
