On Fri, 02 Dec 2005 20:37:10 +0200, Adriaan de Groot <[EMAIL PROTECTED]> wrote:
On Friday 02 December 2005 15:49, Android wrote:
crash/reboot
Could anyone comment this situation?
Well, that's the entirely unrelated 'running gdb on any kde application
under
amd64 causes a total crash and reboot' problem. I believe it was taken
up on
the amd64 mailing list. It happens with ports, home-compiled, 5.4 and
6.0,
all kinds of amd64 machines.
Still looks like some kind of network timeout to me. Or do you have 15000
fancy fonts installed?
Hello, Adriaan.
Thank you for answer!
No, I have a standart font set (xorg + some cyrillic)
This weekend I've tackled these mysterious timeouts in real earnest, and
using patience,
google and luck I've found a matter.
Here's the cause of network timeouts while KDE starting:
net.inet.tcp.blackhole=2 in /etc/sysctl.conf
Default value is "0", I've set this value equal "2" securing my system.
Setting
net.inet.tcp.blackhole=0 solves the problems (in my system) :
(Very) Slow KDE (and kde-apps) startup
Slow gnome startup
Samba (smbd) startup waits
Mozilla Firefox freeze when using Save Link As
Hope, this recommendation (testing net.inet.tcp.blackhole) could help to
save time
solving the similar problems.
I couldn't say I like value "0", but it's always necessary to compromise
between
security and usability.
It's left to analyze the cause of crash...
--
WBR Android Andrew [:]
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd
