Your message dated Thu, 24 Aug 2017 10:03:02 +0200
with message-id
<caoksjbidiow1kgs1ip0mfjm1ez54jpagka_iejpkmko3zk_...@mail.gmail.com>
and subject line Re: Bug#873062: /var/log/ulogd not accesible using sudo
has caused the Debian Bug report #873062,
regarding /var/log/ulogd not accesible using sudo
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
873062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873062
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ulogd2
Version: 2.0.5-5
Severity: normal
Dear Maintainer,
the ulogd2 package creates /var/log/ulogd upon installation for logs to be
there.
Problem is that with the default permissions, this directory is not available
for users using 'sudo', i.e. this is not possible:
% sudo tailf -f /var/log/ulogd/mylog.log
We should change user/group/permissions of this directory to easy system
administration.
Probably simply "chmod -R go+rx" is enough.
I could try to patch this myself.
--- End Message ---
--- Begin Message ---
On 24 August 2017 at 09:59, Chris Boot <[email protected]> wrote:
>
> The directory created by the ulogd2 package in Debian is /var/log/ulog,
> rather than /var/log/ulogd. I will assume this is a typo on your bug
> report rather than you using a different directory.
yes.
>
> The sudo with tail should work just fine, but I assume the issue is you
> can't see within the ulogd directory in order to tab-complete the file
> names. Is my assumption correct?
>
yes :-/
> Either way, my understanding is that the most efficient way to grant
> users read access to log files is by adding them to the 'adm' group. You
> will find the /var/log/ulog directory has 'adm' group ownership and r-x
> group permissions, and files within should also be readable by the adm
> group: the logrotate job rotates *.log and *.pcap in there and creates
> empty files with adm group ownership and read privileges.
>
Great, Chris. Fair enough, you are right :-)
Closing this bug now. Sorry for the noise.
--- End Message ---
