Hello, On Fri, 23 Sep 2011, Greg Freemyer wrote:

Suppose I have a "file" (not a script) that has content:

### TEST_DEV=/dev/sda3 echo $TEST_DEV ###

If I source that (. filename) it will not create a new process. The shell itself is able to process those commands. (It has a built-in echo command.)

Correct. xterm1> cat /tmp/t.sh TEST_DEV=/dev/sda3 echo $TEST_DEV /bin/echo $TEST_DEV xterm1> echo $$ 3236 xterm2> LANG=C strace -f -e process -p 3236 xterm1> . /tmp/t.sh /dev/sda3 /dev/sda3 [meanwhile on xterm2, pruned to the relevant syscalls] clone(Process 24593 attached [pid 24593] execve("/bin/echo", ["/bin/echo", "/dev/sda3"], [/* 125 vars */]) = 0 Process 3236 resumed Process 24593 detached --- SIGCHLD (Child exited) @ 0 (0) --- xterm1> /tmp/t.sh /dev/sda3 /dev/sda3 [meanwhile on xterm2, pruned to the relevant syscalls] clone(Process 24635 attached [pid 24635] execve("/tmp/t.sh", ["/tmp/t.sh"], [/* 125 vars */]) = -1 ENOEXEC (Exec format error) [pid 24635] execve("/bin/sh", ["/bin/sh", "/tmp/t.sh"], [/* 125 vars */]) = 0 [pid 24635] clone(Process 24636 attached child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f55576939d0) = 24636 [pid 24636] execve("/bin/echo", ["/bin/echo", "/dev/sda3"], [/* 122 vars */]) = 0 Process 24635 resumed Process 24636 detached [pid 24635] --- SIGCHLD (Child exited) @ 0 (0) --- Process 3236 resumed Process 24635 detached --- SIGCHLD (Child exited) @ 0 (0) ---

If I execute the above (./filename or just plain filename) then a new shell child process is invoked to run the commands.

If I modify the file to say:

### TEST_DEV=/dev/sda3 /bin/echo $TEST_DEV echo $TEST_DEV ###

Then when I source the file, a child process (/bin/echo) is launched, but only for that one command, the first and last are still processed by the original shell.

And if I execute the file I get both a child shell process and a grandchild /bin/echo process.

Correct. See above. Don't speculate, use the tools ;) -dnh -- I find all proselytisation to be misguided at least. The way I see it, it's not the Enlightened or the Chosen trying to save me or anyone, but just some meme trying to survive in the great war for brain real estate. -- Maarten Wiltink -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hello, On Fri, 23 Sep 2011, sc wrote:

On Friday, September 23, 2011 16:02:28 Philipp Thomas wrote:

...

No. A normal user has '.' in his/her path by default, as you can check by doing 'echo $PATH'. The user root doesn't have '.' in PATH for the reasons I wrote.

i'll take issue with that last -- i was always told it is dangerous and scary to put '.' in path, and have never seen a distribution (in my limited experience) that puts it there by default

==== /etc/sysconfig/suseconfig [SUSE 11.4/64bit] ==== # # Do you want to have "." in root path? This is not recommended, but # many people do prefer it (yes/no). The setting affects all system # users (with uid < 100) # CWD_IN_ROOT_PATH="no" ## Type: yesno ## Default: yes # # Do you want to have "." in the path for normal users? # Defaults to "yes" since this has been the case for years. # CWD_IN_USER_PATH="no" ==== I'm not 100% sure if that's the 11.4 default, as this is an upgrade from 11.1 via 11.2 and that file might have been kept. HTH, -dnh -- "No one goes mad quicker than a totally sane person." -- Terry Pratchett, The Light Fantastic, p. 193 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hello, On Sat, 24 Sep 2011, Lars Müller wrote:

On Sat, Sep 24, 2011 at 12:36:20AM +0200, David Haller wrote: [ 8< ]

...

I'm not 100% sure if that's the 11.4 default, as this is an upgrade from 11.1 via 11.2 and that file might have been kept.

grep CWD_IN_ /var/adm/fillup-templates/sysconfig.suseconfig CWD_IN_ROOT_PATH="no" CWD_IN_USER_PATH="yes"

For openSUSE 11.4 and Factory.

Thank you! So the default hasn't changed yet. I think it should. NOW! Let's have a default of (implicitly) CWD_IN_USER_PATH="no" with 12.2 at latest. Oh, what I don't remember[1] is at what position "." got added to PATH if that variable was set to "yes". If last, just get rid of it, if first, change it to "last" with 12.1. That stupidity has stuck around far far too long already. Those who want to shoot themselves can still use it by setting CWD_IN_USER_PATH to "yes" ;) Oh, and BTW: I plead for removing the variable for root altogether. root should _never ever_ have "." in his PATH. -dnh, using S.u.S.E since 5.3 and _never_ having "." in _any_ PATH. [1] if I ever tried it ;) -- Es fehlt die Glaskugel, die voraussagen kann, welche der anderen Glaskugeln heute am genauesten glaskugelt. -- Christoph Päper in drtm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Moining, On Sat, Sep 24, 2011 at 03:58:46PM +0200, David Haller wrote:

On Sat, 24 Sep 2011, Lars Müller wrote:

...

On Sat, Sep 24, 2011 at 12:36:20AM +0200, David Haller wrote: [ 8< ]

...

I'm not 100% sure if that's the 11.4 default, as this is an upgrade from 11.1 via 11.2 and that file might have been kept.

grep CWD_IN_ /var/adm/fillup-templates/sysconfig.suseconfig CWD_IN_ROOT_PATH="no" CWD_IN_USER_PATH="yes"

For openSUSE 11.4 and Factory.

Thank you!

So the default hasn't changed yet. I think it should. NOW! Let's have a default of (implicitly)

CWD_IN_USER_PATH="no"

with 12.2 at latest. Oh, what I don't remember[1] is at what position "." got added to PATH if that variable was set to "yes".

Are you getting more and more lazy? Must be the age. ;) From /etc/profile.d/profile.sh CWD_IN_USER_PATH=*) test "$val" = "yes" || continue test $UID -ge 100 && PATH=$PATH:.

If last, just get rid of it, if first, change it to "last" with 12.1. That stupidity has stuck around far far too long already. Those who want to shoot themselves can still use it by setting CWD_IN_USER_PATH to "yes" ;)

I suggest to keep it simple stupid and to change the default of CWD_IN_USER_PATH to no

Oh, and BTW: I plead for removing the variable for root altogether. root should _never ever_ have "." in his PATH.

@Rudi: As you added CWD_IN_USER_PATH only ten years back you might still remember why these two settings are needed. ;) Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany