Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #172592
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Failed to execute child process (no such file or directory) ... |
| Date | 2016-09-21 17:30 +0200 |
| Message-ID | <sjRDb-2gi-19@gated-at.bofh.it> (permalink) |
| References | <sjRtw-2de-21@gated-at.bofh.it> <sjRtw-2de-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web