Mr. Junjiro R. Okajima, Mr. Michael S. Zick,

   thanks for your answers concerning the AUFS kernel messages.


   Mr. Michael S. Zick,

   1. Kernel messages

   you are right, I use a Debian based Linux distribution. Thanks for
   your comprehensive explanation concerning the impact of the PAM
   module pam-mount on AUFS. I checked the system and couldn't find
   any usage of pam-mount. First I run the following command to find
   an installed binary package with libpam_mount.so:

   $> dpkg -S libpam_mount

   The answer was void. No libpam_mount* is installed on the system.
   Next I looked into the following directories and there configuration
   files:

   - /etc/security   I found only the file pam_env.conf. In the file
                     I couldn't find any hint on pam_mount.

   - /etc/pam.d      No of the files in that directory provides
                     somethings like pam_mount.

   No hint on the configuration file pam_mount.conf.xml in
   /etc/security or in ~/.

   Thanks again for your engagement.


   Mr. Junjiro R. Okajima,

   1. Kernel messages

   The script gdm is a init script from /etc/init.d. This starts the
   Debian GNOME Display Manager. The following lines show the contents
   of /etc/init.d/gdm:

   #! /bin/sh
   ### BEGIN INIT INFO
   # Provides:          gdm
   # Should-Start:      console-screen kbd acpid dbus hal \
                        network-manager
   # Required-Start:    $local_fs $remote_fs x11-common
   # Required-Stop:     $local_fs $remote_fs
   # Default-Start:     2 3 4 5
   # Default-Stop:      0 1 6
   # Short-Description: GNOME Display Manager
   # Description:       Debian init script for the GNOME Display \
                        Manager
   ### END INIT INFO
   #
   # Author:       Ryan Murray <rmur...@debian.org>
   #
   set -e

   PATH=/sbin:/bin:/usr/sbin:/usr/bin
   DAEMON=/usr/sbin/gdm

   test -x $DAEMON || exit 0

   if [ -r /etc/default/locale ]; then
     . /etc/default/locale
     export LANG LANGUAGE
   fi

   . /lib/lsb/init-functions

   # To start gdm even if it is not the default display manager, change
   # HEED_DEFAULT_DISPLAY_MANAGER to "false."
   HEED_DEFAULT_DISPLAY_MANAGER=true
   DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager

   case "$1" in
     start)
        CONFIGURED_DAEMON=$(basename \
           "$(cat $DEFAULT_DISPLAY_MANAGER_FILE 2> /dev/null)")
        if grep -wqs text /proc/cmdline; then
           log_warning_msg "Not starting GNOME Display Manager (gdm); \
           found 'text' in kernel commandline."
        elif [ -e "$DEFAULT_DISPLAY_MANAGER_FILE" ] && \
           [ "$HEED_DEFAULT_DISPLAY_MANAGER" = "true" ] && \
           [ "$CONFIGURED_DAEMON" != gdm ] ; then
           log_action_msg "Not starting GNOME Display Manager; \
           it is not the default display manager"
        else
           log_daemon_msg "Starting GNOME Display Manager" "gdm"
           start_daemon $DAEMON
           log_end_msg $?
        fi
     ;;
     stop)
        log_daemon_msg "Stopping GNOME Display Manager" "gdm"
        set +e
        start-stop-daemon --stop --quiet --pidfile /var/run/gdm.pid \
                          --name gdm --retry 5
        set -e
        log_end_msg $?
     ;;
     reload)
        log_daemon_msg \
        "Scheduling reload of GNOME Display Manager configuration" \
        "gdm"
        set +e
        start-stop-daemon --stop --signal USR1 --quiet --pidfile \
                          /var/run/gdm.pid --name gdm
        set -e
        log_end_msg $?
     ;;
     status)
        status_of_proc -p "$PIDFILE" "$DAEMON" gdm && exit 0 || exit $?
     ;;
     restart|force-reload)
        $0 stop
        $0 start
     ;;
     *)
        echo "Usage: /etc/init.d/gdm \
        {start|stop|restart|reload|force-reload|status}"
        exit 1
     ;;
   esac

   exit 0


   Maybe this script starts other processes that interfere with AUFS.
   After the GNOME Desktop session log in I listed all running
   processes with the following command:

   $> sudo ps aux | less -SM

   The following lines show all processes that were created during
   the GNOME Desktop session log in. Maybe one of these processes
   interfered with AUFS:

   USER   PID  COMMAND
   user  8849  /usr/bin/gnome-keyring-daemon --daemonize --login
   user  8861  x-session-manager
   user  8906  /usr/bin/ssh-agent \
               /usr/bin/dbus-launch \
               --exit-with-session x-session-manager
   user  8909  /usr/bin/dbus-launch \
               --exit-with-session x-session-manager
   user  8910  /usr/bin/dbus-daemon \
               --fork --print-pid 5 --print-address 8 --session
   user  8915  /usr/lib/libgconf2-4/gconfd-2
   user  8923  gnome-power-manager
   user  8928  /usr/lib/gnome-settings-daemon/gnome-settings-daemon
   root  8932  /usr/lib/upower/upowerd
   user  8954  /usr/lib/gvfs/gvfsd
   user  8958  /usr/bin/metacity
   user  8977  /usr/lib/gvfs/gvfs-gdu-volume-monitor
   root  8996  /usr/lib/udisks/udisks-daemon
   user  9003  gnome-panel
   root  9006  udisks-daemon: polling \
               /dev/sr0 /dev/sdb /dev/sdc /dev/sdd /dev/sde
   user  9021  nautilus
   user  9024  /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
   user  9027  /usr/lib/bonobo-activation/bonobo-activation-server \
               --ac-activate --ior-output-fd=20
   user  9031  /usr/lib/gvfs/gvfs-afc-volume-monitor
   user  9037  update-notifier
   user  9038  /usr/lib/evolution/3.0/evolution-alarm-notify
   user  9040  kerneloops-applet
   user  9042  /usr/lib/policykit-1-gnome\
               /polkit-gnome-authentication-agent-1
   user  9051  bluetooth-applet
   user  9053  /usr/lib/notification-daemon/notification-daemon
   user  9054  nm-applet --sm-disable
   user  9056  python /usr/bin/system-config-printer-applet
   user  9065  /usr/lib/gnome-disk-utility/gdu-notification-daemon
   user  9085  /usr/lib/gnome-applets/mixer_applet2 \
               --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory \
               --oaf-ior-fd=24
   user  9086  /usr/lib/gnome-applets/cpufreq-applet \
               --oaf-activate-iid=OAFIID:GNOME_CPUFreqApplet_Factory \
               --oaf-ior-fd=18
   user  9089  gnome-screensaver
   user  9094  /usr/lib/gvfs/gvfsd-trash --spawner :1.13 \
               /org/gtk/gvfs/exec_spaw/0
   user  9101  /usr/lib/gvfs/gvfsd-burn --spawner :1.13 \
               /org/gtk/gvfs/exec_spaw/1
   root  9113  /usr/bin/python /usr/sbin/aptd

   The next lines show the AUFS kernel message that was created during
   the above GNOME Desktop session log in:

   [11771.764716] aufs au_opts_parse:1039:mount[9011]: unknown option
                  errors=remount-ro
   [11771.771709] aufs au_opts_parse:1039:mount[9013]: unknown option
                  commit=0
   [11771.775236] aufs au_opts_parse:1039:mount[9015]: unknown option
                  commit=0
   [11771.782918] aufs au_opts_parse:1039:mount[9017]: unknown option
                  commit=0
   [11771.796819] aufs au_opts_parse:1039:mount[9018]: unknown option
                  commit=0
   [11771.812259] aufs au_opts_parse:1039:mount[9019]: unknown option
                  commit=0

   Maybe the above data could help to understand why AUFS generated
   the above kernel messages.

   I would be very glad, if you could find some time to answer my
   questions. Thanks a lot in advanced.

   Regards,
   Robert Wotzlaw


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

Reply via email to