On Mon, 2006-11-20 at 08:42 -0500, Gene Heskett wrote: > On Monday 20 November 2006 08:31, Gene Heskett wrote: > >On Monday 20 November 2006 08:09, Anne Wilson wrote: > >>On Monday 20 November 2006 12:46, Gene Heskett wrote: > >>> Now if logrotate would work... Its not. See my other post. > >> > >>Well, for all the logs that I would expect to rotate, I have files > >> dated 5.11.06, 12.11.06, 19.11.06 and 20.11.06. > >> > >>Yet another peculiarity of your install, Gene. > >> > >>Anne > > > >I *may* be on the track of it, following Ricks advice I ran it from a > >shell, and discovered the whole thing died on not finding a user > > 'named', and I do not have bind installed. So I'll do that but set the > > service to off. nscd is running and thats should be enough. > > > >As to this being a bugzilla-able item, dunno. It seems to me that it > >should be bind that installs this particular script, not logrotate's > > rpm. > > > >After installing bind, the user named is in the passwd file, and it > > runs. This to me is a bugzilla-able packaging problem. > > And, now there are apparently more packageing errors. Installing bind did > not create a default /var/named/chroot//etc/named.conf, and an attempt to > start it seems to have locked up the services editor. Ahh, the 'revert' > button rescusitates the editor again so I can quit normally. > > And yes, the doubled // above is a direct paste from the services error > window. > > Where do I take this next? ---- I think that you are way ahead of yourself but bind-chroot is a separate package yum install bind-chroot Craig
