/etc/default in Fedora
Daniel J Walsh
dwalsh at redhat.com
Mon Mar 19 14:27:46 UTC 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/19/2012 10:16 AM, Michał Piotrowski wrote:
> W dniu 19 marca 2012 15:13 użytkownik Michał Piotrowski
> <mkkp4x4 at gmail.com> napisał:
>> 2012/3/19 Daniel J Walsh <dwalsh at redhat.com>:
> On 03/17/2012 11:25 PM, Dave Quigley wrote:
>>>>> On 3/17/2012 7:17 AM, Daniel J Walsh wrote: On 03/17/2012
>>>>> 05:38 AM, Matej Cepl wrote:
>>>>>>>> On 17.3.2012 10:18, Daniel J Walsh wrote:
>>>>>>>>> Here is the current httpd man page.
>>>>>>>>>
>>>>>>>>> http://people.fedoraproject.org/~dwalsh/SELinux/httpd_selinux.html
>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>
>>>>>>>>>
OK, in the end it IS a wiki ...
>>>>>>>> http://wiki.apache.org/httpd/DistrosDefaultLayout?action=diff&rev1=46&rev2=47
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>
>>>>>>>>
Suggestions for further edits are welcome.
>>>>>>>>
>>>>>>>> Matěj
>>>>>>>>
>>>>> I would also suggest they use setroubleshoot.
>>>>>
>>>>> Suggesting setroubleshoot is fine but you need to also tell
>>>>> them how to set it up when they are running without X. One
>>>>> guy told me that setroubleshoot is fine and all but all his
>>>>> machines are headless so he doesn't have X and the nice
>>>>> little applet to notify him. I had to correct him and send
>>>>> him a reference to your page on how to set up
>>>>> setroubleshoot on headless machines so that the messages
>>>>> are sent to another box or to an email account.
>>>>>
>>>>> Dave
>
>
> Which brings up an interesting idea, I have been having, is there
> a better way of getting the setroubleshoot data from one machine
> to another. Originally setroubleshoot was designed to be able to
> push analysys upstream but we never turned it on. Now that we
> have simplified the XML output, we could look at allowing it to
> some how centralize its analysys, using a protocol more robust then
> email If anyone has a good idea of how or where we should do this,
> I am all ears.
>>>
>>> Is it possible to split setroubleshoot into two components: -
>>> gui - daemon that creates logs ?
>
>> I really did not use setroubleshoot for a few years - because I
>> don't use X, so please forgive my ignorance if it's already
>> splited :)
>
setroubleshoot-server is the server componant. (dbus service)
setroubleshoot is the client componant.
We could put the info into systemd-journal.
>>>
>>> Logs can be stored in systemd-journal format. systemd-journal
>>> should have ability to forward logs on other machines.
>>>
>
>>> -- devel mailing list devel at lists.fedoraproject.org
>>> https://admin.fedoraproject.org/mailman/listinfo/devel
>>
>>
>>
>> -- Best regards, Michal
>>
>> http://eventhorizon.pl/
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9nQmIACgkQrlYvE4MpobPMkACeImKNxcR3/AUqrJlwcnJ+sUsM
tacAniIGW9vXHWEDlaTqOPDw1xsDArhO
=Q+fI
-----END PGP SIGNATURE-----
More information about the devel
mailing list