Re: Re: why desktop apps are able to kill my freebsd box?
On Tue, Jul 5, 2011 at 2:42 AM, Timo wrote: >> Why a faulty desktop application run as unprivileged user is able to >> crash my system? >> >> I mean, I know programs have bugs and sometimes they lead to crashes. >> I'm fine with that. But why a crashing program (for example firefox or >> banshee) is able to kill the whole system? >> >> And by 'crash' or 'kill' i mean that for whatever reason the system is >> frozen and doesn't reply to anything but a hard reset. Can you still log in via ssh from another box? Or at least, can you ping the "frozen" box from the outside? Usually, a frozen system isn't really frozen, it's just Xorg which is. And that's often related to buggy graphics drivers. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: why desktop apps are able to kill my freebsd box?
Which video card do you use? -- View this message in context: http://freebsd.1045724.n5.nabble.com/why-desktop-apps-are-able-to-kill-my-freebsd-box-tp4541545p4552169.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: why desktop apps are able to kill my freebsd box?
Who decided to run any privileged application, in terms of doing what you didn't want it to? Did you at all try to implement anything you were not sure of? Or what did you ask again? What do you want to employ in the first place, and what security risks are negotiable? (firefox/freezings? try to reseat every piece of hardware until no freeze is found, including cpu, then complain about software) On 2011-07-01 11:00, Michael wrote: Why a faulty desktop application run as unprivileged user is able to crash my system? I mean, I know programs have bugs and sometimes they lead to crashes. I'm fine with that. But why a crashing program (for example firefox or banshee) is able to kill the whole system? And by 'crash' or 'kill' i mean that for whatever reason the system is frozen and doesn't reply to anything but a hard reset. It just doesn't make much sense so I'm assuming that I must be doing something wrong. Where and what kind of restrictions should I set up to make sure that a buggy unprivileged program cannot freeze my box? Thank you in advance. Michael. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Fwd: Re: why desktop apps are able to kill my freebsd box?
In other words, I don's think, It's about software at all In my opinion Original Message Subject: Re: why desktop apps are able to kill my freebsd box? Date: Tue, 05 Jul 2011 02:29:11 +0200 From: Timo Reply-To: timo.bsdm...@gmail.com To: freebsd-questions@freebsd.org Who decided to run any privileged application, in terms of doing what you didn't want it to? Did you at all try to implement anything you were not sure of? Or what did you ask again? What do you want to employ in the first place, and what security risks are negotiable? (firefox/freezings? try to reseat every piece of hardware until no freeze is found, including cpu, then complain about software) On 2011-07-01 11:00, Michael wrote: Why a faulty desktop application run as unprivileged user is able to crash my system? I mean, I know programs have bugs and sometimes they lead to crashes. I'm fine with that. But why a crashing program (for example firefox or banshee) is able to kill the whole system? And by 'crash' or 'kill' i mean that for whatever reason the system is frozen and doesn't reply to anything but a hard reset. It just doesn't make much sense so I'm assuming that I must be doing something wrong. Where and what kind of restrictions should I set up to make sure that a buggy unprivileged program cannot freeze my box? Thank you in advance. Michael. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: why desktop apps are able to kill my freebsd box?
On Fri, 01 Jul 2011 10:00:59 +0100, Michael wrote: > Why a faulty desktop application run as unprivileged user is able to > crash my system? > > I mean, I know programs have bugs and sometimes they lead to crashes. > I'm fine with that. But why a crashing program (for example firefox or > banshee) is able to kill the whole system? > > And by 'crash' or 'kill' i mean that for whatever reason the system is > frozen and doesn't reply to anything but a hard reset. Do you have anything in /var/log/messages or maybe if you start the suspicious programs from a terminal to see their output? I've been using FreeBSD since 4.0 as a desktop, and I have never encountered problems as you describe. However, fiddling with USB stuff sometimes _can_ lead to system problems (even crash and reboot), but there are always messages that indicate some problem. > It just doesn't make much sense so I'm assuming that I must be doing > something wrong. It shouldn't be POSSIBLE, no matter which kind of userspace program you run, to do something _that_ wrong that the system is affected in that way. > Where and what kind of restrictions should I set up to > make sure that a buggy unprivileged program cannot freeze my box? You should try to find out what _exactly_ is causing the freeze, obtaining logs and messages (and maybe also run top, systat or other means of system monitoring in parallel) to see what does actually happen when the problem occurs. Options would be to separate programs in jails, or even try to run them on a VM (e. g. VirtualBox running a FreeBSD install with that program). Also make absolutely sure your hardware is okay, e. g. use memtest to check the RAM (often an indicator for unstable system behaviour). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
why desktop apps are able to kill my freebsd box?
Why a faulty desktop application run as unprivileged user is able to crash my system? I mean, I know programs have bugs and sometimes they lead to crashes. I'm fine with that. But why a crashing program (for example firefox or banshee) is able to kill the whole system? And by 'crash' or 'kill' i mean that for whatever reason the system is frozen and doesn't reply to anything but a hard reset. It just doesn't make much sense so I'm assuming that I must be doing something wrong. Where and what kind of restrictions should I set up to make sure that a buggy unprivileged program cannot freeze my box? Thank you in advance. Michael. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
