On Wed, Nov 13, 2013 at 7:35 AM, Piotr Grzybowski wrote:
> Hi Everyone, hi Joel,
>
> the idea is nice, and I can really see that it is useful, but I would
> be extremely careful with introducing those kind of changes, it can be
> easily interpreted as "backdoor feature", that is: from security po
On Wed, Jul 17, 2013 at 1:52 AM, Cedric Blancher
wrote:
> On 16 July 2013 23:12, Linus Torvalds wrote:
>> On Tue, Jul 16, 2013 at 1:31 PM, Lionel Cons
>> wrote:
>>>
>>> Either your ulimit -i is greater than 63000 or we have a Linux bug. If
>>> ulimit -i is reached then kill(1) should fail.
>>
>
On Mon, Dec 3, 2012 at 7:48 PM, Dan Douglas wrote:
> On Wednesday, November 28, 2012 07:23:17 PM Nikolai Kondrashov wrote:
>> @(a&!(b))
>
> This is the syntax ksh93 already uses. So far nobody else has adopted it, but
> the equivalent as you already mentioned is the transformation to:
>
> !(!(...)
Chet Ramey wrote:
I want Bash to kill the commands that I run when my script exits. The
option "huponexit" doesn't work for me because Bash runs
non-interactively. How can I achieve my goal?
Since it's a script, all processes are in the same process group.
Depending on your system (most acc
Thank you for your advice. It's really a nifty solution, and it works
great for me!
Best,
Irek
Chet Ramey wrote:
I run a script, and so Bash runs non-interactively. In the script I
run some commands with:
> some_command &
My script is run by a process which doesn't have a controlling
t
I run a script, and so Bash runs non-interactively. In the script I
run some commands with:
> some_command &
My script is run by a process which doesn't have a controlling
terminal, and so my script doesn't inherit the terminal.
I want Bash to kill the commands that I run when my script exi
