-
Notifications
You must be signed in to change notification settings - Fork 378
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
sipp changes working dir if script specified with path #399
Comments
Well... it's not a chdir thing, but a scenario_file thing:
In your case scenario_file is not Not sure if we want to change this behaviour. |
(OTOH, if we want to change it, now is the time.) |
Instead of them being relative to the scenario file, they are now placed in the current working directory. This makes more sense. Closes #399
Instead of them being relative to the scenario file, they are now placed in the current working directory. This makes more sense. Closes #399
i checked current master. |
Happy? |
yes. |
This change broke large automated system that expects the sipp log files to be placed in scenario folders. |
You can add automated system command like
And then start sipp. can you change large automated system script? |
Another option you can use |
I want place sipp log files (used
-trace_err -trace_screen
option) in directory /var/log/sipp.Do to this is executed
After script start i can see logs in
/etc/sipp
folder.Could sipp not change current dir when accessed script files.
The text was updated successfully, but these errors were encountered: