[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-04-03 Thread Marko Lindqvist
Update of bug #21540 (project freeciv): Status: Ready For Test => Fixed Assigned to:None => cazfi Open/Closed:Open => Closed

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-03-31 Thread Marko Lindqvist
Follow-up Comment #10, bug #21540 (project freeciv): S2_6 and TRUNK versions that also pass LOG_DEBUG level without modifications. S2_5 version kept in the form that does not allow levels above LOG_VERBOSE to be passed. This is not a regression as old code hard-coded LOG_VERBOSE. On the

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-03-03 Thread Christian Knoke
Follow-up Comment #9, bug #21540 (project freeciv): My point is, if you limit the server logging to level 3 at max, you won't be able to debug the code for spawning the server from the client. Might be a special case, but we have had it already. Christian

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-03-02 Thread Marko Lindqvist
Follow-up Comment #8, bug #21540 (project freeciv): Besides, I'm not sure logging to the same file from both server and client is a good idea, and less likely so if they produce a lot of log. Within one program we have protection against multiple threads causing trouble to each others output, but

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-03-01 Thread Christian Knoke
Follow-up Comment #7, bug #21540 (project freeciv): Hhm. I think most debugging on level 4 is done separately anyway. That server and client been started separatly. Christian ___ Reply to this item at:

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-03-01 Thread Marko Lindqvist
Follow-up Comment #6, bug #21540 (project freeciv): > Why that? You need this patch esp. to debug start up local in > one games. Usually LOG_DEBUG is associated with further definitions where from the debug logs are enabled so that it doesn't produce enormous amounts of logs. "-d

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-03-01 Thread Christian Knoke
Follow-up Comment #5, bug #21540 (project freeciv): > in which case one level lower is used Why that? You need this patch esp. to debug start up local in one games. Christian ___ Reply to this item at:

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-02-29 Thread Marko Lindqvist
Follow-up Comment #4, bug #21540 (project freeciv): TRUNK version that passes log levels by their name (file #26898) ___ Additional Item Attachment: File name: LoglevelParamForkedServer.patch Size:6 KB

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2016-02-29 Thread Marko Lindqvist
Update of bug #21540 (project freeciv): Category: client-gtk-2.0 => client Status:None => Ready For Test Planned Release: => 2.5.4, 2.6.0, 3.0.0

[Freeciv-Dev] [bug #21540] Client-spawned server always logs at verbose level (level 3) regardless of client log level

2014-02-19 Thread Jacob Nevins
Update of bug #21540 (project freeciv): Summary: debug options do not work as expected = Client-spawned server always logs at verbose level (level 3) regardless of client log level ___ Reply to this item at: