I’m glad I put that last sentence in my post (more when I have time)!! Actually the -i options is one of the first things I used lsof for! That is one of the items I will be adding soon.
Very nice – just what I was looking for.
I wonder how hard it would be to reload the contents if the file changes? 🙂
Thanks,
chris
BTW this line got truncated in the post:
<util:properties id="attr" location="file:/etc/cas/ldap.attribtues
Glad to hear it Chris!
The util schema does support automatic property file reloading, but I don’t believe it does with the method described above. I believe you would have to write a custom bean to accomplish this.
Thank you a lot for this. I am having a problem with file lock contention on my LMS system and reading your posting helped me a lot. I was able to figure out that the problem we are experiencing is actually a application problem and not a system problem. Thank you.
FYI, when I was setting this up on RHEL tomcat & openJDK 7 it was really picky about wanting a particular version of opensaml (1.1b)
Yeah, I forgot to copy that part from Marvin’s documentation. As far as I know, regardless you should use 1.1b. I updated my post.
Don’t forget the wonders of “-i” !
Great to see discussion of SELinux contexts … these are often ignored.
(And yes, I’m still following the team blog – keep up the good postings!)
I’m glad I put that last sentence in my post (more when I have time)!! Actually the -i options is one of the first things I used lsof for! That is one of the items I will be adding soon.
Nice to know someone is reading, very motivating.
Very nice – just what I was looking for.
I wonder how hard it would be to reload the contents if the file changes? 🙂
Thanks,
chris
BTW this line got truncated in the post:
<util:properties id="attr" location="file:/etc/cas/ldap.attribtues
Glad to hear it Chris!
The util schema does support automatic property file reloading, but I don’t believe it does with the method described above. I believe you would have to write a custom bean to accomplish this.
Unicon did implement something similar to this for their JSON based service registry. Although I can’t say whether this would work with the LDAP attributes externalization. The source can be found here: https://github.com/Unicon/springframework-addons/wiki/Resource-change-detecting-event-notifier
For my own uses at least, I would tend to stay away from automatic reloading in a production environment.
Thanks for the catch BTW, looks like I can’t spell attributes either 🙂
Thank you a lot for this. I am having a problem with file lock contention on my LMS system and reading your posting helped me a lot. I was able to figure out that the problem we are experiencing is actually a application problem and not a system problem. Thank you.
That is a *great* tip!
[…] post titled Remember when you issued that command…? by Mitch @ UConn on how to include the date/time of each command in your Bash […]
Cool! Thank you for sharing.
This post did help me a lot!