-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Chris,
The reason I did not reply to your earlier comment regarding the variability of the authdaemon socket location is because it probably has to be fully user specifiable.
Any distro could tamper with the authdaemonrc's authdaemonvar and place this stuff anywhere.
As such, any general solution would require the user to fully specify the authdaemond socket path. This would have to take the form of a environment variable setting in a .bashrc or courier startup script, editing a value in this perl module, appending a __data__ section or the such like. In all of these cases, it would be just as easy to in-place edit this in the socket handle of this script ...
The great thing about Perl of course is that you are welcome to modify it in any way you wish to meet your particular use-case.
But I'd suggest that if you are going to do this, then you should move your code into the BEGIN block to guarantee it's set before first use, and you could also do a -S test to check that it's a socket ;)
Cheers, Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.3.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org Comment:
iD8DBQE/+jF1CfroLk4EZpkRAlhiAJ9z1BE+5lxhYnEjp8IcgR2ediVMyQCgoekx +HmJ6grvpw4r6Iw1Gxzpeus= =RUi/ -----END PGP SIGNATURE-----
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
