Results 1 to 7 of 7

Thread: launch.sh failing. Tekkit server.

  1. #1
    Join Date
    Jan 2013
    Beans
    34

    launch.sh failing. Tekkit server.

    My .sh is set to executable. I double click on the .sh to launch the server and the terminal opens and closes instantly. Am I forgetting something?

  2. #2
    Join Date
    Apr 2008
    Location
    LOCATION=/dev/random
    Beans
    5,767
    Distro
    Ubuntu Development Release

    Re: launch.sh failing. Tekkit server.

    Try launching the sh file from a terminal, it should give some error messages which will help us diagnose the problem.
    Cheesemill

  3. #3
    Join Date
    Jan 2013
    Beans
    34

    Re: launch.sh failing. Tekkit server.

    newb here depending on gui to much

    In terminal, I get to the folder where ther .sh is located. How should I finish out that line in terminal to launch it?

  4. #4
    Join Date
    Apr 2008
    Location
    LOCATION=/dev/random
    Beans
    5,767
    Distro
    Ubuntu Development Release

    Re: launch.sh failing. Tekkit server.

    Once you are in the folder containing the sh file just do...
    Code:
    ./filename.sh
    Cheesemill

  5. #5
    Join Date
    Jan 2013
    Beans
    34

    Re: launch.sh failing. Tekkit server.

    Like this?

    Code:
    /media/zach/6e6209ee-a84e-4ba4-8398-2e4f3be6d421/Tekkit-Server/.launch.sh
    Result:
    Code:
    bash: /media/zach/6e6209ee-a84e-4ba4-8398-2e4f3be6d421/Tekkit-Server/.launch.sh: No such file or directory
    incase I misunderstood I ran it without the .in ./launch.sh, same results. File name is correct.

  6. #6
    Join Date
    Apr 2008
    Location
    LOCATION=/dev/random
    Beans
    5,767
    Distro
    Ubuntu Development Release

    Re: launch.sh failing. Tekkit server.

    Change to the directory first then run the file...
    Code:
    cd /media/zach/6e6209ee-a84e-4ba4-8398-2e4f3be6d421/Tekkit-Server
    ./launch.sh
    Cheesemill

  7. #7
    Join Date
    Jan 2013
    Beans
    34

    Re: launch.sh failing. Tekkit server.

    I figured it out, and I feel so stupid haha. .sh was written tekkit.jar trying to execute Tekkit.jar

    All came down to one letter...Thanks for all the help, I was wracking my head over this for about 3 days.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •