utm-plc 0.1.2 → 0.1.3
Sign up to get free protection for your applications and to get access to all the features.
- data/README.mkd +6 -2
- metadata +1 -1
data/README.mkd
CHANGED
@@ -35,7 +35,8 @@ Here, let me show you. In this configuration, the main web filter (under Web Pr
|
|
35
35
|
is configured to log accessed pages and to not log blocked pages. FilterAction One is configured to log
|
36
36
|
blocked pages, but not accessed pages. FilterAction Two is configured to log accessed pages but not blocked
|
37
37
|
pages. The Default content filter block action is configured to log accessed but not blocked pages.
|
38
|
-
FilterAction Three is configured to not log either accessed or blocked pages
|
38
|
+
FilterAction Three is configured to not log either accessed or blocked pages, but isn't in use by any Filter
|
39
|
+
Profile. Here we go:
|
39
40
|
|
40
41
|
$ ./plc.rb
|
41
42
|
What port?: 22
|
@@ -78,13 +79,16 @@ FilterAction Three is configured to not log either accessed or blocked pages. H
|
|
78
79
|
Please activate the 'Log Accessed Pages' option for the Web Filter Action named: FilterAction One
|
79
80
|
Done
|
80
81
|
|
82
|
+
Note that FilterAction Three doesn't make an appearance. This is because it isn't being used by any of the
|
83
|
+
current Web Filter or Proxy Profiles, so no traffic is hitting it, so the tool doesn't [see or] report it.
|
84
|
+
|
81
85
|
### It doesn't work ###
|
82
86
|
|
83
87
|
Check the output of `echo $PATH`, and compare it against `which bin/plc`. Is the directory that plc is in,
|
84
88
|
in your path? If not, this will be your problem. To resolve this, append that directory to your path.
|
85
89
|
How exactly to do this is left as an exercise for the reader.
|
86
90
|
|
87
|
-
If you're
|
91
|
+
If you're absolutely positively pinkey-swearsey sure that your $PATH contains the right directory, and it
|
88
92
|
still isn't doing what you think it should be doing, [file a bug](https://github.com/jeffWelling/utm-plc/issues).
|
89
93
|
|
90
94
|
### Author ###
|