On Sun, 12 Apr 2020 19:39:05 -0500, Serge E. Hallyn wrote: >On Sun, Apr 12, 2020 at 10:48:08AM -0700, Forest wrote: >> On Sun, 12 Apr 2020 10:51:16 -0500, Serge E. Hallyn wrote: >> >> >On Sat, Apr 11, 2020 at 08:09:56PM -0700, Forest wrote: >> >> I am not passing any command line options to lxc-monitor, and its manual >> >> says, "The default is no log." Nevertheless, whenever I run it, >> >> lxc-monitord writes to lxc-monitord.log. >> >> >> >> I have tools that regularly use lxc-monitor, and this log file has been >> >> slowly growing in size for who knows how long. Passing -o /dev/null >> >> doesn't >> >> help. How can I banish this file? >> >> >> >> $ lxc-monitor --version >> >> 3.0.4 >> > >> >Can you show how exactly you start lxc-monitor? Which file exactly >> >is being created, and can you show a few of its lines? >> > >> >-o /dev/null ought to work, but maybe try -l none instead. >> >> Neither of those work. > >Hm, yeah, actually, confirmed on 3.0.3 at least. The code is clearly >trying to not do that. I'll have to play around with it a bit, unless >Christian knows offhand what's going on.
Thanks. I look forward to whatever insight you come up with. _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
