> On Fri, Jan 28, 2011 at 12:50 PM, Nigel Kukard <[email protected]> wrote: >> Try enabling full debugging, you'll then see what policy checks are >> being done and if they matching ... this will more than likely help >> pinpoint where the problem lies. >> > Thanks for the response, > > I have had the following configuration : > > # Log level: > # 0 - Errors only > # 1 - Warnings and errors > # 2 - Notices, warnings, errors > # 3 - Info, notices, warnings, errors > # 4 - Debugging > log_level=4 > > Does this means I have enabling full debugging or do I need changes > another portion of policyd configuration? # Things to log in extreme detail # modules - Log detailed module running information # tracking - Log detailed tracking information # policies - Log policy resolution # protocols - Log general protocol info, but detailed # bizanga - Log the bizanga protocol # cache - Log cache usage on client shutdown # # There is no default for this configuration option. Options can be # separated by commas. ie. protocols,modules # #log_detail=
-N
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
