Stacy Magedanz
2014-10-01 15:18:50 UTC
We recently switched our authentication method to CAS. (Previously, we had been doing LDAP against a locally-extracted text file.)
CAS works great, but one of the side effects is that messages.txt is now full of nothing but CAS validation messages, numbered 168, 169, 170.
I used to find the messages file useful for discovering sites that were down or other problems with hosts, but if those messages are still being recorded, they're lost among the 168-70 messages. Is there any way I can weed out all the CAS noise from the file, or am I just stuck with it?
_______________
Stacy Magedanz
Coordinator, Electronic Resources & Serials
John M. Pfau Library CSUSB
5500 University Parkway
San Bernardino, CA 92407
909 537 5103
***@csusb.edu
http://www.lib.csusb.edu<http://www.lib.csusb.edu/>
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
CAS works great, but one of the side effects is that messages.txt is now full of nothing but CAS validation messages, numbered 168, 169, 170.
I used to find the messages file useful for discovering sites that were down or other problems with hosts, but if those messages are still being recorded, they're lost among the 168-70 messages. Is there any way I can weed out all the CAS noise from the file, or am I just stuck with it?
_______________
Stacy Magedanz
Coordinator, Electronic Resources & Serials
John M. Pfau Library CSUSB
5500 University Parkway
San Bernardino, CA 92407
909 537 5103
***@csusb.edu
http://www.lib.csusb.edu<http://www.lib.csusb.edu/>
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu