Hi,

The current Hijack design is that it detects player startup in fs/exec.c and fs/read_write.c, and then reads config.ini in the player's context. That way, it can apply the various player-only macros (";@AC", ";@DC", ";@HOME", ";@WORK" ...) it supports to the player's buffered copy of config.ini, but not to anyone else's copy. Nor to subsequent reads of the file by the player (during a "sync", for instance).

I suppose that code could stay in place, and one could then also have Hijack read the config.ini file for itself on the first call to "do_execve" (a nice safe time, as the filesystems are guaranteed to be available by then).

Cheers