This is a discussion on 'Emacs' and 'startx' start so slowly. within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> =====Env===== Slackware 12.0 2.6.21.5-smp KDE 3.5.7 Emacs 22.1.1 ============ I use the router to connect the Internet, so I ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| =====Env===== Slackware 12.0 2.6.21.5-smp KDE 3.5.7 Emacs 22.1.1 ============ I use the router to connect the Internet, so I can just plug the rj45 line to my laptop. I found that if I didn't connect the Internet, it took so much time to start the Emacs(about 1 minute!) and startx(about 20 seconds to see the KDE startup interface). But they started in few seconds when I'm online. I'm confused about that. Someone told me to add 'timeout=1' into the /etc/resolv.conf, but that didn't make better. They two still start so slowly. What's up? |
| |||
| vvoody wrote: > =====Env===== > Slackware 12.0 > 2.6.21.5-smp > KDE 3.5.7 > Emacs 22.1.1 > ============ > > I use the router to connect the Internet, so I can just plug the rj45 > line to my laptop. I found that if I didn't connect the Internet, it > took so much time to start the Emacs(about 1 minute!) and startx(about > 20 seconds to see the KDE startup interface). > > But they started in few seconds when I'm online. I'm confused about > that. Someone told me to add 'timeout=1' into the /etc/resolv.conf, > but that didn't make better. They two still start so slowly. > > What's up? what's your machine's hostname? do you have your hostname entry as well as localhost in /etc/hosts? |
| |||
| > what's your machine's hostname? > do you have your hostname entry as well as localhost in /etc/hosts? vvoody@vvhostname:~$ cat /etc/hosts # # hosts This file describes a number of hostname-to-address # For loopbacking. 127.0.0.1 localhost 192.168.2.101 slackware12.0 slackware12.0 #192.168.2.101 vvhostname.vvdomain vvhostname # End of hosts. ----------------------- vvoody@vvhostname:~$ hostname vvhostname ----------------------- I should use '192.168.2.101 vvhostname.vvdomain vvhostname' ? |
| |||
| vvoody wrote : > # For loopbacking. > 127.0.0.1 localhost > 192.168.2.101 slackware12.0 slackware12.0 Try this instead: # For loopbacking. 127.0.0.1 localhost 127.0.0.1 slackware12.invalid slackware12 -- Thomas O. This area is designed to become quite warm during normal operation. |
| |||
| vvoody wrote : > # For loopbacking. > 127.0.0.1 localhost > 192.168.2.101 vvhostname.vvdomain vvhostname Then try: 127.0.0.1 localhost 127.0.0.1 vvhostname.vvdomain vvhostname This line: 192.168.2.101 vvhostname.vvdomain vvhostname should be used on other computers at your network so they can contact your computer as "vvhostname" instead of 192.168.2.101. -- Thomas O. This area is designed to become quite warm during normal operation. |
| |||
| On Nov 17, 8:16 pm, Thomas Overgaard <tho...@post2.tele.dk> wrote: > vvoody wrote : > > > # For loopbacking. > > 127.0.0.1 localhost > > 192.168.2.101 vvhostname.vvdomain vvhostname > > Then try: > 127.0.0.1 localhost > 127.0.0.1 vvhostname.vvdomain vvhostname > > This line: > 192.168.2.101 vvhostname.vvdomain vvhostname > should be used on other computers at your network so they can contact > your computer as "vvhostname" instead of 192.168.2.101. That's it. Regards |
| |||
| Thomas Overgaard wrote: > Then try: > 127.0.0.1 localhost > 127.0.0.1 vvhostname.vvdomain vvhostname > > This line: > 192.168.2.101 vvhostname.vvdomain vvhostname should be used on > other computers at your network so they can contact your computer as > "vvhostname" instead of 192.168.2.101. I've similar settings on all of my Slackware boxes. However, if I SSH into any of them with the DSL shut off, the username prompt shows up immediately, but takes anywhere from five to ten seconds for the password prompt to come. -- Ayaz Ahmed Khan |
| |||
| Ayaz Ahmed Khan wrote: > I've similar settings on all of my Slackware boxes. However, if I SSH > into any of them with the DSL shut off, the username prompt shows up > immediately, but takes anywhere from five to ten seconds for the password > prompt to come. have you tried 'ssh -v -v -v' to see what is happening? perhaps it doesn't have to do anything with resolv.conf at all... -- Joost Kremers joostkremers@yahoo.com Selbst in die Unterwelt dringt durch Spalten Licht EN:SiS(9) |