-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default configuration file not used since commit f7373b7 #548
Labels
BUG
The issue describes likely incorrect product functionality that likely needs corrected.
Comments
Fish-Git
added a commit
that referenced
this issue
Mar 3, 2023
Sorry about that! Should be fixed now by commit 440e62e. Closing. |
That got it, thanks! |
Jeff, I understand now why you wanted that new feature in Hercules-Helper for Windows. Bill |
Yeah, that was really handy. I was able to write a Perl script to do it on Linux by massaging the config file, but I couldn't find a way with Windows. Thanks again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The changes made in commit f7373b7 have caused Hercules to stop defaulting to a configuration file name of "hercules.cnf". In the prior commit, hercules.cnf was read if it existed and a "file not found" error was raised if not. Since f7373b7, command usage errors are raised whether or not the configuration file exists.
As of commit: f7373b7
Start with a known environment
Start Hercules, defaulting all options, including the filename
Create a configuration file
Start Hercules again, showing it responds the same when the file exists
The prior commit: 468b76c
Start with a known environment
Start Hercules, using all defaults. See the file not found (HHC02342S) message
Create a configuration file
Start Hercules. It starts normally.
The text was updated successfully, but these errors were encountered: