Date: Sun, 21 Aug 2011 00:12:28 -0700 From: perryh@pluto.rain.com To: utisoft@gmail.com Cc: freebsd-ports@freebsd.org Subject: Re: sysutils/diskcheckd needs fixing and a maintainer Message-ID: <4e50afdc.xHmlFZrJWhTmnkq/%perryh@pluto.rain.com> In-Reply-To: <CADLo838fUCCr6Vm_D3BW6m6JtLnvDBicGTFp6kx2ZSQd_7dJBA@mail.gmail.com> References: <CADLo83-kEaQyFOiR45WmYdOru8vqu-MhAgb9p=OhjOo-TVUwfQ@mail.gmail.com> <201108171436.p7HEaNYQ071778@fire.js.berklix.net> <20110817161554.GA2496@lonesome.com> <4e4cc750.GqJImeHzdv6k8zld%perryh@pluto.rain.com> <CADLo83-MXGLOQexp9woAeSmKvC8rBobM49pidTBC7-eXTwoCZA@mail.gmail.com> <4E4CBBEE.4040302@FreeBSD.org> <CADLo83-fu_B1S0Lcnypdhy%2BSe-stdmyBFVwHEinmyenBsLOfHQ@mail.gmail.com> <4e4f3c65.SWjpvhhzZjBepdJu%perryh@pluto.rain.com> <CADLo838fUCCr6Vm_D3BW6m6JtLnvDBicGTFp6kx2ZSQd_7dJBA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Rees <utisoft@gmail.com> wrote: > Is it logging to syslog? I haven't seen anything in /var/log/messages or on ttyv0, but this may be a matter of configuration rather than a problem with diskcheckd. * I'm running diskcheckd as a normal user, not as root. (The user is in the operator group and does have read access to the disks. There's no obvious reason to give diskcheckd full root access since it does not need -- and should not be allowed -- to write to the disks.) * diskcheckd passes LOG_CONS|LOG_PID, and LOG_DAEMON, to openlog(3), and -- for the one message that should actually be logged absent failures -- LOG_INFO to syslog(3). * My syslog configuration is whatever 8.1-RELEASE provides as shipped. I have not tried to figure out whether that combination _should_ produce anything in /var/log/messages or on ttyv0. > Also, would you be happy to take maintainership of this port? Not at this point, given that I would be taking on maintainance not only of the "port" but also of the application itself. I'm not at all sure that I understand it well enough for that, yet. (So far I have built it, read _part_ of the code, hacked in some additional debug, and run it :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e50afdc.xHmlFZrJWhTmnkq/%perryh>