Monique Y. Herman wrote:
> Is this really a bug, or just a bad/pointless idea? I mean, it asked me
> if I should lock these tools down, and I said yes. I can always loosen
> up permissions on a case by case basis.
Unless bastille closes down access to programs like perl, python, gcc,
the shell,
On 2004-02-15, Colin Watson penned:
> On Sun, Feb 15, 2004 at 12:20:26PM -0700, Monique Y. Herman wrote:
>> On 2004-02-15, Joey Hess penned:
>> > That would be a violation of debian policy, and is not the case on
>> > any of my systems.
>> >
>> > -rwxr-xr-x1 root root 33K Oct 9 2
On Sun, 2004-02-15 at 11:16, Monique Y. Herman wrote:
> Hi all! I've looked in the logrotate man page, /usr/share/doc/logrotate
> (not much there), and google, and I can't seem to find the answer to
> these questions:
>
> 1) I'd like to have the option of never deleting the backups for certain
>
On Sun, Feb 15, 2004 at 12:20:26PM -0700, Monique Y. Herman wrote:
> On 2004-02-15, Joey Hess penned:
> > That would be a violation of debian policy, and is not the case on any
> > of my systems.
> >
> > -rwxr-xr-x1 root root 33K Oct 9 2002
> > /usr/sbin/logrotate*
>
> Well, Bas
On 2004-02-15, Joey Hess penned:
>
> Monique Y. Herman wrote:
>> 3) Permissions. The logrotate app is only executable by root on my
>> box. I'm trying to imagine the situation in which giving a normal
>> user access to logrotate would hurt anything, as long as logs have
>> appropriate permissions
Monique Y. Herman wrote:
> 3) Permissions. The logrotate app is only executable by root on my box.
> I'm trying to imagine the situation in which giving a normal user access
> to logrotate would hurt anything, as long as logs have appropriate
> permissions. Could the paranoid among us speak up an
6 matches
Mail list logo
