Results 1 to 7 of 7

Thread: Boot process log

  1. #1

    Default Boot process log

    I just wanna make sure my boot up process is nominal. Here is the log from /var/log/messages from start up all the way to after login:

    Code:
    Nov 30 15:49:37 sda-linux kernel: imklog 5.6.5, log source = /proc/kmsg started.
    Nov 30 15:49:37 sda-linux rsyslogd: [origin software="rsyslogd" swVersion="5.6.5" x-pid="1186" x-info="http://www.rsyslog.com"] start
    Nov 30 15:49:37 sda-linux kernel: [    5.958983] type=1400 audit(1322660975.852:2): apparmor="STATUS" operation="profile_load" name="/bin/ping" pid=973 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    5.980212] type=1400 audit(1322660975.874:3): apparmor="STATUS" operation="profile_load" name="/sbin/klogd" pid=978 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.028277] type=1400 audit(1322660975.922:4): apparmor="STATUS" operation="profile_load" name="/sbin/syslog-ng" pid=982 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.073567] type=1400 audit(1322660975.967:5): apparmor="STATUS" operation="profile_load" name="/sbin/syslogd" pid=986 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.254921] type=1400 audit(1322660976.149:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/apache2/mpm-prefork/apache2" pid=991 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.254954] type=1400 audit(1322660976.149:7): apparmor="STATUS" operation="profile_load" name="/usr/lib/apache2/mpm-prefork/apache2//DEFAULT_URI" pid=991 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.254977] type=1400 audit(1322660976.149:8): apparmor="STATUS" operation="profile_load" name="/usr/lib/apache2/mpm-prefork/apache2//HANDLING_UNTRUSTED_INPUT" pid=991 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.255014] type=1400 audit(1322660976.149:9): apparmor="STATUS" operation="profile_load" name="/usr/lib/apache2/mpm-prefork/apache2//phpsysinfo" pid=991 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.301356] type=1400 audit(1322660976.196:10): apparmor="STATUS" operation="profile_load" name="/usr/lib/dovecot/deliver" pid=995 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.349806] type=1400 audit(1322660976.244:11): apparmor="STATUS" operation="profile_load" name="/usr/lib/dovecot/dovecot-auth" pid=999 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    6.396587] type=1400 audit(1322660976.291:12): apparmor="STATUS" operation="profile_load" name="/usr/lib/dovecot/imap" pid=1003 comm="apparmor_parser"
    Nov 30 15:49:37 sda-linux kernel: [    7.098270] HDA Intel 0000:01:00.1: PCI INT B disabled
    Nov 30 15:49:37 sda-linux kernel: [    7.358975] BIOS EDD facility v0.16 2004-Jun-25, 3 devices found
    Nov 30 15:49:37 sda-linux kdm_config[1348]: Multiple occurrences of section [General] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
    Nov 30 15:49:37 sda-linux kdm_config[1348]: Multiple occurrences of section [Xdmcp] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
    Nov 30 15:49:37 sda-linux kdm_config[1348]: Multiple occurrences of section [X-*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
    Nov 30 15:49:37 sda-linux kdm_config[1348]: Multiple occurrences of section [X-*-Greeter] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
    Nov 30 15:49:37 sda-linux kdm_config[1348]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc
    Nov 30 15:49:37 sda-linux kdm_config[1348]: Multiple occurrences of section [X-:*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
    Nov 30 15:49:37 sda-linux kdm_config[1348]: Multiple occurrences of section [X-:0-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
    Nov 30 15:49:37 sda-linux ifup:     lo        
    Nov 30 15:49:37 sda-linux ifup:     lo        
    Nov 30 15:49:37 sda-linux ifup: IP address: 127.0.0.1/8  
    Nov 30 15:49:37 sda-linux ifup:  
    Nov 30 15:49:37 sda-linux ifup:               
    Nov 30 15:49:37 sda-linux ifup: IP address: 127.0.0.2/8  
    Nov 30 15:49:37 sda-linux ifup:  
    Nov 30 15:49:38 sda-linux ifup:     eth1      device: Realtek Semiconductor Co., Ltd. RTL8111/8168B
    Nov 30 15:49:38 sda-linux ifup:     eth1      Startmode is 'manual'
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Found user 'avahi' (UID 104) and group 'avahi' (GID 106).
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Successfully dropped root privileges.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: avahi-daemon 0.6.28 starting up.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Loading service file /etc/avahi/services/sftp-ssh.service.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Loading service file /etc/avahi/services/ssh.service.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Loading service file /etc/avahi/services/udisks.service.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Network interface enumeration completed.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Registering HINFO record with values 'X86_64'/'LINUX'.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Server startup complete. Host name is sda-linux.local. Local service cookie is 1694101352.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Service "sda-linux" (/etc/avahi/services/udisks.service) successfully established.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Service "sda-linux" (/etc/avahi/services/ssh.service) successfully established.
    Nov 30 15:49:38 sda-linux avahi-daemon[1669]: Service "sda-linux" (/etc/avahi/services/sftp-ssh.service) successfully established.
    Nov 30 15:49:38 sda-linux kernel: Kernel logging (proc) stopped.
    Nov 30 15:49:38 sda-linux rsyslogd: [origin software="rsyslogd" swVersion="5.6.5" x-pid="1186" x-info="http://www.rsyslog.com"] exiting on signal 15.
    Nov 30 15:49:38 sda-linux kernel: imklog 5.6.5, log source = /proc/kmsg started.
    Nov 30 15:49:38 sda-linux rsyslogd: [origin software="rsyslogd" swVersion="5.6.5" x-pid="1804" x-info="http://www.rsyslog.com"] start
    Nov 30 15:49:38 sda-linux auditd[1892]: Started dispatcher: /sbin/audispd pid: 1894
    Nov 30 15:49:38 sda-linux audispd: priority_boost_parser called with: 4
    Nov 30 15:49:38 sda-linux audispd: max_restarts_parser called with: 10
    Nov 30 15:49:38 sda-linux audispd: No plugins found, exiting
    Nov 30 15:49:38 sda-linux mcelog: failed to prefill DIMM database from DMI data
    Nov 30 15:49:38 sda-linux acpid: 1 client rule loaded
    Nov 30 15:49:38 sda-linux kernel: [    8.792974] vboxdrv: Found 8 processor cores.
    Nov 30 15:49:38 sda-linux kernel: [    8.793037] VBoxDrv: dbg - g_abExecMemory=ffffffffa0fd0a60
    Nov 30 15:49:38 sda-linux kernel: [    8.793087] vboxdrv: fAsync=0 offMin=0x1df offMax=0x2213
    Nov 30 15:49:38 sda-linux kernel: [    8.793123] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    Nov 30 15:49:38 sda-linux kernel: [    8.793125] vboxdrv: Successfully loaded version 4.1.6 (interface 0x00190000).
    Nov 30 15:49:38 sda-linux ifup:     wlan0     
    Nov 30 15:49:38 sda-linux ifup-wireless:     wlan0     warning: WPA configured, but is untested
    Nov 30 15:49:38 sda-linux ifup-wireless:     wlan0     warning: with this device
    Nov 30 15:49:38 sda-linux ifup-wireless:     wlan0     starting wpa_supplicant
    Nov 30 15:49:38 sda-linux auditd[1892]: Init complete, auditd 2.0.5 listening for events (startup state disable)
    Nov 30 15:49:38 sda-linux kernel: [    8.999948] vboxpci: IOMMU not found (not registered)
    Nov 30 15:49:38 sda-linux kernel: [    9.027420] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 30 15:49:38 sda-linux kernel: [    9.035713] NET: Registered protocol family 17
    Nov 30 15:49:38 sda-linux /usr/sbin/cron[2240]: (CRON) STARTUP (1.4.7)
    Nov 30 15:49:38 sda-linux /usr/sbin/cron[2240]: (CRON) bad username (/etc/cron.d/smolt)
    Nov 30 15:49:38 sda-linux /usr/sbin/cron[2240]: (CRON) INFO (running with inotify support)
    Nov 30 15:49:38 sda-linux smartd[2242]: smartd 5.40 2010-10-16 r3189 [x86_64-unknown-linux-gnu] (SUSE RPM)#012Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net#012
    Nov 30 15:49:38 sda-linux smartd[2242]: Opened configuration file /etc/smartd.conf
    Nov 30 15:49:38 sda-linux smartd[2242]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
    Nov 30 15:49:38 sda-linux smartd[2242]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
    Nov 30 15:49:38 sda-linux smartd[2242]: Device: /dev/sda, type changed from 'scsi' to 'sat'
    Nov 30 15:49:38 sda-linux smartd[2242]: Device: /dev/sda [SAT], opened
    Nov 30 15:49:38 sda-linux smartd[2242]: Device: /dev/sda [SAT], not found in smartd database.
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sda [SAT], can't monitor Current Pending Sector count - no Attribute 197
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sda [SAT], can't monitor Offline Uncorrectable Sector count - no Attribute 198
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sda [SAT], Read Summary SMART Error Log failed
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sda [SAT], no Summary SMART Error Log, ignoring -l error
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.INTEL_SSDSC2MH120A2-LNEL127200CT120CGN.ata.state
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdb [SAT], opened
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdb [SAT], found in smartd database.
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD6400AAKS_22A7B0-WD_WMASY1314973.ata.state
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdc, type changed from 'scsi' to 'sat'
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdc [SAT], opened
    Nov 30 15:49:39 sda-linux smartd[2242]: Device: /dev/sdc [SAT], not found in smartd database.
    Nov 30 15:49:39 sda-linux ifup-dhcp:     wlan0     Starting DHCP4 client
    Nov 30 15:49:39 sda-linux dhcpcd[2282]: wlan0: dhcpcd 3.2.3 starting
    Nov 30 15:49:39 sda-linux dhcpcd[2282]: wlan0: hardware address = d8:5d:4c:84:1f:3f
    Nov 30 15:49:39 sda-linux dhcpcd[2282]: wlan0: broadcasting for a lease
    Nov 30 15:49:39 sda-linux ifup-dhcp: . 
    Nov 30 15:49:40 sda-linux kernel: [   10.435312] wlan0: authenticate with 74:ea:3a:e4:3c:ea (try 1)
    Nov 30 15:49:40 sda-linux kernel: [   10.437077] wlan0: authenticated
    Nov 30 15:49:40 sda-linux kernel: [   10.631351] wlan0: associate with 74:ea:3a:e4:3c:ea (try 1)
    Nov 30 15:49:40 sda-linux kernel: [   10.635251] wlan0: RX AssocResp from 74:ea:3a:e4:3c:ea (capab=0x431 status=0 aid=2)
    Nov 30 15:49:40 sda-linux kernel: [   10.635254] wlan0: associated
    Nov 30 15:49:40 sda-linux kernel: [   10.699992] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 30 15:49:40 sda-linux smartd[2242]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list.
    Nov 30 15:49:40 sda-linux smartd[2242]: Device: /dev/sdc [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_HD204UI-S2H7J90B110667.ata.state
    Nov 30 15:49:40 sda-linux smartd[2242]: Monitoring 3 ATA and 0 SCSI devices
    Nov 30 15:49:40 sda-linux smartd[2242]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 115 to 126
    Nov 30 15:49:41 sda-linux ifup-dhcp: . 
    Nov 30 15:49:41 sda-linux smartd[2242]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.INTEL_SSDSC2MH120A2-LNEL127200CT120CGN.ata.state
    Nov 30 15:49:41 sda-linux smartd[2242]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD6400AAKS_22A7B0-WD_WMASY1314973.ata.state
    Nov 30 15:49:41 sda-linux smartd[2242]: Device: /dev/sdc [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_HD204UI-S2H7J90B110667.ata.state
    Nov 30 15:49:41 sda-linux smartd[2419]: smartd has fork()ed into background mode. New PID=2419.
    Nov 30 15:49:43 sda-linux dhcpcd[2282]: wlan0: offered 192.168.1.101 from 192.168.1.1
    Nov 30 15:49:43 sda-linux dhcpcd[2282]: wlan0: checking 192.168.1.101 is available on attached networks
    Nov 30 15:49:43 sda-linux ifup-dhcp: . 
    Nov 30 15:49:44 sda-linux dhcpcd[2282]: wlan0: leased 192.168.1.101 for infinity
    Nov 30 15:49:44 sda-linux dhcpcd[2282]: wlan0: adding IP address 192.168.1.101/24
    Nov 30 15:49:44 sda-linux dhcpcd[2282]: wlan0: adding default route via 192.168.1.1 metric 0
    Nov 30 15:49:44 sda-linux avahi-daemon[1669]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.101.
    Nov 30 15:49:44 sda-linux avahi-daemon[1669]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 30 15:49:44 sda-linux avahi-daemon[1669]: Registering new address record for 192.168.1.101 on wlan0.IPv4.
    Nov 30 15:49:44 sda-linux ifdown:     wlan0     
    Nov 30 15:49:44 sda-linux dhcpcd[2282]: wlan0: Failed to lookup hostname via DNS: Name or service not known
    Nov 30 15:49:44 sda-linux ifup:     wlan0     
    Nov 30 15:49:44 sda-linux dhcpcd[2282]: wlan0: exiting
    Nov 30 15:49:44 sda-linux ifup-dhcp:  
    Nov 30 15:49:44 sda-linux ifup-dhcp:     wlan0     IP address: 192.168.1.101/24
    Nov 30 15:49:44 sda-linux kernel: [   14.999273] bootsplash: status on console 0 changed to on
    Nov 30 15:49:49 sda-linux polkitd[3002]: started daemon version 0.99 using authority implementation `local' version `0.99'
    Nov 30 15:49:49 sda-linux checkproc: checkproc: can not get session id for process 4142!
    Nov 30 15:49:49 sda-linux kernel: [   19.821048] start_kdeinit (3150): /proc/3150/oom_adj is deprecated, please use /proc/3150/oom_score_adj instead.
    Nov 30 15:49:50 sda-linux acpid: 1 client rule loaded
    Nov 30 15:49:50 sda-linux kernel: [   20.840425] EXT4-fs (sda3): re-mounted. Opts: acl,discard,commit=0
    Nov 30 15:49:50 sda-linux kernel: [   20.842019] EXT4-fs (sda1): re-mounted. Opts: acl,discard,commit=0
    Nov 30 15:49:50 sda-linux kernel: [   20.843144] EXT4-fs (sdc1): re-mounted. Opts: barrier=1,data=ordered,commit=0
    Nov 30 15:49:55 sda-linux kernel: [   25.079754] fuse init (API version 7.15)
    Nov 30 15:49:55 sda-linux polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.28 [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    Nov 30 15:56:53 sda-linux kernel: [  442.233652] r8169 0000:0b:00.0: eth1: link down
    Nov 30 15:56:53 sda-linux kernel: [  442.234349] ADDRCONF(NETDEV_UP): eth1: link is not ready
    This is with opensuse 11.4. I'll supply any other log or config file contents if needed.
    Can anyone see something wrong?
    Thanks!

  2. #2
    Join Date
    Jun 2008
    Location
    Norman, OK
    Posts
    209

    Default Re: Boot process log

    Are you experiencing any problems?

    The only thing that I can see is the error message about not being able to lookup your hostname via DNS, but if you have your hostname set manually in /etc/hosts then you can ignore that message in the system log .. maybe your DNS server doesn't use Dynamic hostname updating or something.
    Main Machine: Dell Precision M6600 running openSUSE Leap 16
    Server: Dell PowerEdge SC1430 running SLES 15

  3. #3

    Default Re: Boot process log

    Thanks.
    I had some problems in the past but really think I am past them now. Right now the system is stable and working just fine.
    I have different thread about the wireless "thingy" and probably something will come up there. It doesn't bother me at all.
    Anything else noteworthy? I'm pretty sure my hard drive temperature isn't 125 degrees, but that should be some SMART interpreting error.
    Is this remounting for my drives normal? I have the following in fstab:
    Code:
    /dev/disk/by-id/ata-INTEL_SSDSC2MH120A2_LNEL127200CT120CGN-part3 /                    ext4       acl,noatime,discard   1 1
    /dev/disk/by-id/ata-INTEL_SSDSC2MH120A2_LNEL127200CT120CGN-part1 /boot                ext4       acl,noatime,discard   1 2
    /dev/disk/by-id/ata-INTEL_SSDSC2MH120A2_LNEL127200CT120CGN-part2 swap                 swap       defaults              0 0
    proc                 /proc                proc       defaults              0 0
    sysfs                /sys                 sysfs      noauto                0 0
    debugfs              /sys/kernel/debug    debugfs    noauto                0 0
    usbfs                /proc/bus/usb        usbfs      noauto                0 0
    devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
    /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2H7J90B110667-part1 /home/saty/storage/  ext4       defaults              1 2
    Also there are some "Multiple occurrences of section ..... Consider merging them." entries. Anything about them?

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Boot process log

    On 2011-11-30 18:36, ssaatt wrote:
    > Can anyone see something wrong?


    I'm not going to look. First you tell me if you are experiencing problems
    and what are the symptoms, and then I may have a long read at that log dump.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

  5. #5
    Join Date
    Jun 2008
    Location
    Norman, OK
    Posts
    209

    Default Re: Boot process log

    Quote Originally Posted by ssaatt View Post
    Thanks. I had some problems in the past but really think I am past them now. Right now the system is stable and working just fine. I have different thread about the wireless "thingy" and probably something will come up there. It doesn't bother me at all. Anything else noteworthy? I'm pretty sure my hard drive temperature isn't 125 degrees, but that should be some SMART interpreting error. Is this remounting for my drives normal? I have the following in fstab:
    Code:
     /dev/disk/by-id/ata-INTEL_SSDSC2MH120A2_LNEL127200CT120CGN-part3 /                    ext4       acl,noatime,discard   1 1 /dev/disk/by-id/ata-INTEL_SSDSC2MH120A2_LNEL127200CT120CGN-part1 /boot                ext4       acl,noatime,discard   1 2 /dev/disk/by-id/ata-INTEL_SSDSC2MH120A2_LNEL127200CT120CGN-part2 swap                 swap       defaults              0 0 proc                 /proc                proc       defaults              0 0 sysfs                /sys                 sysfs      noauto                0 0 debugfs              /sys/kernel/debug    debugfs    noauto                0 0 usbfs                /proc/bus/usb        usbfs      noauto                0 0 devpts               /dev/pts             devpts     mode=0620,gid=5       0 0 /dev/disk/by-id/ata-SAMSUNG_HD204UI_S2H7J90B110667-part1 /home/saty/storage/  ext4       defaults              1 2
    Also there are some "Multiple occurrences of section ..... Consider merging them." entries. Anything about them?
    Since you have 'discard' as one of your mount options, then I'm going to assume you are using SSD's. You should also append "nodiratime" as a mount option. I also use 'barrier=0,journal_async_commit' but you need to read up on what those mount options do before adding them and understand the tradeoffs. Also how much RAM do you have? I'd mount /tmp as tmpfs and run it in RAM, you get much better performance that way, but now we are getting off-topic.
    Main Machine: Dell Precision M6600 running openSUSE Leap 16
    Server: Dell PowerEdge SC1430 running SLES 15

  6. #6

    Default Re: Boot process log

    Quote Originally Posted by robin_listas View Post
    On 2011-11-30 18:36, ssaatt wrote:
    > Can anyone see something wrong?


    I'm not going to look. First you tell me if you are experiencing problems
    and what are the symptoms, and then I may have a long read at that log dump.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)
    That just is not the right attitude man. If you don't want to read it then just don't but it's a couple of rows. I have several threads in these forums full of "problems". Right now I believe everything is sorted out and just wanna double check. You really believe there is something wrong in that?

    Take care.

    @katanacb I use intel 510 120GB ssd with 8 gigs of RAM. I had way more optimizations than this at one time(explained in pretty long thread in hardware section- "experiencing opensuse12.1 random crashes") but started seeing some crashes so for now I've left most of them out. As for nodiratime - I believe noatime includes nodiratime.

  7. #7
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Boot process log

    On 2011-12-01 09:46, ssaatt wrote:

    > That just is not the right attitude man. If you don't want to read it
    > then just don't but it's a couple of rows.


    No, it is several pages, and my time is valuable and limited.

    > I have several threads in
    > these forums full of "problems".


    Which I may not have seen or remember. If you tell me what problem you
    suspect, I can have a careful look at the log. Or, you can look instead at
    the "warning" log, that is smaller and should have only suspected problems.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •