[ruby-core:100074] [Ruby master Bug#12468] Logger: Can not rotate (log shifting failed. closed stream)

[ruby-core:100074] [Ruby master Bug#12468] Logger: Can not rotate (log shifting failed. closed stream)

[merch-redmine]

Issue #12468 has been updated by jeremyevans0 (Jeremy Evans).


I can't test cygwin, but I've added a pull request to logger that should fix this by treating cygwin like mswin and mingw in regards to log shifting: https://github.com/ruby/logger/pull/50

----------------------------------------
Bug #12468: Logger: Can not rotate (log shifting failed. closed stream)
https://bugs.ruby-lang.org/issues/12468#change-87626

* Author: rovf (Ronald Fischer)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.2.4p230 (2015-12-16 revision 53155) [x86_64-cygwin]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
If I configure a Logger to rotate, by the time the logger is supposed to do the first rotation, it creates the new log file, but then hangs. When I abort the program using Control-C, I get an infinite series of error messages saying

    log shifting failed. closed stream

You can reproduce the error, if you run the attached example program on **Windows** (it could be a platform issue). The only prerequisite is that a subdirectory 'logs' must exist below the working directory.

I'm reporting error for the Cygwin version of Ruby. However, I found the nearly identical error also with JRuby 1.9.3, which suggests that the bug is likely in the Ruby stdlib code, and not in the specific port (i.e. Cygwin vs. JRuby). The main difference between the behaviour of the bug in Cygwin Ruby vs. JRuby is that aborting the program on JRuby does not produced the "log shifting...." error message.

---Files--------------------------------
logtest_s.rb (481 Bytes)


-- 
https://bugs.ruby-lang.org/