Stoneburner Gaming Facebook Link
Stoneburner Gaming Steam Group Link
Stoneburner Gaming Minecraft Chat Logs
Stoneburner Gaming Minecraft Dynamic Map

More of a Suggestion than a question...
Views 393
Replies 5
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Users browsing this thread: 1 Guest(s)
#1
But would it not be a good idea to install and setup some sort of auto-restarting plugin, even if we just modified the .sh to auto-restart when it stops and get a plugin to stop it every-so-often...

Tekkit seems to hog more and more resources and is more and more likely to die/ cause massive lag/badstuffhappens, after it's been on for a while... but it's almost always fixable with a restart...

So perhaps were we to set it up to auto restart every half a day or so (12 hours) it might start to work better...

[Image: Robereid_zps75b54298.png]
Reply
#2
(13-08-2012, 09:56 AM)roberestarkk Wrote:  But would it not be a good idea to install and setup some sort of auto-restarting plugin, even if we just modified the .sh to auto-restart when it stops and get a plugin to stop it every-so-often...

Tekkit seems to hog more and more resources and is more and more likely to die/ cause massive lag/badstuffhappens, after it's been on for a while... but it's almost always fixable with a restart...

So perhaps were we to set it up to auto restart every half a day or so (12 hours) it might start to work better...
Not a bad idea. Although I say we go down to 6 hours.

We must figure out a way!! Or you can be a super badass genius Rob and show me how :3



[Image: b_560_95_1.png]
Reply
#3
i got a suggestion. stop playing tekkit and get your asses back on smp.

I'm Watching You Grief.....  *BOOOOOM Head Shot*
Reply
#4
(13-08-2012, 12:06 PM)weavybaby Wrote:  i got a suggestion. stop playing tekkit and get your asses back on smp.
NEVAR!

[Image: b_560_95_1.png]
Reply
#5
(13-08-2012, 12:06 PM)weavybaby Wrote:  i got a suggestion. stop playing tekkit and get your asses back on smp.
I second that.

Reply
#6
(13-08-2012, 12:26 PM)DKoda Wrote:  
(13-08-2012, 12:06 PM)weavybaby Wrote:  i got a suggestion. stop playing tekkit and get your asses back on smp.
NEVAR!
well I second THIS!
So THERE!



(13-08-2012, 11:42 AM)DKoda Wrote:  
(13-08-2012, 09:56 AM)roberestarkk Wrote:  But would it not be a good idea to install and setup some sort of auto-restarting plugin, even if we just modified the .sh to auto-restart when it stops and get a plugin to stop it every-so-often...

Tekkit seems to hog more and more resources and is more and more likely to die/ cause massive lag/badstuffhappens, after it's been on for a while... but it's almost always fixable with a restart...

So perhaps were we to set it up to auto restart every half a day or so (12 hours) it might start to work better...
Not a bad idea. Although I say we go down to 6 hours.

We must figure out a way!! Or you can be a super badass genius Rob and show me how :3
Download:
http://dev.bukkit.org/media/files/583/562/SimpleRestart.jar


Source:
http://dev.bukkit.org/server-mods/simple_restart/


Setting Up

Simply copy SimpleRestart.jar and the SimpleRestart folder into the "plugins" subdirectory
of your minecraft server. If you do not copy in the SimpleRestart folder, it will be created
for you automatically, along with a default configuration file. Edit the configuration file
(config.yml) as you see fit, then modify your server startup script so that it automatically
reboots the server when it gets "/stop"ped.



The Configuration File

  • auto-restart: enable / disable automatic,
    time-scheduled restarting. If this is set to "no" then the server will
    only ever restart when using the "/restart" command.
  • auto-restart-interval: this is how often (in hours) the server will automatically restart itself (only if auto-restart is set to "yes")
  • warn-times: Before the server restarts, it
    will send out a friendly warning to all connected players, this setting
    is a list that describes the amount of time (in minutes) before the
    server automatically reboots that players are warning. For example:
    warn-times: [10, 5, 2, 1] will warn players at 10 minutes, 5 minutes, 2
    minutes, and 1 minute before the server reboots.
  • warning-message: this is the message that will
    be displayed as a warning that the server will be restarting soon. You
    may use classic minecraft server colour codes (http://www.minecraftwiki.net/wiki/Classic_server_protocol#Color_Codes) and "%t"% to indicate how long before the server reboots. For example: warning-message: "&cServer will be restarting in %t minutes!" will display "Server will be restarting in 5 minutes!" in red (with warn-time = 5)
  • restart-message: this is the message that
    players will see when they are kicked from the server due to the
    automatic reboot. Again, color codes can be used here.


Editing Your Startup Script
(Here you would use 'nano launch.sh' and replace everything inside with what is here, I've already edited it to contain the Tekkit-spcific line, so it's just a straight c/p.)
Example:

#!/bin/sh
BINDIR=$(dirname "$(readlink -fn "$0")")
cd "\$BINDIR"
while true
do
java -Xmx3G -Xms2G -jar Tekkit.jar nogui
echo "If you want to completely stop the server process now, press Ctrl+C before the time is up!"
echo "Rebooting in:"
for i in 5 4 3 2 1
do
echo "$i..."
sleep 1
done
echo "Rebooting now!"
done

Misc Info:

Permissions Nodes

The following permissions can be configured:
  • simplerestart.restart to use just about anything in the /restart or /reboot commands, users must have the permission
  • simplerestart.time to use the /restart time command, users must have the permission
  • simplerestart.memory to use the /memory command, users must have the permission
  • Note: simplerestart.* shouldn't work
Commands

All commands may be typed in the console (without the "/" of course) or by players in-game:
  • /restart help: gives a simple help menu
  • /restart now: restarts the server immediately
  • /restart time: informs you how much time is left before the server restarts
  • /restart (h|m|s) <time>: turns automatic restarting on (if it was off) and reschedules the next
    automatic restart to be <time> (hours, minutes, or seconds) away from now. For example,
    to reboot the server in 15 minutes, use "/restart m 15". 'h' is for hours, 'm' is for minutes,
    and 's' is for seconds.
  • /restart on: turns automatic restarting on (if disabled in configuration OR via
    commands. Will start the scheduler from the current time based on the settings
    in the configuration.
  • /restart off: cancels any pending automatic restarts and prevents automatic restarts
    from happening until re-enabled
  • /memory: displays the java runtime memory usage, useful for catching runaway plugins



[Image: Robereid_zps75b54298.png]
Reply


Forum Jump: