On Tue, 2013-07-09 at 18:52 +0800, Ed Greshko wrote: > Well, I find one thing interesting..... > > Notice the error message.... > > fail2ban-client[2804]: ERROR Directory /var/run/fail2ban exists but not > accessible for writing > > But, if you execute the command in the service file from the command line.... > > [root@f18x log]# /usr/bin/fail2ban-client -x start > 2013-07-09 18:46:10,558 fail2ban.server : INFO Starting Fail2ban v0.8.10 > 2013-07-09 18:46:10,559 fail2ban.server : INFO Starting in daemon mode > > and.... > > [root@f18x fail2ban]# pwd > /var/run/fail2ban > [root@f18x fail2ban]# ls > fail2ban.pid fail2ban.sock > > And if you put selinux in permissive mode.... > > [root@f18x fail2ban]# pwd > /var/run/fail2ban > [root@f18x fail2ban]# ls > [root@f18x fail2ban]# setenforce 0 > [root@f18x fail2ban]# systemctl start fail2ban > [root@f18x fail2ban]# ls > fail2ban.pid fail2ban.sock > > So it is running with selinux placed in permissive mode..... Yes, you're right. Thank you for the fix. Why selinux is not complaining with an AVC?
C. Sava -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
