Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #172590 > unrolled thread

Re: Failed to execute child process (no such file or directory) ...

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Failed to execute child process (no such file or directory) ... "Thomas Schmitt" <scdbackup@gmx.net> - 2016-09-21 17:20 +0200
    Re: Failed to execute child process (no such file or directory) ... Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-21 17:30 +0200
    Re: Failed to execute child process (no such file or directory) ... Anthony Baldwin <baldwinlinguas@gmx.com> - 2016-09-21 20:40 +0200

#172590 — Re: Failed to execute child process (no such file or directory) ...

Hi,

Anthony Baldwin wrote:
> giving the full path in the rc.xml doesn't seem to make
> any difference.

Are you sure openbox is aware of the change ?
(Did you restart it ? Does it react immediately on newly added
 key combinations ?)


> Yes, the $PATH is set in my .bashrc...
> Wait.. Is this why I can start them in a terminal, but openbox can't?

Possibly.

It depends on when and by what entity the openbox window manager was
started and whether it uses PATH to find commands.
If the starter was some kind of shell, then it probably has forwarded
its own PATH variable to openbox. If it was something more fancy, then
behavior depends on the mood of its developers.

You could put a script into /usr/bin (where it will be found, i hope),
let it print the PATH to a file, bind it to a key combination, and
look what it writes into the file:
  #!/bin/sh
  echo "$PATH" >/tmp/my_openbox_test_for_PATH

But if PATH was to blame, then an absolute program path should have
helped. If it came into effect, that is.


Have a nice day :)

Thomas

[toc] | [next] | [standalone]

#172592

On Wed, Sep 21, 2016 at 05:20:31PM +0200, Thomas Schmitt wrote:
> You could put a script into /usr/bin (where it will be found, i hope),
> let it print the PATH to a file, bind it to a key combination, and
> look what it writes into the file:
>   #!/bin/sh
>   echo "$PATH" >/tmp/my_openbox_test_for_PATH

Or you can use  ps eww -p "$(pgrep openbox)"  (or directly substitute
the PID you want in case that command substitution is wrong; it works
for me with fvwm).  The PATH should be visible in the process's
environment as displayed by ps.  There may be a lot of noise to filter
out, of course.

[toc] | [prev] | [next] | [standalone]

#172597

On 09/21/2016 11:20 AM, Thomas Schmitt wrote:
> Hi,
>
> Anthony Baldwin wrote:
>> giving the full path in the rc.xml doesn't seem to make
>> any difference.
>
> Are you sure openbox is aware of the change ?
> (Did you restart it ? Does it react immediately on newly added
>  key combinations ?)

Normally, yes, OBx would, indeed reload, the configurations in its 
rc.xml file upon a --restart and immediately implement any changes.
>
>
>> Yes, the $PATH is set in my .bashrc...
>> Wait.. Is this why I can start them in a terminal, but openbox can't?
>
> Possibly.
>
> It depends on when and by what entity the openbox window manager was
> started and whether it uses PATH to find commands.
> If the starter was some kind of shell, then it probably has forwarded
> its own PATH variable to openbox. If it was something more fancy, then
> behavior depends on the mood of its developers.
>
> You could put a script into /usr/bin (where it will be found, i hope),
> let it print the PATH to a file, bind it to a key combination, and
> look what it writes into the file:
>   #!/bin/sh
>   echo "$PATH" >/tmp/my_openbox_test_for_PATH
>
> But if PATH was to blame, then an absolute program path should have
> helped. If it came into effect, that is.

So it's not likely a path problem it seems..

Thanks,
Tony
>
>
> Have a nice day :)
>
> Thomas
>


-- 
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web