10:55 | ralix | morning |
14:00 | Wizzup_ | Time to revive Gentoo on Cubox soon :) |
14:00 | ralix | use arch, its better ;) |
14:01 | Wizzup_ | in breaking down and bloating my system |
14:05 | mhoney_work | use debian, its best |
14:07 | Wizzup_ | debian is okay too, in some cases |
14:08 | Wizzup_ | but any distro that uses systemd will be avoided by me |
14:16 | _rmk_ | a very good plan. |
14:17 | _rmk_ | systemd uses dbus for communication, which times out if your system is under heavy load, which means you can't ask systemd to take stuff down or restart it. |
14:17 | _rmk_ | your only options are to delve into the systemd scripts to find out what command actually needs to be run, or to use pkill to recover from the situation, or pull the power plug |
15:14 | Coolgeek | or use windows, that is better |
15:14 | Coolgee | 15:14 * Coolgeek hides |
15:19 | dv_ | _rmk_: this problem still persists? |
15:19 | dv_ | I thought it was fixed |
15:48 | _rmk_ | dv_: F16's systemd suffers that problem... yes, might be over a year old but online upgrades past F16 are apparantly impossible to do |
15:48 | _rmk_ | and doing offline upgrades on a machine located 300+ miles from anyone is... |
15:51 | dv_ | I use arch on my desktop, never had these issues even under very heavy load |
15:52 | dv_ | so I hope it was fixed :) |
15:59 | _rmk_ | heavy load I define as a load average of 130 |
15:59 | _rmk_ | with lots of processes sitting in iowait |
16:43 | Kiranos_ | _rmk_: that indeed is heavy load:) |
16:45 | dv_ | those hard disks must be crying |