When SIGUSR2 is sent to DD, the info is split across stderr and world.log, with neither having the full info.
Numbered Steps to Reproduce Problem:
send SIGUSR2 to a running DD instance whose world.log has been redirected from stdout
Code Snippet (if applicable) to Reproduce Problem:
/world/New()
log = file("usr2.txt")
log << "Starting."
Expected Results: One of:
- Full info to either world.log or stderr, with partial info to the other
- Full info to both world.log and stderr
Actual Results:
Partial info to world.log and stderr, each having information the other lacks.
Does the problem occur:
Every time? Or how often? Every time
In other games? N/A
In other user accounts? Unknown
On other computers? Unknown
When does the problem NOT occur? N/A
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? Unknown
Workarounds: redirect stderr to append to world.log's file?
usr2.txt
Starting.
Dream Daemon network diagnostics:
IP Address: 127.0.0.1
Port: 5000
Users:
server mem usage:
Prototypes:
obj: 2140 (16)
mob: 2156 (1)
proc: 7440 (51)
str: 14048 (497)
appearance: 14048 (0)
id array: 7828 (98)
map: 8192 (0,0,0)
objects:
mobs: 0 (0)
objs: 0 (0)
datums: 0 (0)
lists: 48 (2)
stderr
*************************************
Caught SIGUSR2, printing diagnostics:
Server port: 5000
Server visibility: public
Server reachable by players: yes
Backtrace for BYOND 510.1346 on Linux:
Generated at Wed Aug 17 13:47:25 2016
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bb24]
linux-gate.so.1 [0xf771d000, 0xf771dd00], [0xf771d000, 0xf771dd09]
linux-gate.so.1 [0xf771d000, 0xf771dcf0], [0xf771d000, 0xf771dcf0]
linux-gate.so.1 [0xf771d000, 0xf771dd00], [0xf771d000, 0xf771dd09]
libc.so.6 0xe1d90, 0xe1dbd (__select)
libbyond.so 0x2f8600, 0x2f89d5
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ae34]
libc.so.6 0x180a0, 0x18196 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a731]
Recent proc calls:
/world/New
End of diagnostics.
*************************************