[SOLVED] rtorrent&screen don't start at boot time

Hello. I use rc-script from ArchWiki to start screen with rtorrent (http://wiki.archlinux.org/index.php/RTo … ith_screen), but at boot time neither rtorrent nor screen start, although script prints "[DONE]". If I login as root and start script manually it works perfect, but I can't understand why it doesn't start automatically.
Please, help.
P.S. Of course script was added to DAEMONS array in rc.conf.
Last edited by Atragor (2009-03-29 11:56:10)

jordz, adding command to rc.local didn't change anything.
LeoSolaris, yes, script is executable, and according to screen's man page:
-d -m      Start screen in "detached" mode. This creates a new session but doesn't  attach  to  it.  This  is  useful  for  system startup scripts.
I think it's something that could be called "daemon mode".
Maybe some environment variables must be set in order to execute screen and rtorrent? I've tried to set HOME manually but it didn't help.

Similar Messages

  • Auditing a process started at boot time

    Hi All,
    I am having a problem with auditd. I am starting a process of my own at boottime that I would like to audit. I think the problem lies in that my process is not getting an auditID. If I run the process from a terminal after the system is started it audits correctly, only when started at boot will it not audit.
    I have the process's audit class defined in the audit_control file as such (md is my audit class):
    dir:/var/audit
    flags:md,lo,ad,-fw,-fm,-fd,-nt,no
    minfree:50
    naflags:md
    I thought placing it under naflags would allow it to audit without attributes, but this does not work. The audit event and audit class are also properly in place.
    Any help with getting a process to audit when started at boot would be greatly appreciated.
    Victor

    Hi,
    Processes, are not able to start at boot-time as the "processes" is a OS based concept. The closest method you can do is replace the bootloader of Windows with your bootloader then load the Windows through your bootloader, and before loading the OS your
    Bootloader can perform any calculations or start files up as soon as Windows loads. This is the only way to start processes closest to Boot time. 
    In windows vista+ OS this technique would not work because Windows Vista+ has Session separation which by design separates processes into sessions and if you were to start it as soon as the OS starts the process would crash the entire OS as the process would
    not be able to fit in any session as it started before "Winlogon.exe"
    process. Therefore it is not really possible. 

  • Process start at boot time..

    Hi All,
    I am developing a client application which needs to be start up at boot time and there is one more requirement that no body 
    should be able to delete this to provide it security.
    Please reply .
    Thanks

    Hi,
    Processes, are not able to start at boot-time as the "processes" is a OS based concept. The closest method you can do is replace the bootloader of Windows with your bootloader then load the Windows through your bootloader, and before loading the OS your
    Bootloader can perform any calculations or start files up as soon as Windows loads. This is the only way to start processes closest to Boot time. 
    In windows vista+ OS this technique would not work because Windows Vista+ has Session separation which by design separates processes into sessions and if you were to start it as soon as the OS starts the process would crash the entire OS as the process would
    not be able to fit in any session as it started before "Winlogon.exe"
    process. Therefore it is not really possible. 

  • [SOLVED - partly] Minidlna won't start on boot, but OK otherwise

    I am using an up-to-date system as of 2012-11-13. The problem is that minidlna fails to start on boot:
    minidlna.service - minidlna server
    Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
    Active: failed (Result: exit-code) since Tue, 2012-11-13 07:53:55 CET; 1h 33min ago
    Process: 401 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
    CGroup: name=systemd:/system/minidlna.service
    Nov 13 07:53:59 earth minidlna[401]: [2012/11/13 07:53:54] minidlna.c:754: fatal: No IP address automatically detected!
    So I guess it has to do something with the network, I am using DHCP, with systemd + net-auto-wired.service.
    I have found this: https://ask.fedoraproject.org/question/ … r-dhcp-has
    They have solved the problem by changing the after part in the unit by adding: dbus-org.freedesktop.NetworkManager.target
    Since I do not use networkmanager, this is not an option for me. The current, unmanipulated state of the minidlna unit is:
    [Unit]
    Description=minidlna server
    After=network.target
    [Service]
    Type=forking
    User=nobody
    ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid
    PIDFile=/var/run/minidlna/minidlna.pid
    [Install]
    WantedBy=multi-user.target
    What I have noticed is that it refers to a network.target in the after section, but it seems to me that I don't have one.
    I only have:
    UNIT LOAD ACTIVE SUB JOB DESCRIPTION
    basic.target loaded active active Basic System
    cryptsetup.target loaded active active Encrypted Volumes
    getty.target loaded active active Login Prompts
    graphical.target loaded active active Graphical Interface
    local-fs-pre.target loaded active active Local File Systems (Pre)
    local-fs.target loaded active active Local File Systems
    multi-user.target loaded active active Multi-User
    remote-fs.target loaded active active Remote File Systems
    sockets.target loaded active active Sockets
    sound.target loaded active active Sound Card
    swap.target loaded active active Swap
    sysinit.target loaded active active System Initialization
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    JOB = Pending job for the unit.
    12 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    Edit: having run the command again with the --all prefix:
    Notice: network.target         loaded inactive dead       Network
    UNIT LOAD ACTIVE SUB JOB DESCRIPTION
    basic.target loaded active active Basic System
    cryptsetup.target loaded active active Encrypted Volumes
    emergency.target loaded inactive dead Emergency Mode
    final.target loaded inactive dead Final Step
    getty.target loaded active active Login Prompts
    graphical.target loaded active active Graphical Interface
    local-fs-pre.target loaded active active Local File Systems (Pre)
    local-fs.target loaded active active Local File Systems
    multi-user.target loaded active active Multi-User
    network.target loaded inactive dead Network
    nss-lookup.target loaded inactive dead Host and Network Name Lookups
    nss-user-lookup.target loaded inactive dead User and Group Name Lookups
    remote-fs.target loaded active active Remote File Systems
    rescue.target loaded inactive dead Rescue Mode
    shutdown.target loaded inactive dead Shutdown
    sockets.target loaded active active Sockets
    sound.target loaded active active Sound Card
    swap.target loaded active active Swap
    sysinit.target loaded active active System Initialization
    syslog.target loaded inactive dead Syslog
    umount.target loaded inactive dead Unmount All Filesystems
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    JOB = Pending job for the unit.
    21 loaded units listed.
    To show all installed unit files use 'systemctl list-unit-files'.
    My question is what should I add to the after part to make minidlna work upon booting? Wouldn't a graphical.target be an overkill?
    Thanks in advance.
    Last edited by szebenyib (2012-12-02 16:45:26)

    szebenyib wrote:(However I cannot access the internet that way, maybe because of a bad network file. Honestly I have some space to improve my network knowledge.)
    In the case of the possible bad network file. here is what it expects.  First, you need to know the router's IP address.  In the following I will assume 192.168.0.1 for the router's IP address.
    192.168.0.1 is common for D-Link routers, but it does vary by router manufacturer and model.  I believe 192.168.1.1 is common for Linksys.
    /etc/conf.d/network
    interface=eth0                                    # ethernet port to activate, usually eth0
    address=192.168.0.110                     # IP address you want the minidlna computer to have. the first 3 triads must be the same as the router's IP addr in this case 192.168.0  the fourth triad can be from 5 to 250
    netmask=24
    broadcast=192.168.0.255                  # the first 3 triads must be the same as the router's IP address and the fourth triad should be 255
    gateway=192.168.0.1                         # the IP address of your router
    In a terminal window, enter:
    systemctl restart network.service
    ping -c5 127.0.0.1
    which is localhost.  The -c5 means ping 5 times then quit.  If you get: 5 packets transmitted, 5 received, 0% packet loss    then the ping was successful, which means
    that the ethernet port (usually eth0) is active.  If this ping is not successful, go back and check the syntax and spelling in both /etc/conf.d/network and /etc/systemd/system/network.service
    If the ping is successful:
    ping -c5 192.168.0.1
    and ping the router.
    If you cannot ping the router's IP address, then there is still something wrong in one of the two involved files. or the router's settings need to be changed.
    If you can ping the router's IP address successfully and still cannot get to the internet, you probably have DNS server issues.
    ping -c5 google.com
    ping -c5 8.8.8.8
    If you cannot ping google.com but can ping 8.8.8.8 then you have DNS problems, see Arch WIKI resolv.conf
    My network is a mixture of DHCP and STATIC IP addresses.  In my router, I have the DHCP server enabled to give IP addresses between 192.168.0.10 and 192.168.0.60
    this gives the router 50 DHCP addresses to work with which is more that enough for my home network.  The rest of the addresses between 192.168.0.61 and 192.168.0.250
    can be used as static addresses.  Just an example, this can be changed as necessary.
    HTH
    Pudge

  • RTorrent+Screen doesn't start properly from systemd

    I decided to finally upgrade my system from init.d to systemd.
    Pretty much everything went smoothly except my rtorrent+screen startup.
    I'm using mostly the ruTorrent webui for controlling rtorrent. I'm using a service that starts rTorrent in a detatched GNU screen.
    This is my problem, when I start the service, rtorrent is just king of sleeping and not responding/doesn't create a SCGI socket I use to connect my webui to the rtorrent client.
    If I attach the screen the problem goes away and rtorrent resumes normal operation. If I run the exact same commands through a shell, it also works perfectly.
    I've also tried to run a basic screen as a service with rtorrent in my ~/.screenrc .
    Can anyone help? I've got no idea how to do debug this more than checking so that rtorrent and the service are running.
    This is my service:
    [Unit]
    Description=rTorrent
    [Service]
    Type=forking
    ExecStart=/usr/bin/screen -d -m -S rtorrent /usr/bin/rtorrent
    ExecStop=/usr/bin/killall -w -s 2 rtorrent
    [Install]
    WantedBy=multi-user.target
    My systemctl status output:
    rtorrent.service - rTorrent
    Loaded: loaded (/etc/systemd/system/rtorrent.service; enabled)
    Active: active (running) since Thu 2013-01-24 21:50:10 CET; 54s ago
    Process: 1130 ExecStart=/usr/bin/screen -d -m -S rtorrent /usr/bin/rtorrent (code=exited, status=0/SUCCESS)
    Main PID: 1131 (screen)
    CGroup: name=systemd:/system/rtorrent.service
    1131 /usr/bin/SCREEN -d -m -S rtorrent /usr/bin/rtorrent
    1133 rtorrent
    Jan 24 21:50:10 Laptop systemd[1]: Starting rTorrent...
    Jan 24 21:50:10 Laptop systemd[1]: Started rTorrent.
    ps -aux | grep rtorrent output
    root 1131 0.0 0.0 15560 1008 ? Ss 21:50 0:00 /usr/bin/SCREEN -d -m -S rtorrent /usr/bin/rtorrent
    root 1133 0.0 0.1 201528 5172 pts/0 Ssl+ 21:50 0:00 rtorrent

    This works for me, YMMV:
    /etc/systemd/system/screen.service
    [Unit]
    Description=Detached screen session
    After=network.target
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    User=tomk
    ExecStart=/usr/bin/screen -dm
    [Install]
    Wants=network.target
    WantedBy=multi-user.target
    ~/.screenrc
    screen -t rtorrent 5 /usr/bin/rtorrent

  • [SOLVED] systemd : services failing to start on boot

    I have removed sysvinit completely as per the systemd wiki pages.
    I don't usually re-boot very often so I'm not sure exactly when the problem started.
    I only noticed this problem about 4 or 5 days ago.
    But now whenever I reboot my machine 2 services fail consistently.
    adsl.service
    colord.service
    They both start flawlessly once I can log in at a console.
    I'm using kde and in the last couple of days, while trying to fix my problem, the kdm service has failed to start a couple of times too - saying there is no X server.
    Before switching to systemd I never had any of these problems using the old rc.conf method. My DAEMONS array had the adsl service start after the network service.
    I need some help and advice to find out what is causing the problem and how to fix it.
    Last edited by bhrgunatha (2012-10-25 05:44:22)

    Thanks. That seems plausible. So I've been snooping at the journal.
    journalctl -ab
    Oct 25 17:06:13 starch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Oct 25 17:06:14 starch systemd[1]: Started Recreate Volatile Files and Directories.
    Oct 25 17:06:14 starch systemd[1]: Starting System Initialization.
    Oct 25 17:06:14 starch systemd[1]: Reached target System Initialization.
    Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printing Service Sockets.
    Oct 25 17:06:14 starch systemd[1]: Listening on CUPS Printing Service Sockets.
    Oct 25 17:06:14 starch systemd[1]: Starting Console System Startup Logging...
    Oct 25 17:06:14 starch systemd[1]: Starting Restore Sound Card State...
    Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printer Service Spool.
    Oct 25 17:06:14 starch systemd[1]: Started CUPS Printer Service Spool.
    Oct 25 17:06:14 starch systemd[1]: Starting D-Bus System Message Bus Socket.
    Oct 25 17:06:16 starch ntpd[381]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
    Oct 25 17:06:16 starch ntpd[413]: proto: precision = 0.156 usec
    Oct 25 17:06:17 starch ntpd[413]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 25 17:06:17 starch ntpd[413]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen and drop on 1 v6wildcard :: UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen normally on 3 lo ::1 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: peers refreshed
    Oct 25 17:06:18 starch ntpd[413]: Listening on routing socket on fd #20 for interface updates
    Oct 25 17:06:18 starch dbus[384]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
    Oct 25 17:06:18 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Oct 25 17:07:03 starch dbus[384]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
    Oct 25 17:07:03 starch systemd[1]: Starting Manage, Install and Generate Color Profiles...
    Oct 25 17:07:03 starch systemd[1]: Started Manage, Install and Generate Color Profiles.
    Oct 25 17:07:03 starch systemd[1]: colord.service: main process exited, code=killed, status=6
    Oct 25 17:07:03 starch systemd[1]: Unit colord.service entered failed state.
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
    Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    Oct 25 17:07:04 starch kernel: PPP generic driver version 2.4.2
    Oct 25 17:07:04 starch cupsd[380]: Unknown directive DefaultAuthType on line 26.
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link up
    Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Oct 25 17:07:04 starch pppoe-start[382]: TIMED OUT
    Oct 25 17:07:04 starch kernel: NET: Registered protocol family 24
    Oct 25 17:07:04 starch pppoe-start[382]: /usr/sbin/pppoe-start: line 193: 394 Terminated $CONNECT "$@" > /dev/null 2>&1
    That seems to confirm your theory.
    eth0 link is not up when attempting to start colord and adsl
    So the $64,000 question:
    How do I defer them until eth0 is ready?
    Or how can I force the eth0 link to be up before colord or adsl try to use it?
    Last edited by bhrgunatha (2012-10-25 01:33:36)

  • SMF - start at boot time, but don't restart - possible?

    I'm setting up a software package that has a number of background processes.
    I've got SMF manifests created and imported for all of them, and they're working great for starting the processes at boot time, and doing the automatic restarts when one fails.
    Here's my problem. It turns out that the users of this software want to be able to use the software's integrated process control methods to stop some of their processes. With the current configuration, they use the software's method to stop one of it's processes, and SMF promptly restarts it.
    Is there a way to set up SMF managed software so that SMF starts it at boot time, but then doesn't care if stops later?
    Richard

    I'm not sure how it would be SMF "managed" in such a case. Obviously you want the management to be elsewhere.
    You could use the "legacy" startup scripts in /etc/rcX.d. That will start a process and forget about it, just like pre-Solaris 10. You don't use manifests or have any other benefits of SMF.
    If you do want SMF, I guess the question is how you want it to act..
    When the users stop the processes, do you want SMF to say enabled or disabled? SMF does not track enabled processes by periodic polling, it does it by tracking contracts. This means that starting a process outside of SMF does not allow SMF to track it.
    Darren

  • [SOLVED] NET_PROFILES=('menu') doesn't work at boot time

    Hi I've created two network profiles to change eth0 configuration on my laptop according to where I am.
    The problem is that NET_PROFILES=('menu') (in rc.conf) doesn't work at boot time: the profile select dialog doesn't appear.
    It works only if I do a /etc/rc.d/network restart.
    Here is the relevant part of my rc.conf
    lo="lo 127.0.0.1"
    eth0="eth0 192.168.0.3 netmask 255.255.255.0 broadcast 192.168.0.255"
    INTERFACES=(lo eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network-profiles
    NET_PROFILES=('menu') #### I tried even without quotes with the same result!!
    By the way, I tried this on three different machines (one is always up to date, the others aren't)  with the same result.
    Last edited by proc (2007-04-15 14:00:57)

    iphitus thanks for your prompt reply, but I already have dialog installed. In fact the menu appears if I do a network restart, but it doesn't at boot.

  • [SOLVED!] Archiso -- KDM - LXDM don't start at boot (enabled)

    Hello,
    I have installed on this computer my customized Archiso (with no special configurations). I have enabled kdm.service, but nothing happened. After reboot either.
    I have now tried with LXDM, same thing. With "systemctl status" I usually get something like: "enabled, dead"
    If I start kdm or lxdm manually, it works.
    sudo systemctl start lxdm; sudo systemctl status lxdm
    lxdm.service - LXDE Display Manager
    Loaded: loaded (/usr/lib/systemd/system/lxdm.service; enabled)
    Active: active (running) since vie 2013-03-29 13:54:08 UTC; 46min ago
    Main PID: 319 (lxdm-binary)
    CGroup: name=systemd:/system/lxdm.service
    └─321 /usr/bin/X :0 vt07 -nolisten tcp
    ‣ 319 /usr/sbin/lxdm-binary
    mar 29 13:54:08 ubunchu systemd[1]: Starting LXDE Display Manager...
    mar 29 13:54:08 ubunchu systemd[1]: Started LXDE Display Manager.
    mar 29 13:54:12 ubunchu lxdm-binary[319]: pam_unix(lxdm:session): session opened for user ubunchu by (uid=0)
    Dmesg: http://pastie.org/private/8n97afoezf3urejz3qizeq
    On some posts they mentioned that maybe nvidia or a module starts up too late, or the login managers too early.
    Any tips/hints on what should I try?
    Thanks in advance.
    Cheers!
    Last edited by ubunchu (2013-04-22 22:06:12)

    At boot I can get:
    [root@ubunchu ~]# systemctl status kdm
    kdm.service - K Display Manager
    Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled)
    Active: inactive (dead)
    [root@ubunchu ~]# ls -al /etc/systemd/system/
    total 32
    drwxr-xr-x 4 root root 4096 abr 10 22:51 .
    drwxr-xr-x 5 root root 4096 abr 18 09:10 ..
    -rw-r--r-- 1 root root 1660 mar 23 16:43 [email protected]
    lrwxrwxrwx 1 root root 46 mar 24 13:39 dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
    lrwxrwxrwx 1 root root 41 mar 23 15:50 default.target -> /usr/lib/systemd/system/multi-user.target
    -rw-r--r-- 1 root root 230 mar 7 14:07 dhcpcd.service
    lrwxrwxrwx 1 root root 35 abr 10 22:51 display-manager.service -> /usr/lib/systemd/system/kdm.service
    -rw-r--r-- 1 root root 134 mar 7 14:07 etc-pacman.d-gnupg.mount
    drwxr-xr-x 2 root root 4096 abr 18 09:10 multi-user.target.wants
    drwxr-xr-x 2 root root 4096 mar 24 13:39 network.target.wants
    -rw-r--r-- 1 root root 325 mar 7 14:07 pacman-init.service
    On every system I install my custom archiso (basic install) the same thing happens, what am I missing?

  • [SOLVED] apache daemon fails to start on boot, but rc.d restart works?

    I installed apache from the official repos and followed the instructions in the wiki for configuring it. I checked to make sure the http user exists, and I /etc/hosts looks good (to me). Upon boot, the daemon fails to start and I can't load local web pages, but running "rc.d restart httpd" works just fine. Since I'd rather not start it manually every time I boot, is there a way to fix this? Also, httpd is the last daemon in my DAEMONS array.
    /etc/httpd/conf/httpd.conf:
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
    # with ServerRoot set to "/etc/httpd" will be interpreted by the
    # server as "/etc/httpd//var/log/httpd/foo_log".
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk. If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "/etc/httpd"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 127.0.0.1:80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_anon_module modules/mod_authn_anon.so
    LoadModule authn_dbd_module modules/mod_authn_dbd.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    LoadModule auth_digest_module modules/mod_auth_digest.so
    LoadModule file_cache_module modules/mod_file_cache.so
    LoadModule cache_module modules/mod_cache.so
    LoadModule disk_cache_module modules/mod_disk_cache.so
    LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule dbd_module modules/mod_dbd.so
    LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule reqtimeout_module modules/mod_reqtimeout.so
    LoadModule ext_filter_module modules/mod_ext_filter.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    LoadModule substitute_module modules/mod_substitute.so
    LoadModule deflate_module modules/mod_deflate.so
    LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule log_forensic_module modules/mod_log_forensic.so
    LoadModule logio_module modules/mod_logio.so
    LoadModule env_module modules/mod_env.so
    LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    LoadModule ident_module modules/mod_ident.so
    LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule ssl_module modules/mod_ssl.so
    LoadModule mime_module modules/mod_mime.so
    LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule info_module modules/mod_info.so
    LoadModule suexec_module modules/mod_suexec.so
    LoadModule cgi_module modules/mod_cgi.so
    LoadModule cgid_module modules/mod_cgid.so
    LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule rewrite_module modules/mod_rewrite.so
    #php
    LoadModule php5_module modules/libphp5.so
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName www.example.com:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # Options FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock /var/run/httpd/cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # MaxRanges: Maximum number of Ranges in a request before
    # returning the entire resource, or one of the special
    # values 'default', 'none' or 'unlimited'.
    # Default setting is to accept 200 Ranges.
    #MaxRanges unlimited
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    #PHP
    Include conf/extra/php5_module.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    /etc/hosts
    # /etc/hosts: static lookup table for host names
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost laptop
    ::1 localhost.localdomain localhost
    # End of file
    Per the wiki, I also tried commenting out the line that reads
    LoadModule unique_id_module modules/mod_unique_id.so
    Either way, it still fails on boot.
    Last edited by pythonscript (2012-06-10 21:14:44)

    The SIGTERM are from reboots, yes. I'm not absolutely sure that the process isn't running; I just know that I can't access http://localhost immediately upon reboot. I have to restart the httpd daemon, which works fine. How would I be able to tell if it's just hung?
    I checked everything.log, and I don't see anything that leaps off the page to me.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1930 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 2 threads of 1 processes of 1 users.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1931 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 3 threads of 1 processes of 1 users.
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=RegisterClient
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: RegisterClient 106d33cade29b1ba713392593689729000000018320001
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689729000000018320001 to session
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): uid = 120
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): pid = 1842
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client2 to store
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client2
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): App gnome-settings-daemon.desktop registered
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase INITIALIZATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting app '/org/gnome/SessionManager/App1'
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): Starting app: /org/gnome/SessionManager/App1
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: starting gnome-shell.desktop: command=gnome-shell --gdm-mode startup-id=106d33cade29b1ba713392593689681600000018320000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: started pid:1936
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase RUNNING
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmPresence: adding idle watch
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for positive transition wait=600000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for negative transition wait=599999
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost kernel: [ 29.003352] wlan0: no IPv6 routers present
    Jun 9 17:29:31 localhost NetworkManager[765]: <warn> could not commit DNS changes: (0) Could not replace /etc/resolv.conf: Operation not permitted
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) successful, device activated.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: accept_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: auth_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Setting up new connection
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: New client '0x7f9ff0004e60 []'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client3 to store
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client3
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Initializing client 0x7f9ff0004e60 []
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 []' received RegisterClient(106d33cade29b1ba713392593689681600000018320000)
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689681600000018320000 to session
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Sending RegisterClientReply to '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Set properties from client '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Program = 'gnome-shell'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: UserID = 'gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 0
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: ProcessID = '1936'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: CurrentDirectory = '/var/lib/gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: _GSM_Priority = 20
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: sending IPv6 Router Solicitation
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: no IPv6 Routers available
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: sending IPv6 Router Solicitation
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: no IPv6 Routers available
    Jun 9 17:29:33 localhost NetworkManager[765]: <warn> error monitoring device for netlink events: error processing netlink message: Object busy
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> (eth0): IP6 addrconf timed out or failed.
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> (wlan0): IP6 addrconf timed out or failed.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: handling signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Found 1 callbacks
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x41c9e0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Got callback for signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Logout called
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: requesting logout
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase RUNNING
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: sending query-end-session to clients (logout mode: forceful)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.8
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Caught signal 15, shutting down normally.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Done handling signals
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, 9, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: query end session complete
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, c, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect for app 'at-spi-registryd.desktop'
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: unable to find application for client - not restarting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428a40
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Using ConsoleKit for session tracking
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_stop ('0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]')
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received CloseConnection
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x7f9ff0004e60
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000])
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428ac0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: last client disconnected - exiting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Unreffing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disposing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473070
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473150
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gdm-simple-slave[1728]: WARNING: Child process 1832 was already dead.
    Jun 9 17:29:43 localhost gnome-session[1970]: EggSMClient-WARNING: Desktop file '/home/ak5791/.config/autostart/dropbox.desktop' has malformed Icon key 'dropbox.png'(should not include extension)
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2022 of process 2022 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 4 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2023 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 5 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2024 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 6 threads of 2 processes of 2 users.
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
    Jun 9 17:29:44 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.colord-sane' (using servicehelper)
    Jun 9 17:29:45 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.colord-sane'
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Successfully made thread 2079 of process 2079 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Supervising 7 threads of 3 processes of 2 users.
    Jun 9 17:29:46 localhost pulseaudio[2079]: [pulseaudio] pid.c: Daemon already running.
    Jun 9 17:29:48 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
    Jun 9 17:29:48 localhost udisksd[2110]: udisks daemon version 1.94.0 starting
    Jun 9 17:29:48 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks2'
    Jun 9 17:29:48 localhost udisksd[2110]: Acquired the name org.freedesktop.UDisks2 on the system message bus
    Jun 9 17:29:48 localhost kernel: [ 46.319778] gnome-shell-cal[2103] trap int3 ip:7ff3f55b85e1 sp:7fff94941890 error:0
    Jun 9 17:30:19 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:40:53 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:47:15 localhost kernel: [ 1092.983585] usb 8-1.4.1: new high-speed USB device number 8 using ehci_hcd
    Jun 9 22:47:15 localhost mtp-probe: checking bus 8, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1/8-1.4/8-1.4.1"
    Jun 9 22:47:15 localhost mtp-probe: bus: 8, device: 8 was not an MTP device
    Jun 9 22:47:15 localhost kernel: [ 1093.132002] usbcore: registered new interface driver uas
    Jun 9 22:47:15 localhost kernel: [ 1093.135601] Initializing USB Mass Storage driver...
    Jun 9 22:47:15 localhost kernel: [ 1093.135785] scsi6 : usb-storage 8-1.4.1:1.0
    Jun 9 22:47:15 localhost kernel: [ 1093.135905] usbcore: registered new interface driver usb-storage
    Jun 9 22:47:15 localhost kernel: [ 1093.135913] USB Mass Storage support registered.
    Jun 9 22:47:16 localhost kernel: [ 1094.137579] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2 1.00 PQ: 0 ANSI: 2
    Jun 9 22:47:16 localhost kernel: [ 1094.140133] sd 6:0:0:0: [sdb] 15636304 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Jun 9 22:47:16 localhost kernel: [ 1094.140631] sd 6:0:0:0: [sdb] Write Protect is off
    Jun 9 22:47:16 localhost kernel: [ 1094.140634] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
    Jun 9 22:47:16 localhost kernel: [ 1094.141128] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.141132] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.144916] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.144921] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.146680] sdb: sdb1
    Jun 9 22:47:16 localhost kernel: [ 1094.151407] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.151411] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.151414] sd 6:0:0:0: [sdb] Attached SCSI removable disk
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Version 2012.1.15 external FUSE 29
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mounted /dev/sdb1 (Read-Write, label "kingstonGB", NTFS 3.1)
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uhelper=udisks2
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Global ownership and permissions enforced, configuration type 7
    Jun 9 22:47:17 localhost udisksd[2110]: Mounted /dev/sdb1 at /run/media/ak5791/kingstonGB on behalf of uid 1000
    Jun 9 22:47:28 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
    Jun 9 22:47:28 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks'
    Jun 9 22:47:46 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:57:59 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 23:01:02 localhost /USR/SBIN/CROND[5529]: (root) CMD (run-parts /etc/cron.hourly)
    Jun 9 23:21:02 localhost -- MARK --
    All I notice is that my system's time is having a few problems, since you'll notice that events occur at 22:00 and change, then 17:00 and change, then back to 22:00 and change afterwards. Could this be the problem? I've had the CMOS batteries peg out on me suddenly in the last few weeks. I would hope this sytem is not also suffering a similar fate. Nothing else was happening on my system except for the standard processes from /etc/rc.conf and other standard ones, since I've just been rebooting, checking the logs, then posting here.

  • [SOLVED]Graphical environment doesn't start on boot

    Hi,
    I've tried to change default boot target to graphical, but it doesn't work. I use grub so I tried to edit
    /etc/default/grub
    GRUB_DEFAULT=2
    GRUB_TIMEOUT=5
    GRUB_DISTRIBUTOR="Arch"
    GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.unit=graphical.target"
    GRUB_CMDLINE_LINUX=""
    It didn't change anything, so I tried to use
    systemctl set-default -f graphical.target
    But it's not working either. What am I doing wrong? Or what am I missing?
    I know that simple workaround is starting X after log in to console, but I don't want this.
    Last edited by blady (2014-05-10 09:14:16)

    If you don't wan't to use a DM: Start X at Login and Automatic login to virtual console. Then set multi-user as default target.
    Last edited by Ziusudra (2014-05-10 06:58:21)

  • Black screen on system start, before boot.

    This machine had a noisy cooling fan for some time, then the screen suddenly went black but could see very dimmed images on it when using a flashlight.
    Now the fan is quiet, but working and cooling, however the screen is entirely black after power up, the ESC to enter menu appears in orange color, then nothing at all. When pressing escape, it also goes entirely black. Can see the hard drive light flashing and have removed the drive to check it externally. The drive is fine. Different RAM makes no difference.
    Is the graphics chip damaged and if so, can it be replaced in the Philippines at a service center?
    Thanks.

    @knetphils 
    ‎Thank you for using HP Support Forum. I have brought your issue to the appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post ( serial numbers and case details).
    If you are unfamiliar with the Forum's private messaging please click here to learn more.
    Thank you,
    Omar
    I Work for HP

  • Openntpd won't start at boot [SOLVED]

    Hi all!
    My system clock is perpetually off by 4 hours, and I've narrowed it down to an issue with Openntpd; it seems to be refusing to start at boot time. Here are the relevant lines from daemon.log:
    Sep 1 21:30:26 raskolnikov ntpd[1440]: Terminating
    and the output of ps aux | grep ntpd:
    [raskolnikov@raskolnikov ~]$ ps aux | grep ntpd
    ntp 1323 0.0 0.0 3184 700 ? S 17:32 0:00 /usr/sbin/ntpd -s
    root 1332 0.0 0.0 3292 256 ? Ss 17:32 0:00 /usr/sbin/ntpd -s
    1000 1412 0.0 0.0 3616 800 pts/0 S+ 17:33 0:00 grep ntp
    I can manually restart the daemon via /etc/rc.d/openntpd restart, which works fine, and the time is set correctly. However, when I reboot, the adjustments are wiped out, and the daemon does not start again (same message in daemon.log). I have the default ntpd.conf. I have found very little helpful information on Google, I would greatly appreciate it if someone could point me in the right direction, I've wasted quite a few hours this evening working on this problem! Thanks!
    Edit: Just in case it's helpful, here is my daemons array from rc.conf:
    DAEMONS=(syslog-ng !network acpid eee hal networkmanager netfs crond openntpd bitlbee)
    Last edited by happycodemonkey (2009-09-02 03:55:46)

    I've had this problem too, although I do not use networkmanager. I've found that openntpd fails to configure itself properly if the network is not up when it starts (in my case this happens when I background the network daemon and start openntpd in the daemons array).
    My current working solution* is to add this line to rc.local:
    (sleep 300 && /etc/rc.d/openntpd start) &
    That will wait 5 minutes before starting the openntpd daemon which gives the network more than sufficient time to start. An alternative would be run "/etc/rc.d/openntpd restart" in an hourly cronjob if your network settings change often.
    * Why not just unbackground the network daemon you ask? If the network isn't up then it takes a while to timeout and I don't want to wait to boot in that case.
    Last edited by Xyne (2009-09-02 02:05:52)

  • [solved] wireless doesn't start at boot

    I have BCM94311MCG wlan mini-PCI (rev 01) which works with b43 + wpa_supplicant nicely, except I can't seem to get to automagically start at boot time.
    wlan0 always times out (wired connects at boot time just fine). I'd like my laptop to automatically connect to one of two networks, else remain disconnected.
    Once started I can always netcfg2 <network name> and it connects no problem... I must have missed something in the wireless setup but I can't find what it is.
    my rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    LOCALE="en_US.utf8"
    HARDWARECLOCK="localtime"
    USEDIRECTISA="yes"
    TIMEZONE="Canada/Pacific"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    MOD_AUTOLOAD="yes"
    MOD_BLACKLIST=(!pcspkr !bcm43xx !ndiswrapper ) #deprecated
    MOD_LOADLIST=(acpi-cpufreq cpufreq_ondemand slhc i8k tg3 fuse b43 ppdev snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
    MODULES=( ${MOD_BLACKLIST[@]} ${MOD_LOADLIST[@]} )
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    HOSTNAME="myhostname"
    # Interfaces to start at boot-up (in this order)
    eth0="dhcp"
    wlan0="dhcp"
    INTERFACES=(eth0 wlan0)
    # Routes to start at boot-up (in this order)
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    NETWORKS=("auto-wireless wlan0")
    # DAEMONS
    DAEMONS=(syslog-ng iptables @network @fusesmb @cups !netfs !crond @alsa @hal @dbus @fam @acpid @laptop-mode @cpufreq)
    afaik the only unique thing I have in rc.conf is my fusesmb daemon (a script that mounts samba shares)
    and my network.d/<network name>
    CONNECTION="wireless"
    INTERFACE=wlan0
    SCAN="yes"
    SECURITY="wpa-config"
    ESSID="BCSI"
    IP="dhcp"
    TIMEOUT=20
    when I look for wpa_supplicant after a boot, it is not running ( ps aux | grep wpa ).
    wlan0 is up right after boot:
    $ ifconfig
    eth0 Link encap:Ethernet HWaddr 00:15:C5:08:1E:1C
    inet addr:10.1.1.148 Bcast:10.1.1.255 Mask:255.255.255.0
    inet6 addr: fe80::215:c5ff:fe08:1e1c/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:14443 errors:0 dropped:0 overruns:0 frame:0
    TX packets:13281 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:8031647 (7.6 Mb) TX bytes:2248854 (2.1 Mb)
    Interrupt:19
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:1221 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1221 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:75880 (74.1 Kb) TX bytes:75880 (74.1 Kb)
    wlan0 Link encap:Ethernet HWaddr 00:16:CE:67:85:B5
    inet addr:169.254.55.57 Bcast:169.254.255.255 Mask:255.255.0.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    wmaster0 Link encap:UNSPEC HWaddr 00-16-CE-67-85-B5-00-00-00-00-00-00-00-00-00-00
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    but since wpa_supplicant isn't running, it won't associate.
    I'm misunderstading (I think) how netcfg2 is used during startup, I thought the line  `NETWORKS=("auto-wireless wlan0")` would tell netcfg2 to try /etc/network.d/*
    thanks for looking
    Last edited by bioe007 (2008-04-30 14:19:12)

    From: http://wiki.archlinux.org/index.php/Network_Profiles
    "Ensure that net-profiles is in your rc.conf DAEMONS=() line."

  • How to start ASM instance at boot time - RHEL 2.1

    Oracle 10.1.0.3
    RHEL 2.1
    I'm not able to get the ASM instance (not RAC) to start at boot time. It seems that the ocssd daemon does not finish starting until after all rc* scripts, including rc.local, have finished executing.
    Patch 3458327 includes a new dbstart with header notes that are in conflict. The notes says that dbstart can't be used to start ASM until AFTER all rc* is finished.  Then it continues and states that ASM instance startup should be put in rc.local.
    As soon as I get logged on, a ps -ef|grep ocssd shows the daemon running. I can then manually start the ASM instance.  There must be a way to get the ASM instance "auto" started at boot time.
    Ideas?

    The cheapest and administratively easiest way for me was to start Oracle instances (ASM and data) by "at" command :-) from rc scripts. Something like:
    ....echo "oracle start" | at now+2min....
    Additionally the deferred startup has some additional advantages in my environment, so I am not motivated to look for better solution.
    Best regards,
    Pavel

Maybe you are looking for