8 commits

Author	SHA1	Message	Date
Jon Siwek	186e67ec1d	Allow logging filters to inherit default path from stream. ... This allows the path for the default filter to be specified explicitly when creating a stream and reduces the need to rely on the default path function to magically supply the path. The default path function is now only used if, when a filter is added to a stream, it has neither a path nor a path function already. Adapted the existing Log::create_stream calls to explicitly specify a path value. Addresses BIT-1324	2015-03-19 14:49:55 -05:00
Daniel Thayer	9374a7d584	Fix typos and formatting in the policy/protocols docs ... Also updated a test related to these changes, and adjusted line numbers.	2013-10-21 02:34:28 -05:00
Daniel Thayer	9d2668a3f4	Fix incorrect uses of reST directives ... These did not generate any warning messages unfortunately, so had to find them using grep.	2013-10-17 01:50:42 -05:00
Jon Siwek	e0805498c6	Fix some warnings from sphinx when building docs.	2012-11-15 16:40:18 -06:00
Robin Sommer	4e12813445	Fixing tests after modbus merge.	2012-11-05 15:58:38 -08:00
Robin Sommer	86ce564107	Merge remote-tracking branch 'remotes/origin/topic/seth/modbus-merge' ... * remotes/origin/topic/seth/modbus-merge: Small modbus documentation update and tiny refactoring. Final touches to modbus analyzer for now. Major revisions to Modbus analyzer support (not quite done yet). put some make-up on Modbus analyser Modbus analyser, added support: FC=20,21 Modbus analyzer,added support: FC=1,2,15,24 Modbus analyzer, current support: FC=3,4,5,6,7,16,22,23 Closes #915.	2012-11-05 15:26:57 -08:00
Seth Hall	c32b179ac5	Small modbus documentation update and tiny refactoring.	2012-10-31 23:57:38 -04:00
Seth Hall	a2f336cc72	Final touches to modbus analyzer for now. ... - There are still some broken events in the modbus analyzer because I don't have traffic to test with (coil and record related events primarily). - There are a few example scripts in policy/protocols/modbus	2012-10-31 23:34:43 -04:00