ID:1113532
 Jan 5 2013, 7:17 am
|
|
When you start a process with & at the end, it allows you to do other things and leave that process. But what do you do to enter back into the process (DreamDaemon) to see its log again?
| |
|
Jan 5 2013, 8:46 am
|
|
Stephen001
  |
fg [process id]. Alternatively, redirect the log when you start the process with '2>&1 > [some file]'. This redirects standard error and output streams to that file, which you can look at, tail -f on to watch it as it's printing out etc.
|
I am a newbie with linux, could you [tt] the commands so I can see when they end? ;D
| |
Sure.
fg [process id] For bringing a background process forward. DreamDaemon [DMB] [port] 2>&1 > [some file] & Launch a process in the background with standard error and standard output directed to some file. | |
You can also use -logself or -log with DreamDaemon to spit the output to the log.
| |
tail -f [somefile]
| |
Looks like you can also go:
fg DreamDaemon Which is a little more user friendly. I'm on ubuntu. | |
I assume as it's matching the binary name. Wouldn't work if you had multiple worlds, but I guess you don't.
| |
Ok how can I go back to > after a process is raised to foreground
I am afraid to end or pause the process. | |
Ctrl + Z. Then do:
bg To background the printed output also. | |
Stephen001 wrote:
Ctrl + Z. Then do: Cool, thanks. Is it bad to nice DreamDaemon at -20? | |
Probably, you don't really want DreamDaemon outstripping realtime or system processes. Typically I'd leave it at 0, and adjust down specific things you know to be CPU intensively at times, that are not important to your server.
| |
I had a high priority because I'm noticing lag spikes when awstats runs (it also hosts a web server). So instead of fighting for performance I'm going to move the game to a new machine / instance.
| |