[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Bug 1435] New: Shutdown-at-night do not work because ldap group membership names do not match


           Summary: Shutdown-at-night do not work because ldap group
                    membership names do not match
           Product: Skolelinux
           Version: lenny-rc2
          Platform: All
        OS/Version: Linux
            Status: ASSIGNED
          Severity: normal
          Priority: P3
         Component: System distrubution
        AssignedTo: debian-edu@lists.debian.org
        ReportedBy: pere@hungry.com

I just discovered that shutdown-at-night do not work with the LDAP host
groups populated by lwat.

Adding the host static00.intern to the shutdown-at-night group in lwat causes
the host name 'static00' to be added to the group, while the shutdown-at-night
cron job is looking for the value of uname -n, which in this case is
'static00.intern'.  The two strings do not match, and the host is not shut
down at it should.

I see two proposals for a solution.

(1)Get lwat to add both strings to the group ('static00' and
'static00.intern').  This is the way we add hosts to host netgroups at
the University of Oslo, because different operating systems check group
memberships differently and we want it to work on both Solaris, Linux
and Tru64 Unix.

(2)Get shutdown-at-night to look for both the output of uname -n and
the output of hostname -s (which is 'static00') in the cron job.

The second solution is easy to activate with a package upgrade, while the first
is hard (require rewriting the current LDAP database content).

The shutdown-at-night feature is one of the new features in the lenny
release, so it is a pitty it isn't working as it should out of the box.

Configure bugmail: http://bugs.skolelinux.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.

Reply to: