* jobs
@ Igor Gueths
` jobs Toby Fisher
` jobs Thomas D. Ward
0 siblings, 2 replies; 4+ messages in thread
From: Igor Gueths @ UTC (permalink / raw)
To: speakup
Hi all. Just as an experiment, I attempted to put Lynx in the background
and Freeamp was streaming a radio station that I just happened to be
listening to. I suspended the job and put job 1 in the background, because
I had no other jobs running. It ran fine and I was sitting at the bash
prompt, however when I typed a command, the job got killed. Does anyone
know why this happens? I think that it is very interesting, considering
that a cp and/or erasing job on a Cd for example would run fine after
being suspended and switched to a background process. Could this have to
do that Lynx can't run in the background if it is running an imbedded
application such as Freeamp? Thanks in advance for any info regarding
this!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: jobs
jobs Igor Gueths
@ ` Toby Fisher
` jobs Victor Tsaran
` jobs Thomas D. Ward
1 sibling, 1 reply; 4+ messages in thread
From: Toby Fisher @ UTC (permalink / raw)
To: speakup
On Tue, 2 Apr 2002, Igor Gueths wrote:
> Hi all. Just as an experiment, I attempted to put Lynx in the background
> and Freeamp was streaming a radio station that I just happened to be
> listening to. I suspended the job and put job 1 in the background, because
> I had no other jobs running. It ran fine and I was sitting at the bash
> prompt, however when I typed a command, the job got killed. Does anyone
> know why this happens? I think that it is very interesting, considering
> that a cp and/or erasing job on a Cd for example would run fine after
> being suspended and switched to a background process. Could this have to
> do that Lynx can't run in the background if it is running an imbedded
> application such as Freeamp? Thanks in advance for any info regarding
> this!
Lynx does not appreciate being put into the background, even when, for
example, doing an ftp download. Still, with 6 consoles to play with, I
haven't run out yet, though I have come close. *grin*
--
Toby Fisher Email: toby@g0ucu.freeserve.co.uk
Tel.: +44(0)1480 417272 Mobile: +44(0)7974 363239
ICQ: #61744808
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: jobs
jobs Igor Gueths
` jobs Toby Fisher
@ ` Thomas D. Ward
1 sibling, 0 replies; 4+ messages in thread
From: Thomas D. Ward @ UTC (permalink / raw)
To: speakup
I've seen similar problems with using background, and choose to use screen
instead. That works 100% better.
On Tue, 2 Apr 2002, Igor Gueths wrote:
> Hi all. Just as an experiment, I attempted to put Lynx in the background
> and Freeamp was streaming a radio station that I just happened to be
> listening to. I suspended the job and put job 1 in the background, because
> I had no other jobs running. It ran fine and I was sitting at the bash
> prompt, however when I typed a command, the job got killed. Does anyone
> know why this happens? I think that it is very interesting, considering
> that a cp and/or erasing job on a Cd for example would run fine after
> being suspended and switched to a background process. Could this have to
> do that Lynx can't run in the background if it is running an imbedded
> application such as Freeamp? Thanks in advance for any info regarding
> this!
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: jobs
` jobs Toby Fisher
@ ` Victor Tsaran
0 siblings, 0 replies; 4+ messages in thread
From: Victor Tsaran @ UTC (permalink / raw)
To: speakup
that's true, Lynx is not on the list of apps that want to be run in the
background.
Vic
----- Original Message -----
From: "Toby Fisher" <toby_fisher@bigfoot.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, April 04, 2002 4:55 AM
Subject: Re: jobs
> On Tue, 2 Apr 2002, Igor Gueths wrote:
>
> > Hi all. Just as an experiment, I attempted to put Lynx in the background
> > and Freeamp was streaming a radio station that I just happened to be
> > listening to. I suspended the job and put job 1 in the background,
because
> > I had no other jobs running. It ran fine and I was sitting at the bash
> > prompt, however when I typed a command, the job got killed. Does anyone
> > know why this happens? I think that it is very interesting, considering
> > that a cp and/or erasing job on a Cd for example would run fine after
> > being suspended and switched to a background process. Could this have to
> > do that Lynx can't run in the background if it is running an imbedded
> > application such as Freeamp? Thanks in advance for any info regarding
> > this!
>
> Lynx does not appreciate being put into the background, even when, for
> example, doing an ftp download. Still, with 6 consoles to play with, I
> haven't run out yet, though I have come close. *grin*
>
> --
> Toby Fisher Email: toby@g0ucu.freeserve.co.uk
> Tel.: +44(0)1480 417272 Mobile: +44(0)7974 363239
> ICQ: #61744808
> Please avoid sending me Word or PowerPoint attachments.
> See http://www.fsf.org/philosophy/no-word-attachments.html
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
jobs Igor Gueths
` jobs Toby Fisher
` jobs Victor Tsaran
` jobs Thomas D. Ward
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).