Re: Trans.: Re: gnome long startup
On Tuesday 06 April 2004 02:57, Antoine Jacoutot wrote: Yes, the blackholes have been known to cause problems with GNOME startup. First make sure you can do: Indeed, blackholes were the problem... It works now. Is there a way to have blackholes enabled and make tthis work anyway ? Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
gnome long startup
Hi :) I have problems when starting gnome if I enable the esd sound server, it takes forever for gnome to launch itself. In my logs, I can see a connexion attempt to 127.0.0.1:16001. Anyone knows how I could speed up gnome start ? Thanks. Regards. -- Antoine Jacoutot [EMAIL PROTECTED] http://www.lphp.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome long startup
Antoine Jacoutot wrote: I have problems when starting gnome if I enable the esd sound server, it takes forever for gnome to launch itself. In my logs, I can see a connexion attempt to 127.0.0.1:16001. Anyone knows how I could speed up gnome start ? Hi, do you have a firewall, and if so, are you sure it does not block that connection? The same goes for tcpwrappers, so check /etc/hosts.allow and /etc/hosts.deny. I third thing that comes to my mind is /etc/hosts? Is it set up properly, e.g. ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain 10.0.0.1 myhostmyhost.my.domain Does the problem go away, if you create a test user and try to log into Gnome? If so, then some of your ~/.* configuration files/directories are hosed, and you should be able to fix the problem by moving them away. If all of the above fails, please provide more information, e.g. FreeBSD version, list of installed packages (ls /var/db/pkg), the login manager you use. An excerpt from the log you mentioned might also be useful. HTH, Simon signature.asc Description: Digital signature
Re: gnome long startup
On Monday 05 April 2004 20:15, Simon Barner wrote: do you have a firewall, and if so, are you sure it does not block that connection? Nope, this is a test station within my LAN, there's no firewall on it. The same goes for tcpwrappers, so check /etc/hosts.allow and /etc/hosts.deny. I never touched those files, so I don't think there' re the problem. I third thing that comes to my mind is /etc/hosts? Is it set up properly, e.g. Yes, and there's also a DNS server on the LAN. Does the problem go away, if you create a test user and try to log into Gnome? If so, then some of your ~/.* configuration files/directories are hosed, and you should be able to fix the problem by moving them away. No, the problem still occurs. If all of the above fails, please provide more information, e.g. FreeBSD version, list of installed packages (ls /var/db/pkg), the login manager you use. An excerpt from the log you mentioned might also be useful. Well, I use FreeBSD-5.2.1-p1 and my login manager is gdm2. But even if I start gnome from console (using .xinitrc), I get the same problem. Disabling esd in gnome control center make the problem disapear. I have no log whatsover except what I said about 127.0.0.1:16001 which appeared when I set log_in_vain in rc.conf. I do have these in my sysctl.conf, do you think this could cause problem: security.bsd.see_other_uids=0 net.inet.tcp.blackhole=2 net.inet.udp.blackhole=1 net.inet.tcp.sendspace=65535 vfs.usermount=1 kern.randompid=2 Thanks. Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome long startup
On Mon, 2004-04-05 at 15:21, Antoine Jacoutot wrote: On Monday 05 April 2004 20:15, Simon Barner wrote: do you have a firewall, and if so, are you sure it does not block that connection? Nope, this is a test station within my LAN, there's no firewall on it. The same goes for tcpwrappers, so check /etc/hosts.allow and /etc/hosts.deny. I never touched those files, so I don't think there' re the problem. I third thing that comes to my mind is /etc/hosts? Is it set up properly, e.g. Yes, and there's also a DNS server on the LAN. Does the problem go away, if you create a test user and try to log into Gnome? If so, then some of your ~/.* configuration files/directories are hosed, and you should be able to fix the problem by moving them away. No, the problem still occurs. If all of the above fails, please provide more information, e.g. FreeBSD version, list of installed packages (ls /var/db/pkg), the login manager you use. An excerpt from the log you mentioned might also be useful. Well, I use FreeBSD-5.2.1-p1 and my login manager is gdm2. But even if I start gnome from console (using .xinitrc), I get the same problem. Disabling esd in gnome control center make the problem disapear. I have no log whatsover except what I said about 127.0.0.1:16001 which appeared when I set log_in_vain in rc.conf. I do have these in my sysctl.conf, do you think this could cause problem: security.bsd.see_other_uids=0 net.inet.tcp.blackhole=2 net.inet.udp.blackhole=1 net.inet.tcp.sendspace=65535 vfs.usermount=1 kern.randompid=2 Yes, the blackholes have been known to cause problems with GNOME startup. First make sure you can do: ping `hostname` Then try disabling the blackholes, and see if that helps. Joe Thanks. Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
