summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Longbons <b.r.longbons@gmail.com>2013-10-16 10:55:09 -0700
committerBen Longbons <b.r.longbons@gmail.com>2013-10-16 10:55:09 -0700
commit5094d0859a7ca4116d59dcfd1dfb606472a69feb (patch)
treeda131dd9af6140a9f69781cc93d40aa3cd533322
parent3fa6f4b4c400c7354e05ac7bae128d4d9ee30e5c (diff)
downloadtmwa-5094d0859a7ca4116d59dcfd1dfb606472a69feb.tar.gz
tmwa-5094d0859a7ca4116d59dcfd1dfb606472a69feb.tar.bz2
tmwa-5094d0859a7ca4116d59dcfd1dfb606472a69feb.tar.xz
tmwa-5094d0859a7ca4116d59dcfd1dfb606472a69feb.zip
Flush GM log after every single freaking log entry
Oh well, I guess it's still slightly better than reopening the file all the time ... There's still a bug in our cron scripts if no one uses a GM command in the first few minutes of a new month.
-rw-r--r--src/map/atcommand.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/map/atcommand.cpp b/src/map/atcommand.cpp
index 508209c..2ed853f 100644
--- a/src/map/atcommand.cpp
+++ b/src/map/atcommand.cpp
@@ -422,6 +422,7 @@ void log_atcommand(dumb_ptr<map_session_data> sd, ZString cmd)
sd->bl_m->name_, sd->bl_x, sd->bl_y,
sd->status.name, sd->status.account_id,
cmd);
+ fflush(fp);
}
FString gm_log;