-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/11 23:07, Cleaver, Japheth wrote:
On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote:
- change systems logs owners from root:root mode 600 to root:adm mode
640 (or something similar)
snip
One benefit of setgid over simply
On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote:
- change systems logs owners from root:root mode 600 to root:adm mode
640 (or something similar)
So, what would be the implementation of this? How would logcheck or any log
reader
work. Would they be setgid applications or
On Sun, 2011-02-27 at 23:20 +0100, Till Maas wrote:
On Sun, Feb 27, 2011 at 12:30:43PM -0700, Kevin Fenzi wrote:
Were you thinking of just /var/log/messages? or all log files?
Or all syslog written files? or ?
If you are talking all log files, I would suggest making this into a
On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote:
- change systems logs owners from root:root mode 600 to root:adm mode
640 (or something similar)
So, what would be the implementation of this? How would logcheck or any log
reader
work. Would they be setgid applications or would
On Mon, Feb 28, 2011 at 11:46:13AM -0500, Steve Grubb wrote:
On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote:
- change systems logs owners from root:root mode 600 to root:adm mode
640 (or something similar)
So, what would be the implementation of this? How would logcheck or
On Mon, Feb 28, 2011 at 08:26:05PM +1030, Glen Turner wrote:
On Sun, 2011-02-27 at 23:20 +0100, Till Maas wrote:
On Sun, Feb 27, 2011 at 12:30:43PM -0700, Kevin Fenzi wrote:
Were you thinking of just /var/log/messages? or all log files?
Or all syslog written files? or ?
If you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/11 17:46, Steve Grubb wrote:
On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote:
- change systems logs owners from root:root mode 600 to root:adm mode
640 (or something similar)
So, what would be the implementation of this?
On Sat, 26 Feb 2011 10:44:05 +0100
Matthias Runge mru...@matthias-runge.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/11 17:21, Till Maas wrote:
...snip...
I like a special group just for accounts that should be able to
read all log files, too, e.g. a group logread.
On Sun, Feb 27, 2011 at 12:30:43PM -0700, Kevin Fenzi wrote:
Were you thinking of just /var/log/messages? or all log files?
Or all syslog written files? or ?
If you are talking all log files, I would suggest making this into a
feature for f16, since it's going to require coordinating a
Dne 25.2.2011 09:13, Matthias Runge napsal(a):
What do you think? Did I miss something? Has anybody of you another hint?
No detailed analysis, but just brief +1 (unless some terrible issue is
discovered in further discussion) ... I really liked this on Debian.
Matěj
--
devel mailing list
On 02/25/2011 09:13 AM, Matthias Runge wrote:
yum provides */messages did not list it. Is it really unowned?
In order to give Big Brother read access to /var/log/messages I have
added:
create 640 root wheel
to /etc/logrotate.d/syslog and have added bbuser to the wheel group.
That file is
Dne 25.2.2011 10:39, Mogens Kjaer napsal(a):
create 640 root wheel
to /etc/logrotate.d/syslog and have added bbuser to the wheel group.
That file is owned by rsyslog in Fedora and sysklogd in RHEL.
I am not sure whether wheel is the correct group ... I don't think we
should mix together
On Fri, Feb 25, 2011 at 03:50:57PM +0100, Matej Cepl wrote:
Dne 25.2.2011 10:39, Mogens Kjaer napsal(a):
create 640 root wheel
to /etc/logrotate.d/syslog and have added bbuser to the wheel group.
That file is owned by rsyslog in Fedora and sysklogd in RHEL.
I am not sure whether
13 matches
Mail list logo
