Hello Tom,
Sunday, June 15, 2003, 7:39:29 AM, you wrote:
TB> As you can see 'x' is a heck of a lot more than 'X'.
Yes, indeed. :-) I see.
TB> First, you generally only want to use 'kill' on specific
TB> applications that can't be stopped more normally, not systems like
TB> X.
Aha - sound
Hello stormjumper,
Saturday, June 14, 2003, 9:54:26 PM, you wrote:
s> in this case, since you can still ssh in, would it be better, once
s> this happens, to issue a reboot command. hopefully at least the
s> system would bring itself down gracefully,
Ah... good suggestion.
--
Thank you,
ri
Hello Anne,
Saturday, June 14, 2003, 12:49:33 PM, you wrote:
AW> On Saturday 14 Jun 2003 7:54 pm, rikona wrote:
>> F> The New twikis work too. :D
>>
>> What's a twiki?
AW> It;s a community owned and edited site. Ours is at
Thanks for the info.
--
Thank you,
rikona
On Saturday June 14 2003 02:03 pm, rikona wrote:
> Hello Tom,
>
> Thursday, June 12, 2003, 10:54:10 AM, you wrote:
> >> That's exactly what I did, but it didn't kill it. I'd run top,
> >> get the PID, exit top, kill it, go back to top, and it's still
> >> there. Any idea why?
>
> TB>Usually I s
ppens, to issue a reboot command. hopefully at least the system would
bring itself down gracefully, better than a hard reset would.
- Original Message -
From: "rikona" <[EMAIL PROTECTED]>
To: "stormjumper" <[EMAIL PROTECTED]>
Sent: Sunday, June 15, 2003 03:32
On Saturday 14 Jun 2003 7:54 pm, rikona wrote:
> F> The New twikis work too. :D
>
> What's a twiki?
It;s a community owned and edited site. Ours is at
http://mandrake.vmlinuz.ca/bin/view/Main/WebHome
Browse around, there's a surprising amount there already, and it's
growing fast. There's also
Hello stormjumper,
Thursday, June 12, 2003, 9:57:57 PM, you wrote:
>> That seemed to bring down everything - ssh remote quit responding,
>> could not log back in, no keys worked anywhere.
s> i'm sorry to hear that. i've just tried, and killing the pid of
s> startx brought down everything running
Hello Tom,
Thursday, June 12, 2003, 10:54:10 AM, you wrote:
>> That's exactly what I did, but it didn't kill it. I'd run top, get
>> the PID, exit top, kill it, go back to top, and it's still there.
>> Any idea why?
TB>Usually I start with a 'killall ' If that doesn't get
TB> it done I run
Hello FemmeFatale,
Wednesday, June 11, 2003, 5:08:14 PM, you wrote:
F> I hate "man" pages...with a passion... they weren't meant as
F> tutorials...as such they suck. They are terse, capable but like
F> the military very practical. Rely on web stuff if you can more
F> often for how-tos & "i'm a
Hello Stephen,
Wednesday, June 11, 2003, 4:19:25 PM, you wrote:
SK> On Thu, 2003-06-12 at 04:41, rikona wrote:
>> That's exactly what I did, but it didn't kill it. I'd run top, get the
>> PID, exit top, kill it, go back to top, and it's still there. Any idea
>> why?
SK> It's probably easier to
On Thursday June 12 2003 01:27 pm, JoeHill wrote:
> On Thu, 12 Jun 2003 12:54:10 -0500
>
> Tom Brinkman <[EMAIL PROTECTED]> uttered:
> > 'kill -9' all the relevant pid's. (alias wpid='ps aux |
> > grep')
>
> or my favourite, kill `pidof "appname"`... you gotta do it as
> root, but it will kill al
- Original Message -
From: "rikona" <[EMAIL PROTECTED]>
To: "stormjumper" <[EMAIL PROTECTED]>
Sent: Thursday, June 12, 2003 07:08
Subject: Re[7]: [newbie] Backdoor for crashes?
> Hello stormjumper,
>
> Wednesday, June 11, 2003, 1:42:02 PM, you w
On Thu, 12 Jun 2003 12:54:10 -0500
Tom Brinkman <[EMAIL PROTECTED]> uttered:
> 'kill -9' all the relevant pid's. (alias wpid='ps aux | grep')
or my favourite, kill `pidof "appname"`... you gotta do it as root, but
it will kill all instances of the app without you having to do all the
PIDs. the
On Wednesday June 11 2003 01:41 pm, rikona wrote:
> SK> Ain't it all the more easy to login via telnet or ssh from
> another SK> machine and just kill the offending process(es)? Or
> is that too easy?
>
> That's exactly what I did, but it didn't kill it. I'd run top,
> get the PID, exit top, kill i
At 04:08 PM 6/11/2003 -0700, you wrote:
Hmmm... didn't know there was more than one. :-) Us newbies have a lot
to learn, I guess. I am slowly beginning to undersatnd the man pages
better. The terseness and jargon, for me, is not newbie oriented, and
sometimes quite difficult to fully understand. L
are
man kill
man 2 kill
man 7 signal
- Original Message -
From: "rikona" <[EMAIL PROTECTED]>
To: "Stephen Kuhn" <[EMAIL PROTECTED]>
Sent: Thursday, June 12, 2003 02:41
Subject: Re[5]: [newbie] Backdoor for crashes?
> Hello Stephen,
>
>
Hello Adolfo,
Wednesday, June 11, 2003, 6:28:17 AM, you wrote:
AB> I am back to RTFM, "man runlevel" and understanding scripts in
AB> /etc/rc.d/init.d/.
If you run across something that will help me recover from X crashes,
please let me know. For now, I've UNINSTALLED stellarium 0.5 (and
better
Hello Stephen,
Wednesday, June 11, 2003, 4:56:24 AM, you wrote:
SK> Anyways, REAL linux users don't use XWindows anyways. Complete
SK> waste of space. Complete waste of resource. Using a mouse for
SK> anything other than a paperweight is a useless operation with
SK> nothing but bad things to come
Hello Stephen,
Wednesday, June 11, 2003, 4:17:46 AM, you wrote:
>> I tried 'kill 1452' to > get rid of X, and that wouldn't stop it
>> either. A 'kill -9 1452' > apparently killed the machine. Reboot
>> time.
SK> Ain't it all the more easy to login via telnet or ssh from another
SK> machine and
Hello Adolfo,
Wednesday, June 11, 2003, 4:07:23 AM, you wrote:
AB> Ctrl-Alt-Backspace restarts X.
When I was snooping to find emergency fixes, I ran across an article:
How to prevent ctrl-alt-backspace from killing the X session. I
thought that was what it did. The article suggests: Start X with
On Wed, 2003-06-11 at 07:56, Stephen Kuhn wrote:
> I reckon I understand, but isn't starting a system in runlevel 3 and
> killing X two different things?? Unless I've really really missed
> something here...
For sure, the one missing something here is me.
I thought that switching from run level
On Wed, 2003-06-11 at 22:32, Charles A Edwards wrote:
> But I can't watch my porn unless I use XWindows lynx just doesn't cut
> the mustard
Good point, Charles. You win.
--
Wed Jun 11 23:05:00 EST 2003
23:05:00 up 4 days, 8:56, 4 users, load average: 0.00, 0.07, 0.10
-
On 11 Jun 2003 21:56:24 +1000
Stephen Kuhn <[EMAIL PROTECTED]> wrote:
> Anyways, REAL linux users don't use XWindows anyways. Complete waste
> of space. Complete waste of resource. Using a mouse for anything other
> than a paperweight is a useless operation with nothing but bad things
> to come ou
On Wed, 2003-06-11 at 21:41, Adolfo Bello wrote:
> > Ain't it all the more easy to login via telnet or ssh from another
> > machine and just kill the offending process(es)? Or is that too easy?
>
> Right. It is too easy.
>
> Now seriously. Rikona was talking about killing X and the best way tha
On Wed, 2003-06-11 at 07:17, Stephen Kuhn wrote:
> On Wed, 2003-06-11 at 21:07, Adolfo Bello wrote:
> > On Wed, 2003-06-11 at 00:22, rikona wrote:
> >
> > > As I understand it, Ctl+Alt+Backspace is supposed to stop X, but it
> > > does not stop according to the remote terminal. I tried 'kill 1452'
On Wed, 2003-06-11 at 21:07, Adolfo Bello wrote:
> On Wed, 2003-06-11 at 00:22, rikona wrote:
>
> > As I understand it, Ctl+Alt+Backspace is supposed to stop X, but it
> > does not stop according to the remote terminal. I tried 'kill 1452' to
> > get rid of X, and that wouldn't stop it either. A '
On Wed, 2003-06-11 at 00:22, rikona wrote:
> As I understand it, Ctl+Alt+Backspace is supposed to stop X, but it
> does not stop according to the remote terminal. I tried 'kill 1452' to
> get rid of X, and that wouldn't stop it either. A 'kill -9 1452'
> apparently killed the machine. Reboot time.
Hello rikona,
Tuesday, June 10, 2003, 8:12:58 PM, you wrote:
r> Got it working, and now looking through the 'back door' from a Win
r> machine.
Well, stellarium crashed the screen again! This time, though, I can
see (via ssh & top) that everything is running happily on the machine,
even stellariu
On Wednesday 11 Jun 2003 2:20 am, rikona wrote:
> Hello,
>
> Just had another crash, with a full screen app. Tried all the
> emergency recovery techniques mentioned earlier, but nothing seemed to
> restore a console or screen I could work with. Did a reboot. :-(
>
> For several of the emergency thi
Hello,
Just had another crash, with a full screen app. Tried all the
emergency recovery techniques mentioned earlier, but nothing seemed to
restore a console or screen I could work with. Did a reboot. :-(
For several of the emergency things, it seemed as though linux was
still working (I could mo
30 matches
Mail list logo
