AGI Directory Bug?

In Asterisk 1.4.11 the behavior of the working directory for AGI scripts seems to be a little different than it was in asterisk 1.4.1. In both versions, safe_asterisk changes to /tmp before starting asterisk. In 1.4.1, when I launch AGI scripts, their working directory is the directory they are launched from (/var/lib/asterisk/agi-bin). In 1.4.11, however, their working directory is the directory asterisk was original launched from (/tmp).

This causes relative paths in the AGI scripts to fail (unless they are relative to /tmp).

It seems like the correct behavior would be to make the working directory the same as the executing script, during that scripts execution.

I can work around this problem by changing safe_asterisk to start from /var/lib/asterisk/agi-bin/. But, I’m not sure if that has any negative side-effects.

Does anyone else have this problem? Is the new behavior wrong? Do I have something configured wrong?

Thanks,
Joel