1
2
May 6 2012, 11:03 am
|
|
I connect via BYOND pager.
|
[root@localhost ~]# ps fx
PID TTY STAT TIME COMMAND 1 ? Ss 0:00 init [3] 2 ? S 0:00 [kthreadd/1072] 3 ? S 0:00 \_ [khelper/1072] 99 ? S<s 0:00 /sbin/udevd -d 488 ? Ss 0:00 syslogd -m 0 499 ? Ss 0:00 /usr/sbin/sshd 566 ? Ss 0:00 \_ sshd: root@pts/0 568 pts/0 Ss 0:00 \_ -bash 586 pts/0 R+ 0:00 \_ ps fx 508 ? Ss 0:00 /usr/sbin/httpd 517 ? Ss 0:00 crond 525 ? Ss 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2 526 ? S 0:00 \_ /usr/sbin/saslauthd -m /var/run/saslauthd -a pam [root@localhost ~]# When I tried to connect, it failed. |
Alright, there's your problem. It appears as if Dream Daemon actually isn't running anymore. After you used the DreamDaemon command, it should have hijacked your console. Hitting CTRL + C or exiting would kill the process. To start up a proper DreamDaemon process, use a command similar to the following:
"DreamDaemon game.dmb [port] -trusted -logself &" The ampersand at the end drops the process into the background so that it can continue running. From there, you can use 'exit' to get out of the process without killing Dream Daemon. |
In response to Audeuro
|
|
Off topic:
My comment still got the "Best response" :D |
1
2