You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the DomainParser via the WhoisParser and am doing whois queries both within web server/request contexts and within a shell script run by a cron job.
When the whois is done first within the web request context the DomainParser creates a cache file with file permissions that wont allow the subsequent shell script runs to get write access to the cached file. This causes the shell script to throw notices because it cannot remove and recreate the (stale) cached file.
My suggestion would be to either allow configuring file permissions for the cache file through both DomainParser and WhoisParser or get rid of the caching to file through the approach I've outlined in RFC and PR #3.
The text was updated successfully, but these errors were encountered:
I'm using the DomainParser via the WhoisParser and am doing whois queries both within web server/request contexts and within a shell script run by a cron job.
When the whois is done first within the web request context the DomainParser creates a cache file with file permissions that wont allow the subsequent shell script runs to get write access to the cached file. This causes the shell script to throw notices because it cannot remove and recreate the (stale) cached file.
My suggestion would be to either allow configuring file permissions for the cache file through both DomainParser and WhoisParser or get rid of the caching to file through the approach I've outlined in RFC and PR #3.
The text was updated successfully, but these errors were encountered: