Damn-Small-Linux telnet server freezes

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I'm using Damn Small Linux (or "DSL") (which is based "non-purely" on Debian - I have access to apt-get) in a Virtual Machine.

I installed telnet server (telnetd + xinetd).

I'm also running another Virtual Machine, this time with installed telnet client in it (Linux distribution AntiX).



When I'm connecting with telnet from AntiX to DSL, I'm prompted about login+password, which is ok.

But then, when I log-in it's just shows a message and then freezes. By "freezes" I mean:



  1. I can type anything I want, but when I press ENTER the commands are not executed. Instead the cursor just moves to the next line.

  2. The line "dsl@dsl$ " (which prompts for entering a command) does not show.

  3. In the server side (DSL) the windows flash (close) when the login happens.

It seems like some process is running, but the problem is that it never stops. I have to type "Ctrl+C" to stop it and continue with the command line.



Here is a screenshot when it freezes:telnet freeze screenshot



There is also a warning in DSL's site which says that if you install the wrong application via apt-get, then you can break something, "for Instance the X server"? Could this be X server?



My questions are:



  1. Can I find out which process is running? I'm intended here only to try and make it not start again.

  2. Can I make this process not start upon telnet connection?

Logging in with root also reproduces the error.







share|improve this question


























    up vote
    1
    down vote

    favorite












    I'm using Damn Small Linux (or "DSL") (which is based "non-purely" on Debian - I have access to apt-get) in a Virtual Machine.

    I installed telnet server (telnetd + xinetd).

    I'm also running another Virtual Machine, this time with installed telnet client in it (Linux distribution AntiX).



    When I'm connecting with telnet from AntiX to DSL, I'm prompted about login+password, which is ok.

    But then, when I log-in it's just shows a message and then freezes. By "freezes" I mean:



    1. I can type anything I want, but when I press ENTER the commands are not executed. Instead the cursor just moves to the next line.

    2. The line "dsl@dsl$ " (which prompts for entering a command) does not show.

    3. In the server side (DSL) the windows flash (close) when the login happens.

    It seems like some process is running, but the problem is that it never stops. I have to type "Ctrl+C" to stop it and continue with the command line.



    Here is a screenshot when it freezes:telnet freeze screenshot



    There is also a warning in DSL's site which says that if you install the wrong application via apt-get, then you can break something, "for Instance the X server"? Could this be X server?



    My questions are:



    1. Can I find out which process is running? I'm intended here only to try and make it not start again.

    2. Can I make this process not start upon telnet connection?

    Logging in with root also reproduces the error.







    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I'm using Damn Small Linux (or "DSL") (which is based "non-purely" on Debian - I have access to apt-get) in a Virtual Machine.

      I installed telnet server (telnetd + xinetd).

      I'm also running another Virtual Machine, this time with installed telnet client in it (Linux distribution AntiX).



      When I'm connecting with telnet from AntiX to DSL, I'm prompted about login+password, which is ok.

      But then, when I log-in it's just shows a message and then freezes. By "freezes" I mean:



      1. I can type anything I want, but when I press ENTER the commands are not executed. Instead the cursor just moves to the next line.

      2. The line "dsl@dsl$ " (which prompts for entering a command) does not show.

      3. In the server side (DSL) the windows flash (close) when the login happens.

      It seems like some process is running, but the problem is that it never stops. I have to type "Ctrl+C" to stop it and continue with the command line.



      Here is a screenshot when it freezes:telnet freeze screenshot



      There is also a warning in DSL's site which says that if you install the wrong application via apt-get, then you can break something, "for Instance the X server"? Could this be X server?



      My questions are:



      1. Can I find out which process is running? I'm intended here only to try and make it not start again.

      2. Can I make this process not start upon telnet connection?

      Logging in with root also reproduces the error.







      share|improve this question














      I'm using Damn Small Linux (or "DSL") (which is based "non-purely" on Debian - I have access to apt-get) in a Virtual Machine.

      I installed telnet server (telnetd + xinetd).

      I'm also running another Virtual Machine, this time with installed telnet client in it (Linux distribution AntiX).



      When I'm connecting with telnet from AntiX to DSL, I'm prompted about login+password, which is ok.

      But then, when I log-in it's just shows a message and then freezes. By "freezes" I mean:



      1. I can type anything I want, but when I press ENTER the commands are not executed. Instead the cursor just moves to the next line.

      2. The line "dsl@dsl$ " (which prompts for entering a command) does not show.

      3. In the server side (DSL) the windows flash (close) when the login happens.

      It seems like some process is running, but the problem is that it never stops. I have to type "Ctrl+C" to stop it and continue with the command line.



      Here is a screenshot when it freezes:telnet freeze screenshot



      There is also a warning in DSL's site which says that if you install the wrong application via apt-get, then you can break something, "for Instance the X server"? Could this be X server?



      My questions are:



      1. Can I find out which process is running? I'm intended here only to try and make it not start again.

      2. Can I make this process not start upon telnet connection?

      Logging in with root also reproduces the error.









      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 29 '17 at 11:21









      Jeff Schaller

      32.1k849109




      32.1k849109










      asked Oct 16 '17 at 10:57









      thanopi57

      1084




      1084




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          According to this wiki page about /home/dsl/.bash_profile, the default contents of this file check if you are logging in from ssh, and if not it uses the command startx to start the X11 graphics server:



          #!/bin/bash
          export IRCNICK=DSL
          SSH=`env | grep SSH_CONNECTION`
          RUNLEVEL=`runlevel|cut -f2 -d' '`
          if [ -z "$SSH" ]; then
          if [ $RUNLEVEL -eq 5 ]; then
          startx
          fi
          fi


          So when you login from telnet, ssh is not detected, and you are probably doing startx and running X11. The simplest solution is for you to edit this file to make the command a comment, : startx, or somehow detect your telnet connection. Telnet doesn't usually set any special environment variables. You could perhaps use the command tty to see that you are on a pseudo-tty instead of a real console. Eg after the SSH= line add:



          case `tty` in
          /dev/pts*) SSH=telnet ;;
          esac


          For a user different to dsl such as root, you need to look in its home directory to see if it is different to /home/dsl, and check out both .profile and .bash_profile. Find the directory with eg:



          awk -F: '$1=="root"print $6' /etc/passwd





          share|improve this answer






















          • Well running "sudo startx" in the command line reproduces the error in server! For editing the /home/dsl/.bash_profile (which was a bit different) I added the lines you suggested for detecting the telnet connection and it worked! Now rebooting starts the GUI, while telneting does not. Thanks for searching this. Did now know .bash_profile runs at login.
            – thanopi57
            Oct 16 '17 at 12:44











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f398380%2fdamn-small-linux-telnet-server-freezes%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote



          accepted










          According to this wiki page about /home/dsl/.bash_profile, the default contents of this file check if you are logging in from ssh, and if not it uses the command startx to start the X11 graphics server:



          #!/bin/bash
          export IRCNICK=DSL
          SSH=`env | grep SSH_CONNECTION`
          RUNLEVEL=`runlevel|cut -f2 -d' '`
          if [ -z "$SSH" ]; then
          if [ $RUNLEVEL -eq 5 ]; then
          startx
          fi
          fi


          So when you login from telnet, ssh is not detected, and you are probably doing startx and running X11. The simplest solution is for you to edit this file to make the command a comment, : startx, or somehow detect your telnet connection. Telnet doesn't usually set any special environment variables. You could perhaps use the command tty to see that you are on a pseudo-tty instead of a real console. Eg after the SSH= line add:



          case `tty` in
          /dev/pts*) SSH=telnet ;;
          esac


          For a user different to dsl such as root, you need to look in its home directory to see if it is different to /home/dsl, and check out both .profile and .bash_profile. Find the directory with eg:



          awk -F: '$1=="root"print $6' /etc/passwd





          share|improve this answer






















          • Well running "sudo startx" in the command line reproduces the error in server! For editing the /home/dsl/.bash_profile (which was a bit different) I added the lines you suggested for detecting the telnet connection and it worked! Now rebooting starts the GUI, while telneting does not. Thanks for searching this. Did now know .bash_profile runs at login.
            – thanopi57
            Oct 16 '17 at 12:44















          up vote
          1
          down vote



          accepted










          According to this wiki page about /home/dsl/.bash_profile, the default contents of this file check if you are logging in from ssh, and if not it uses the command startx to start the X11 graphics server:



          #!/bin/bash
          export IRCNICK=DSL
          SSH=`env | grep SSH_CONNECTION`
          RUNLEVEL=`runlevel|cut -f2 -d' '`
          if [ -z "$SSH" ]; then
          if [ $RUNLEVEL -eq 5 ]; then
          startx
          fi
          fi


          So when you login from telnet, ssh is not detected, and you are probably doing startx and running X11. The simplest solution is for you to edit this file to make the command a comment, : startx, or somehow detect your telnet connection. Telnet doesn't usually set any special environment variables. You could perhaps use the command tty to see that you are on a pseudo-tty instead of a real console. Eg after the SSH= line add:



          case `tty` in
          /dev/pts*) SSH=telnet ;;
          esac


          For a user different to dsl such as root, you need to look in its home directory to see if it is different to /home/dsl, and check out both .profile and .bash_profile. Find the directory with eg:



          awk -F: '$1=="root"print $6' /etc/passwd





          share|improve this answer






















          • Well running "sudo startx" in the command line reproduces the error in server! For editing the /home/dsl/.bash_profile (which was a bit different) I added the lines you suggested for detecting the telnet connection and it worked! Now rebooting starts the GUI, while telneting does not. Thanks for searching this. Did now know .bash_profile runs at login.
            – thanopi57
            Oct 16 '17 at 12:44













          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          According to this wiki page about /home/dsl/.bash_profile, the default contents of this file check if you are logging in from ssh, and if not it uses the command startx to start the X11 graphics server:



          #!/bin/bash
          export IRCNICK=DSL
          SSH=`env | grep SSH_CONNECTION`
          RUNLEVEL=`runlevel|cut -f2 -d' '`
          if [ -z "$SSH" ]; then
          if [ $RUNLEVEL -eq 5 ]; then
          startx
          fi
          fi


          So when you login from telnet, ssh is not detected, and you are probably doing startx and running X11. The simplest solution is for you to edit this file to make the command a comment, : startx, or somehow detect your telnet connection. Telnet doesn't usually set any special environment variables. You could perhaps use the command tty to see that you are on a pseudo-tty instead of a real console. Eg after the SSH= line add:



          case `tty` in
          /dev/pts*) SSH=telnet ;;
          esac


          For a user different to dsl such as root, you need to look in its home directory to see if it is different to /home/dsl, and check out both .profile and .bash_profile. Find the directory with eg:



          awk -F: '$1=="root"print $6' /etc/passwd





          share|improve this answer














          According to this wiki page about /home/dsl/.bash_profile, the default contents of this file check if you are logging in from ssh, and if not it uses the command startx to start the X11 graphics server:



          #!/bin/bash
          export IRCNICK=DSL
          SSH=`env | grep SSH_CONNECTION`
          RUNLEVEL=`runlevel|cut -f2 -d' '`
          if [ -z "$SSH" ]; then
          if [ $RUNLEVEL -eq 5 ]; then
          startx
          fi
          fi


          So when you login from telnet, ssh is not detected, and you are probably doing startx and running X11. The simplest solution is for you to edit this file to make the command a comment, : startx, or somehow detect your telnet connection. Telnet doesn't usually set any special environment variables. You could perhaps use the command tty to see that you are on a pseudo-tty instead of a real console. Eg after the SSH= line add:



          case `tty` in
          /dev/pts*) SSH=telnet ;;
          esac


          For a user different to dsl such as root, you need to look in its home directory to see if it is different to /home/dsl, and check out both .profile and .bash_profile. Find the directory with eg:



          awk -F: '$1=="root"print $6' /etc/passwd






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 16 '17 at 14:41

























          answered Oct 16 '17 at 12:22









          meuh

          29.8k11751




          29.8k11751











          • Well running "sudo startx" in the command line reproduces the error in server! For editing the /home/dsl/.bash_profile (which was a bit different) I added the lines you suggested for detecting the telnet connection and it worked! Now rebooting starts the GUI, while telneting does not. Thanks for searching this. Did now know .bash_profile runs at login.
            – thanopi57
            Oct 16 '17 at 12:44

















          • Well running "sudo startx" in the command line reproduces the error in server! For editing the /home/dsl/.bash_profile (which was a bit different) I added the lines you suggested for detecting the telnet connection and it worked! Now rebooting starts the GUI, while telneting does not. Thanks for searching this. Did now know .bash_profile runs at login.
            – thanopi57
            Oct 16 '17 at 12:44
















          Well running "sudo startx" in the command line reproduces the error in server! For editing the /home/dsl/.bash_profile (which was a bit different) I added the lines you suggested for detecting the telnet connection and it worked! Now rebooting starts the GUI, while telneting does not. Thanks for searching this. Did now know .bash_profile runs at login.
          – thanopi57
          Oct 16 '17 at 12:44





          Well running "sudo startx" in the command line reproduces the error in server! For editing the /home/dsl/.bash_profile (which was a bit different) I added the lines you suggested for detecting the telnet connection and it worked! Now rebooting starts the GUI, while telneting does not. Thanks for searching this. Did now know .bash_profile runs at login.
          – thanopi57
          Oct 16 '17 at 12:44


















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f398380%2fdamn-small-linux-telnet-server-freezes%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?