I opened https://github.com/Pylons/pyramid/issues/3455 to track this.
On Fri, Jan 25, 2019 at 3:00 PM Michael Merickel wrote:
> The issue is that pserve configures logging *before* forking the children,
> while in the monitor process, and then configures logging again in the
> child
On Fri, 25 Jan 2019 at 21:13, Marcus Mann wrote:
> So what if I moved the logging stuff into the __init__.py and remove all
> the logging stuff from development.ini? Would that solve my issue?
>
Some ideas with lack of better information:
1) Not sure about pserve, but uWSGI had an event it
So what if I moved the logging stuff into the __init__.py and remove all
the logging stuff from development.ini? Would that solve my issue?
On Friday, January 25, 2019 at 4:01:40 PM UTC-5, Michael Merickel wrote:
>
> The issue is that pserve configures logging *before* forking the children,
>
The issue is that pserve configures logging *before* forking the children,
while in the monitor process, and then configures logging again in the
child subprocesses after forking. This is an issue and hasn't been pointed
out by anyone before. This means you always have two processes opening
those
Thanks for the quick reply!
It says on the page:
This handler is not appropriate for use under Windows, because under Windows
open log files cannot be moved or renamed - logging opens the files with
exclusive locks - and so there is no need for such a handler. Furthermore,
*ST_INO* is not
Hi Marcus,
Hello!
> I am trying to setup logging. I have run into a bug. If I
> use RotatingFileHandler and try to start my pyramid setup with pserve
> --reload development.ini, it throws an error similar to this when it tries
> to rotate the file:
>
Maybe this
Hello!
I am trying to setup logging. I have run into a bug. If I
use RotatingFileHandler and try to start my pyramid setup with pserve
--reload development.ini, it throws an error similar to this when it tries
to rotate the file:
PermissionError: [WinError 32] The process cannot access the
