Karaf
  1. Karaf
  2. KARAF-1757

Welcome message incorrect during ssh session or using bin/client.

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.9
    • Fix Version/s: 2.2.10, 2.3.0, 3.0.0
    • Component/s: karaf-shell
    • Labels:
      None
    • Environment:

      Debian 6.0.5

      Description

      A remote ssh connection to karaf displays the following welcome message:

      Shell
              __ __                  ____
             / //_/____ __________ _/ __/
            / ,<  / __ `/ ___/ __ `/ /_
           / /| |/ /_/ / /  / /_/ / __/
          /_/ |_|\__,_/_/   \__,_/_/
      
        Apache Karaf (2.2.9)
      
      Hit '<tab>' for a list of available commands
      and '[cmd] --help' for help on a specific command.
      Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Karaf.
      

      The last line is incorrect. Pressing <ctrl-d> just closes ssh connection / exits the client. Karaf ist not shut down. <ctrl-d> appears to be equivalent to the command 'logout'.

        Activity

        Show
        Freeman Fang added a comment - commit fix http://svn.apache.org/viewvc?rev=1383221&view=rev for trunk http://svn.apache.org/viewvc?rev=1383219&view=rev for 2.3.x branch http://svn.apache.org/viewvc?rev=1383213&view=rev for 2.2.x branch
        Hide
        Freeman Fang added a comment -

        +1
        yeah, seems the only option is to use different branding

        Show
        Freeman Fang added a comment - +1 yeah, seems the only option is to use different branding
        Hide
        Andreas Pieber added a comment -

        oh... right now the same branding is used on the ssh login as on the regular startup. TBH the only real option I see to workaround this issue is to allow a different branding for ssh connections as for "regular startups". WDYT?

        Show
        Andreas Pieber added a comment - oh... right now the same branding is used on the ssh login as on the regular startup. TBH the only real option I see to workaround this issue is to allow a different branding for ssh connections as for "regular startups". WDYT?

          People

          • Assignee:
            Freeman Fang
            Reporter:
            Raphael Majeed
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development