Open GoogleCodeExporter opened 8 years ago
Thanks for yours answers (in private)
Original comment by julien....@gmail.com
on 2 Dec 2009 at 5:09
Hello.
We are using glog too and facing the same problem.
Is there already any solution?
Any advice will be helpful.
Thank you.
Ivan
Original comment by I.Dun...@gmail.com
on 30 Aug 2010 at 8:14
I'm attaching a patch I made to add a RotateLogFiles() API to glog. I use this
with a SIGHUP handler and an external program like logrotate to handle rotating
log files. It would certainly be nice though if glog was as flexible as
log4j/log4cxx in this respect.
I miss the log4cxx feature to set a max log file size before rotation, and a
max number of log files to keep around. This way I can have a rough
approximation of how much disk space will be dedicated to logging and it is
bounded.
Original comment by toffale...@gmail.com
on 10 Sep 2010 at 1:38
Attachments:
export GLOG_max_log_size=100
This environment variable will keep the maximum log size to 100MB.
export GLOG_stop_logging_if_full_disk=1
This environment variable will stop logging if the disk is full.
Original comment by slateef...@gmail.com
on 10 Nov 2010 at 7:51
Those environment variables are not the same as rolling logs with a max size.
Original comment by toffale...@gmail.com
on 13 Dec 2010 at 8:38
Any progress on this issue?
+1 for adding RotateLogFiles() API to be used in conjunction with SIGHUP, as
proposed in #3.
Original comment by maehashi
on 18 Mar 2014 at 6:18
It's been more than a year since the last comment on this issue/request. Has
there been any further updates to this issue? glog would be a more complete
logging solution if it had support for Log Rotation. It is unwise for a log to
use up all available disk space (unless that's that the user wants). Ensuring
that we can estimate (if not fix) the total size limit of glog creates a better
solution for all it's users.
Original comment by meonyg
on 20 May 2015 at 7:23
Original issue reported on code.google.com by
julien....@gmail.com
on 20 Nov 2009 at 9:22