From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Guardian 2 - Correction
Date: Sat, 16 Jul 2016 22:10:59 +0200 [thread overview]
Message-ID: <851b9292-33a9-7514-99c3-1cfc6616a447@ipfire.org> (raw)
In-Reply-To: <578A8C3E.6050408@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
Hi,
On 16.07.2016 21:34, R. W. Rodolico wrote:
>> As Matthias says, it is a permissions issue on the configuration file
>> directory. Either manually create the files (with correct ownership and
>> permission) or change ownership/permission on the directory.
Actually, these directories and files are effected:
...
[root(a)ipfiretest guardian-2.0-002_expanded]# find -user samba -group samba
./opt/pakfire/db/installed/meta-guardian
./etc/rc.d/rc6.d
./etc/rc.d/rc0.d
./etc/rc.d/init.d/networking/red.up/35-guardian
./etc/rc.d/init.d/snort
./etc/rc.d/init.d/guardian
./etc/rc.d/rc3.d
./etc/logrotate.d
./etc/logrotate.d/guardian
./var/ipfire/menu.d
./var/ipfire/menu.d/EX-guardian.menu
./var/ipfire/backup/addons/includes
./var/ipfire/backup/addons/includes/guardian
./var/ipfire/langs/en.pl
./var/ipfire/langs/de.pl
./var/ipfire/guardian
./var/log/guardian/guardian.log
./usr/sbin/guardian
./usr/lib/perl5/site_perl/5.12.3/Net/IP.pm
./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto
./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto/Linux/Inotify2/Inotify2.so
./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/Linux
./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/Linux/Inotify2.pm
./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common
./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common/sense.pod
./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common/sense.pm
./usr/bin
./usr/bin/guardianctrl
./srv/web/ipfire
./srv/web/ipfire/cgi-bin/guardian.cgi
./srv/web/ipfire/cgi-bin/ids.cgi
...
Best,
Matthias
next prev parent reply other threads:[~2016-07-16 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACOO0z-ZmvxauaLjrv5nLX_kctaPcbMB1nGNZy02iT=E5FDNEA@mail.gmail.com>
2016-07-16 15:12 ` Guardian 2 Matthias Fischer
2016-07-16 18:43 ` R. W. Rodolico
2016-07-16 19:34 ` Guardian 2 - Correction R. W. Rodolico
2016-07-16 20:10 ` Matthias Fischer [this message]
2016-07-16 22:26 ` R. W. Rodolico
2016-07-16 23:19 ` R. W. Rodolico
2016-07-18 14:03 ` Stefan Schantl
[not found] <CACOO0z_XpLEKp3E7M1n6t6cgmVmDNO7OGzUaVN-pr9b7rOwWaQ@mail.gmail.com>
2016-07-17 0:56 ` R. W. Rodolico
2016-07-17 5:43 ` Matthias Fischer
[not found] <CACOO0z_2rhPGhW_rCe46VMCgWTT_4jLxMwSJZoAheY5ouiNt=g@mail.gmail.com>
2016-07-17 13:57 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=851b9292-33a9-7514-99c3-1cfc6616a447@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox