Prev: Virtualbox and kernel 2.6.30.5 (Slackware64)
Next: Montreal wins Grey Cup 28-27
From: root on 29 Nov 2009 05:21
I do almost all my work using the command line and I
have noticed a difference in type-ahead: when I enter
the next command while a previous command is still
running the new command is ignored. The version of
bash is the same as in 12.2, I have not re-compiled
the particular applications I am using, so the difference
must come from the change in the kernel?

Any way I can revert to the old behavior?

Thanks.
From: Dan C on 29 Nov 2009 11:06
On Sun, 29 Nov 2009 10:21:46 +0000, root wrote:

> I do almost all my work using the command line and I have noticed a
> difference in type-ahead: when I enter the next command while a previous
> command is still running the new command is ignored. The version of bash
> is the same as in 12.2, I have not re-compiled the particular
> applications I am using, so the difference must come from the change in
> the kernel?
>
> Any way I can revert to the old behavior?
>
> Thanks.

Try slowing down a little. What's the hurry?


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he wiped the vomit from his chin.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
From: Douglas Mayne on 29 Nov 2009 11:48
On Sun, 29 Nov 2009 10:21:46 +0000, root wrote:

> I do almost all my work using the command line and I have noticed a
> difference in type-ahead: when I enter the next command while a previous
> command is still running the new command is ignored. The version of bash
> is the same as in 12.2, I have not re-compiled the particular
> applications I am using, so the difference must come from the change in
> the kernel?
>
> Any way I can revert to the old behavior?
>
> Thanks.
>
FWIW: On my Slack 13 system, I do not see that behavior.

OT: I have recently started using the "screen" command which is a useful
terminal multiplexer. It is a lot more useful than I first estimated.

--
Douglas Mayne
From: fred on 29 Nov 2009 16:07
root <NoEMail(a)home.org> wrote:
> I do almost all my work using the command line and I
> have noticed a difference in type-ahead: when I enter
> the next command while a previous command is still
> running the new command is ignored. The version of
> bash is the same as in 12.2, I have not re-compiled
> the particular applications I am using, so the difference
> must come from the change in the kernel?

> Any way I can revert to the old behavior?

My system (Slack 13) works as usual. Could it be command dependent?

Have fun,
Fred
From: Lew Pitcher on 29 Nov 2009 19:05
Douglas Mayne <invalid(a)invalid.com> trolled:
> On Sun, 29 Nov 2009 21:13:33 +0000, Realto Margarino wrote:

> So far, I have found screen useful for the following tasks:
>
> 1. To run remote jobs which take a long time to complete. If the
> connection goes down, then the screen command can be reattached and the
> job's progress can be determined.
>
> 2. To run jobs in a "secure" terminal. This is similar to item #1 above.
> I use this mode when a job must be started from a terminal, and it is not
> desirable to leave the terminal running unattended because that would be
> a security hole. Previous to using screen, I relied on the lock provided
> by the X screensaver. screen is more secure than that.
>
> 3. To host local servers such as vncserver. Again, similar to #1 and #2.
> vnc is important in virtual environments, which is also a throwback to an
> earlier design. It seems "time sharing" is in fashion, again. This time,
> the accounting measure is the number of virtual machine instances, not
> CPU cycles. It's interesting ping-pong, as the compute intensive tasks
> are either distributed at the nodes or concentrated at the host.

Wouldn't the "nohup" command suit your purposes? Admittedly, I
haven't used the command in a long time. But it means "no hangup"
and I believe I used to use it to keep stuff going on dialup
servers, after I had hung up. You can also get stuff to work
reliably in the background if you use crontab and the crond daemon.

There is surely more than one way to skin a cat with linux and I
am not trying to deride your use of the screen command. I just
haven't even thought of using it in years...


LewPitcher(a)LewPitcher.ca
--
Official Website -->> http://lewpitcher.ca/
Something to look at: -->> http://www.emusclemag.com/
Lonely in Brampton? -->> http://gaypros.meetup.com/cities/ca/on/brampton/
Peel HIV/AIDS Network -->> http://www.phan.ca/home.html
 |  Next  |  Last
Pages: 1 2
Prev: Virtualbox and kernel 2.6.30.5 (Slackware64)
Next: Montreal wins Grey Cup 28-27