[openbox] set working directory when starting Openbox

Crni Gorac cgorac at gmail.com
Thu May 22 12:30:33 EDT 2014

I already did strace, and indeed one can find "chdir($HOME)" in the
listing - it happens somewhere in between syscalls to create
$HOME/.config/openbox/openbox.log file and
$HOME/.cache/openbox/sessions directory, so I strongly suspecting
Openbox is doing this current directory change, and this is why I
posted the question in the first place.

I wouldn't agree that changing current directory to $HOME is right
thing to do - current directory is "inherited" through exec*()
syscalls, and then further when "exec-ed" program forks child
processes (as Openbox is doing to start xterm).  I know I can achieve
what I want in number of other ways, but I was just curious why
Openbox is doing this current directory change...


On Thu, May 22, 2014 at 6:02 PM, Mathias Dufresne
<mathias.dufresne at gmail.com> wrote:
> I don't use xinit and I never used it but I expect your issue is in the
> chain of processes running between your login and the apparition of openbox.
> All I can say is if I create the 2 files as you described then run a startx,
> I have the same behaviour than you: a full launch of openbox, which set up a
> new environment for my user session which set up my default directory to my
> homedir.
> Once more, for me this is a normal behaviour: new session, new environment.
> And what happen during that time, I have no idea. You can use this command
> line to generate awfully huge logs:
> strace exec openbox-session > /your/path/to/openbox.log 2>
> /your/path/to/openbox.strace
> the first ">" is to get standard logs (those sent to the console)
> the second is to get stderr which is used by strace which should tell you
> alsmot all what happens during the launch time.
> And finally, if your goal is only to have your user thrown into /tmp after
> bash is launched in interactive mode, modify your .bashrc.
> Cheers,
> mat

More information about the openbox mailing list