> __DIR__	The directory of the file.

It is not affected by chdir(), as expected, maybe you're looking for getcwd().

It's chroot, not chdir. The idea is that __DIR__ and friends should be updated to reflect the new path to the file after the chroot(2) call. Which is not necessarily possible (eg, file is outside the new root) so I don't know if anything can/should be done about it anyways.

echo __FILE__; // originally /path/to/file.php
chroot("/path");
echo __FILE__; // now /to/file.php

In my current use case I execute chroot in auto_prepend_file so I'm not sure when the __FILE__ constant is filled.

The reason for this is to execute customer cronjobs in a jail. And most frameworks uses __DIR__ to require other files like autoload.php...

In this case it seams that the executed file get loaded (and __DIR__ is set) before the auto_prepend_file is executed. I'm not sure if it would be possible that at least this can be fixed.

No -__DIR__ reflects the physical directory where the current file is stored and is practically the same as __FILE__ without the basename - it is known at compile time and any change after that would break half of the world in existing code

> Which is not necessarily possible (eg, file is outside the new
> root) so I don't know if anything can/should be done about it
> anyways.

That.  It might be best to just clearly document that chroot()
doesn't affect __DIR__ and friends.