William Case wrote: > Hi; > On Fri, 2010-01-15 at 18:29 +0800, Ed Greshko wrote: > >> William Case wrote: >> >>> Hi; >>> > > >> If you disable vncserver from starting at boot time, does the boot time >> decrease? >> > > It decreases somewhat -- but the boot log is still showing problems. > > %G Welcome to [0;34mFedora[0;39m > Press 'I' to enter interactive startup. > Starting udev: %G[60G[[0;32m OK [0;39m] > Setting hostname CASE: [60G[[0;32m OK [0;39m] > mdadm: No arrays found in config file or automatically > Setting up Logical Volume Management: [60G[[0;32m OK [0;39m] > Checking filesystems > /dev/sdb2: clean, 232303/1272960 files, 1955001/5082564 blocks > /dev/sdb1: clean, 41/64256 files, 48232/257008 blocks > /dev/sdb3: clean, 57500/28164096 files, 2194276/112639747 blocks > [60G[[0;32m OK [0;39m] > Remounting root filesystem in read-write mode: [60G[[0;32m > OK [0;39m] > Mounting local filesystems: [60G[[0;32m OK [0;39m] > Enabling local filesystem quotas: [60G[[0;32m OK [0;39m] > Enabling /etc/fstab swaps: [60G[[0;32m OK [0;39m] > Entering non-interactive startup > Applying Intel CPU microcode update: WARNING: Deprecated config > file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. > Checking kmods exist for 2.6.31.9-174.fc12.x86_64[60G[[0;32m > OK [0;39m] > WARNING: Deprecated config file /etc/modprobe.conf, all config files > belong into /etc/modprobe.d/. > Enabling ondemand cpu frequency scaling: [60G[[0;32m OK [0;39m] > ip6tables: Applying firewall rules: WARNING: Deprecated config > file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. > [60G[[0;32m OK [0;39m] > ip6tables: Loading additional modules: nf_conntrack_netbios_ns > [60G[[0;32m OK [0;39m] > iptables: Applying firewall rules: [60G[[0;32m OK [0;39m] > iptables: Loading additional modules: nf_conntrack_netbios_ns > [60G[[0;32m OK [0;39m] > Checking for module nvidia.ko: [60G[[0;32m OK [0;39m] > Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 520: 979 > Segmentation fault "$@" > [60G[[0;31mFAILED[0;39m] > Starting portreserve: [60G[[0;32m OK [0;39m] > Starting system logger: [60G[[0;32m OK [0;39m] > Starting irqbalance: [60G[[0;32m OK [0;39m] > Starting rpcbind: [60G[[0;32m OK [0;39m] > Starting system message bus: [60G[[0;32m OK [0;39m] > Starting Avahi daemon... [60G[[0;32m OK [0;39m] > Starting NFS statd: [60G[[0;32m OK [0;39m] > Starting RPC idmapd: WARNING: Deprecated config file /etc/modprobe.conf, > all config files belong into /etc/modprobe.d/. > WARNING: Deprecated config file /etc/modprobe.conf, all config files > belong into /etc/modprobe.d/. > [60G[[0;32m OK [0;39m] > Starting cups: [60G[[0;32m OK [0;39m] > Starting acpi daemon: [60G[[0;32m OK [0;39m] > Starting HAL daemon: [60G[[0;32m OK [0;39m] > Starting PC/SC smart card daemon (pcscd): [60G[[0;32m OK [0;39m] > Setting network parameters... [60G[[0;32m OK [0;39m] > Starting NetworkManager daemon: [60G[[0;32m OK [0;39m] > Starting sshd: [60G[[0;32m OK [0;39m] > Starting xinetd: [60G[[0;32m OK [0;39m] > Starting sendmail: [60G[[0;32m OK [0;39m] > Starting sm-client: [60G[[0;32m OK [0;39m] > Starting abrt daemon: [60G[[0;32m OK [0;39m] > Starting crond: [60G[[0;32m OK [0;39m] > [60G[[0;32m OK [0;39m] > > Enabling monthly Smolt checkin: [60G[[0;32m OK [0;39m] > Starting atd: [60G[[0;32m OK [0;39m] > [60G[[0;32m OK [0;39m] > > > >> Are you actually able to start the vncserver after the system starts? >> >> > ]# service vncserver status > Xvnc (pid 3327) is running.. > I take it from this that you didn't change the configuration and vncserver started at boot. This time without any errors in the log > >> At first blush it sure seems as if you have a problem in your >> /etc/sysconfig/vncservers file. >> > > Commented out the two lines in /etc/sysconfig/vncservers. I am not to > worried about the config file per se. I was just setting up Tigervnc > and had applied the exact advice I got for configuration. I was > expecting further tweaking. > > But where did this modprobe.conf stuff come from ?? > > Why is idmap.d giving me problems ?? > That isn't a big deal. First, I don't think there is any complaint about RPC idmapd. It is just that a "return" doesn't follow the start message being sent to the log. Second, the message about modprobe.conf is just a warning. It doesn't take any additional time for the boot process. If you want to get rid of the warning you can check the contents of modprobe.conf and if there is anything there you can move it to an appropriately named file in /etc/modeprobe.d. > If interested, I had earlier problems with my network. See bugs > https://bugzilla.redhat.com/show_bug.cgi?id=552024 and, > https://bugzilla.redhat.com/show_bug.cgi?id=555598 > > Somehow, on my LAN, my remote machine's address got changed > (re-mapped ??) from ...1.7 to ...1.2. I did nothing intentional to > cause this. > > If I get the chance I'll take a look at that. FWIW, you can always hit "escape" at the start of the boot process and watch all the messages. When/if the process stalls you'll know where it is happening. -- The propriety of some persons seems to consist in having improper thoughts about their neighbours. -- F.H. Bradley
Attachment:
signature.asc
Description: OpenPGP digital signature
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
