From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Scripts not working... HELP!
Date: Thu, 28 Apr 2011 08:12:34 +0200 [thread overview]
Message-ID: <4DB90552.5060104@smash-net.org> (raw)
In-Reply-To: <20110428054001.GA3033@waltdnes.org>
Had similar symptoms as my default system python was not defined properly.
Use "eselect python list --python2" to see if that is the case.
Set it with "eselect python set --python2 <number>" if necessary.
Regards
Norman
Am 04/28/11 07:40, schrieb Walter Dnes:
> This message is coming from my 32-bit "hot backup" gentoo machine.
> For some reason, any script that I call on my 64-bit machine immediately
> returns to the command prompt. No warnings or error messages or
> diagnostics. Builtins and compiled executables work OK. For instance,
> if I have a script named "xyz" that goes like so...
>
> #!/bin/bash
> man bash
>
> ..., executing "xyz" or "~/bin/xyz" results in bash immediately
> returning to to the command prompt. If I type "man bash", it works OK.
> On top of everything else, getmail seems to go into "forkbomb mode",
> generating a gazillion processes, and eventually locking up the machine,
> if I type in...
> /usr/bin/getmail -v -v -v --rcfile rc_cotse
>
> It looks like the script is being totally ignored, e.g...
>
> waltdnes@i3 ~ $ emerge anyone home?
> waltdnes@i3 ~ $
>
> Any ideas what gives?
>
next prev parent reply other threads:[~2011-04-28 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 5:40 [gentoo-user] Scripts not working... HELP! Walter Dnes
2011-04-28 6:11 ` Alexey Mishustin
2011-04-28 6:12 ` Norman Rieß [this message]
2011-04-28 10:21 ` Alex Schuster
2011-04-28 22:16 ` [gentoo-user] [SOLVED] " Walter Dnes
2011-04-29 7:25 ` Norman Rieß
2011-04-29 8:31 ` Mick
2011-04-29 8:41 ` covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DB90552.5060104@smash-net.org \
--to=norman@smash-net.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox