karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hendy Irawan (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-1226) Karaf Client cannot run a script
Date Fri, 24 Feb 2012 12:37:48 GMT

     [ https://issues.apache.org/jira/browse/KARAF-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hendy Irawan updated KARAF-1226:
--------------------------------

    Description: 
Example usage:

{code}
echo osgi:ls | bin/client
{code}

or:

{code}
bin/client < commands.karafsh
{code}

or redirecting stdout to file:

{code}
echo osgi:ls | bin/client > bundles.txt
{code}

Expected outcome:
1. Output of the command printed to stdout
2. Banners etc. (if any) printed to stderr
3. Shell prompt should not be output at all
4. The client exits immediately

Actual behavior:
1. All output including banners and the shell prompt are printed to stdout (only)
2. The client then hangs but still using around 20% CPU usage. It's not possible to Ctrl+C,
and need to kill the process.

GNU tools (like bash) tend to detect the presence of an input stream, to differ between interactive
mode and a batch mode.
If this is not possible, can also add a switch e.g. "--batch" or "-b" for "Batch mode".

BTW this should also be possible to do on karaf launcher itself (i.e. start Karaf, execute
command(s), then immediately shutdown the runtime).

  was:
Example usage:

{code}
echo osgi:ls | bin/client
{code}

or:

{code}
bin/client < commands.karafsh
{code}

or redirecting stdout to file:

{code}
echo osgi:ls | bin/client > bundles.txt
{code}

Expected outcome:
1. Output of the command printed to stdout
2. Banners etc. (if any) printed to stderr
3. Shell prompt should not be output at all
4. The client exits immediately

Actual behavior:
1. All output including banners and the shell prompt are printed to stdout (only)
2. The client then hangs but still using around 20% CPU usage. It's not possible to Ctrl+C,
and need to kill the process.

GNU tools (like bash) tend to detect the presence of an input stream, to differ between interactive
mode and a batch mode.
If this is not possible, can also add a switch e.g. "--batch" or "-b" for "Batch mode".

    
> Karaf Client cannot run a script
> --------------------------------
>
>                 Key: KARAF-1226
>                 URL: https://issues.apache.org/jira/browse/KARAF-1226
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-shell
>    Affects Versions: 2.2.5
>         Environment: Ubuntu 11.10 64-bit, OpenJDK 6
>            Reporter: Hendy Irawan
>
> Example usage:
> {code}
> echo osgi:ls | bin/client
> {code}
> or:
> {code}
> bin/client < commands.karafsh
> {code}
> or redirecting stdout to file:
> {code}
> echo osgi:ls | bin/client > bundles.txt
> {code}
> Expected outcome:
> 1. Output of the command printed to stdout
> 2. Banners etc. (if any) printed to stderr
> 3. Shell prompt should not be output at all
> 4. The client exits immediately
> Actual behavior:
> 1. All output including banners and the shell prompt are printed to stdout (only)
> 2. The client then hangs but still using around 20% CPU usage. It's not possible to Ctrl+C,
and need to kill the process.
> GNU tools (like bash) tend to detect the presence of an input stream, to differ between
interactive mode and a batch mode.
> If this is not possible, can also add a switch e.g. "--batch" or "-b" for "Batch mode".
> BTW this should also be possible to do on karaf launcher itself (i.e. start Karaf, execute
command(s), then immediately shutdown the runtime).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message