Mailinglist Archive: opensuse-bugs (8111 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=249965

           Summary: gdm does not handle SIGHUP correctly, used by "rcxdm
                    reload"
           Product: openSUSE 10.3
           Version: Alpha 1plus
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
        AssignedTo: bnc-team-gnome@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: andreas.hanke@xxxxxxxxxxxxxx
         QAContact: qa@xxxxxxx


The xdm init script /etc/init.d/xdm contains this code:



    reload|force-reload)
        test -x /etc/X11/xdm/SuSEconfig.xdm && \
        MD5DIR="/var/adm/SuSEconfig/md5" \
          /etc/X11/xdm/SuSEconfig.xdm | \
          sed 's+\(.*\)+/etc/init.d/xdm: \1+g' | \
          /bin/logger
        echo -n "Reload service $DM"
        killproc -p $PIDFILE -HUP  $DISPLAYMANAGER
        rc_status -v
        ;;



gdm does not survive the "killproc -p $PIDFILE -HUP  $DISPLAYMANAGER" (and
kills the whole session with it).

This works correctly with kdm (also when using kdm+GNOME). It should work with
gdm as well.

SIGHUP is suggested by the LSB init specification to support reloading the
configuration of a service without restarting it:

http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html

Supporting this is not mandatory, though. But if it is not supported, it must
not crash: The specification says that "reload" should do nothing if it is not
supported (and crashing is not equal to "nothing").


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.