Jump to content

Archived

This topic is now archived and is closed to further replies.

026jan

wie steuere ich einen Linux BF1942 ?

Recommended Posts

Posted

hallo

wie kann ich einen Linux BF1942 Dedicated Server mit dem Remote Manager fernsteuern??

Posted

Etwas mehr Details bitte ;)

Welchen Remote Manager meinst Du ? Den 1.4er, der nur remote arbeitet oder den 2.0, der auch eine Serverkomponente hat ?

Guest
Posted

Hi!

Wie old-pitcher es schon geschrieben hat solltest Du genau schreiben was Du machen willst.

Du kannst entweder z.B. HLSW von http://www.hlsw.org oder den BFSM 2.0 benutzen.

Ein Handbuch für die Benutzung des BFSM 2.0 findest Du hier:

http://www.blackbagops.com/files/bfsm20ug.pdf

Und hier findest Du noch ein paar weitere Infos zum BFSM:

http://www.blackbagops.com/bf1942/bfsm/index.shtml

@old-pitcher

So wie es aussieht wird der 1.4er nicht mehr auf www.blackbagops.com zum Download angeboten.

Posted

@fisch:

kann es sein dass du ein profi in sachen server bist?

zu jeder frage gleich ne antwort

Posted

wie starte ich denn den BFSM 2.0 unter Linux ???

Guest
Posted

Hi!

@fisch:

kann es sein dass du ein profi in sachen server bist?

zu jeder frage gleich ne antwort

Posted

na also doch

gut dass es hier einen gibt dem sowas freude macht

du hilfst ziehmlich vielen muss ich sagen

thx

Posted

zum starten habe ich mir ein kleines rc-script gebastelt. dieses liegt unter /etc/init.d/bfdc und wird per chkconfig -a bfdc automatisch in die Runlevel eingetragen.

der elementare Befehl ist (eine Zeile !)

startproc -u bfserver /home/bfserver/bf1942/bfsmd -path /home/bfserver/bf1942 -daemon -restart -start -port 14667 -pid /tmp/bfdc.pid +StatusMonitor 0
damit wird der bfsmd als Daemon unter dem Userkontext bfserver aus dessen Homeverzeichnis gestartet.
#! /bin/sh

### BEGIN INIT INFO

# Provides:          bfdc

# Required-Start:    $syslog $remote_fs

# X-UnitedLinux-Should-Start: $time ypbind sendmail

# Required-Stop:     $syslog $remote_fs

# X-UnitedLinux-Should-Stop: $time ypbind sendmail

# Default-Start:     3 5

# Default-Stop:      0 1 2 6

# Short-Description: FOO XYZ daemon providing ZYX

# Description:       Start FOO to allow XY and provide YZ

#       continued on second line by '#<TAB>'

#       should contain enough info for the runlevel editor

#       to give admin some idea what this service does and

#       what it's needed for ...

#       (The Short-Description should already be a good hint.)

### END INIT INFO

BFSERVER_BIN=/home/bfserver/bf1942/bfsmd

test -x $BFSERVER_BIN || exit 5

. /etc/rc.status

rc_reset

case "$1" in

    start)

        echo -n "Starting BFSERVER "

        ## Start daemon with startproc(8). If this fails

        ## the return value is set appropriately by startproc.

        startproc -u bfserver /home/bfserver/bf1942/bfsmd -path /home/bfserver/bf1942 -daemon -restart -start -port 14667 -pid /tmp/bfdc.pid +StatusMonitor 0

        # Remember status and be verbose

        rc_status -v

       ;;

    stop)

        echo -n "Shutting down BFSERVER "

        ## Stop daemon with killproc(8) and if this fails

        ## killproc sets the return value according to LSB.

        kill -9 $(cat /tmp/bfdc.pid)

        # Remember status and be verbose

        rc_status -v

       ;;

    try-restart)

        ## Do a restart only if the service was active before.

        ## Note: try-restart is not (yet) part of LSB (as of 1.2)

        $0 status >/dev/null &&  $0 restart

        # Remember status and be quiet

        rc_status

       ;;

    restart)

        ## Stop the service and regardless of whether it was

        ## running or not, start it again.

        $0 stop

        $0 start

        # Remember status and be quiet

        rc_status

       ;;

    force-reload)

        ## Signal the daemon to reload its config. Most daemons

        ## do this on signal 1 (SIGHUP).

        ## If it does not support it, restart.

        echo -n "Reload service BFSERVER "

        ## if it supports it:

        #killproc -HUP $BFSERVER_BIN

        #touch /var/run/BFSERVER.pid

        #rc_status -v

        ## Otherwise:

        $0 stop  &&  $0 start

        rc_status

       ;;

    reload)

        ## Like force-reload, but if daemon does not support

        ## signaling, do nothing (!)

        # If it supports signaling:

        echo -n "Reload service BFSERVER "

        #killproc -HUP $BFSERVER_BIN

        #touch /var/run/BFSERVER.pid

        #rc_status -v



        ## Otherwise if it does not support reload:

        rc_failed 3

        rc_status -v

       ;;

    status)

        echo -n "Checking for service BFSERVER "

        ## Check status with checkproc(8), if process is running

        ## checkproc will return with exit status 0.

        # Return value is slightly different for the status command:

        # 0 - service up and running

        # 1 - service dead, but /var/run/  pid  file exists

        # 2 - service dead, but /var/lock/ lock file exists

        # 3 - service not running (unused)

        # 4 - service status unknown :-(

        # 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)



        # NOTE: checkproc returns LSB compliant status values.

        checkproc $BFSERVER_BIN

        # NOTE: rc_status knows that we called this init script with

        # "status" option and adapts its messages accordingly.

        rc_status -v

       ;;

    probe)

        ## Optional: Probe for the necessity of a reload, print out the

        ## argument to this init script which is required for a reload.

        ## Note: probe is not (yet) part of LSB (as of 1.2)

        #test /etc/BFSERVER/BFSERVER.conf -nt /var/run/BFSERVER.pid && echo reload

       ;;

    *)

        echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}"

        exit 1

       ;;

esac

rc_exit



  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.