May 2005 - openSUSE Users - openSUSE Mailing Lists

Re: [SLE] SUSe 9.3 and LDAP Docu?
by Markus Natter 23 May '05

23 May '05

On 5/23/05, Jerry Westrick <jerry(a)westrick.com> wrote: > On Monday 23 May 2005 16:44, Markus Natter wrote: > > On 5/23/05, Markus Natter <markus.natter(a)gmail.com> wrote: > > > On 5/23/05, Jerry Westrick <jerry(a)westrick.com> wrote: > > > > On Monday 23 May 2005 09:29, Markus Natter wrote: > > > > > On 5/22/05, Jerry Westrick <jerry(a)westrick.com> wrote: > > > > > > Is there a step by step docu on > > > > > > how to get SuSE 9.3 to use openldap > > > > > > for authorization.... > > > > > > > > > > > > I worked my way through the Admin Guide... > > > > > > but All I get is connection failures.... > > > > > > > > > > > > anybody seen a decent how to? > > > > > > > > > > > > Jerry > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Check the headers for your unsubscription address > > > > > > For additional commands send e-mail to suse-linux-e-help(a)suse.com > > > > > > Also check the archives at http://lists.suse.com > > > > > > Please read the FAQs: suse-linux-e-faq(a)suse.com > > > > > > > > > > Hi Jerry, > > > > > > > > > > YaST could do this for you ( see chapter 29.5 SuSE Admin. Guide ).. > > > > > but on the other hand you need a working LDAP - configuration and and > > > > > a working database first. > > > > > > > > > > Have you already tried to connect and made a successful request with > > > > > any cmd-line ldap tools ( ldapsearch ... ) or any ldap client? > > > > > > > > > > > > > > > Markus > > > > > > > > Thanks for the answer Markus... > > > > > > > > Yes I got ldap running by following the instructions > > > > at /usr/share/doc/packages/openldap2/admin-guide/quickstart.html > > > > > > > > > > > > There I issued: > > > > > > > > ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts > > > > ldapadd -x -D "cn=Manager,dc=<MY-DOMAIN>,dc=<COM>" -W -f example.ldif > > > > ldapsearch -x -b 'dc=example,dc=com' '(objectclass=*)' > > > > > > > > all of which worked. > > > > > > > > I guess is that either the User (as setup by quick installation guide) > > > > is not yast compatible, or that the security method is not the one that > > > > yast expects? > > > > > > > > Jerry > > > > > > well, > > > there could be some caveats.. > > > > > > could you post your /etc/openldap/slapd.conf & /etc/ldap.conf? (e.g. > > > did you include the required .schema files, like > > > yast.schema [as I remember, yast uses member entries instead of > > > memberUID per default (you could change this behavior-> extended > > > settings)..]) > > > > > > the idea behind this all is, that yast would help you setting up the > > > other configs correctly.. > > > (some hints: /etc/pam.d, nss_ldap / pam_ldap, /etc/security, > > > /etc/nsswitch.conf ) > > > > > > another idea is to let yast create the standard objects etc.. [ > > > extended settings ], if your > > > setup does not fit into the yast expectations. > > > And also try one thing after another.. [ e.g. do not start with > > > TLS/SSL related stuff > > > before you have fixed the other problems ] > > > > > > Markus > > > > well I just tried this by setting up a very simple base.. (only the > > root-dir, and > > configured a rootdn and rootpw using slapadd, for setting things up.. > > then I configured a basic /etc/ldap.conf to point to the new slapd > > running on the localhost) > > and yast configured the rest for me.. it was not that difficult.. > > > > here are the lines I used for this test: > > > > /etc/slapd.conf: > > ============ > > > > # this should be the schema section as it was shipped.. > > include /etc/openldap/schema/core.schema > > include /etc/openldap/schema/cosine.schema > > include /etc/openldap/schema/inetorgperson.schema > > include /etc/openldap/schema/rfc2307bis.schema > > include /etc/openldap/schema/yast.schema > > > > suffix "dc=test,dc=example,dc=com" > > rootdn "cn=Manager,dc=test,dc=example,dc=com" > > # Cleartext passwords, especially for the rootdn, should > > # be avoid. See slappasswd(8) and slapd.conf(5) for details. > > # Use of strong authentication encouraged. > > rootpw secret > > > > base.ldif ( note: be careful with empty spaces at the end of a line, > > if you copy/paste! ) > > ======= > > > > ## > > ## TEST.EXAMPLE.COM > > ## > > ## Basis of the LDAP-tree test.example.com > > ## > > dn: dc=test,dc=example,dc=com > > dc: test > > o: example > > objectClass: organization > > objectClass: dcObject > > structuralObjectClass: organization > > > > ======= > > > > install this ldiff.. > > you should remove your old database before that.. > > please, keep your DB_CONFIG!!! > > > > rcldap stop > > > > cd /var/lib/ldap > > rm *.bdb log.* __db.* > > > > cd /etc/openldap/ # or wherever your base.ldif is > > slapadd -p -w -l base.ldif > > > > rcldap start > > > > /etc/ldap.conf > > ========== > > # Your LDAP server. Must be resolvable without using LDAP. > > # if you want tls / ssl later on, you should replace localhost with > > your fq. hostname > > host localhost > > > > # The distinguished name of the search base. > > base dc=test,dc=example,dc=com > > > > # this could be your anonymous-bind substitute later.. > > #binddn cn=pam,dc=test,dc=example,dc=com > > #bindpw another_secret > > > > # The distinguished name to bind to the server with > > # if the effective user ID is root. Password is > > # stored in /etc/ldap.secret (mode 600) > > rootbinddn cn=Manager,dc=natter,dc=itellium,dc=net > > > > nss_base_passwd dc=natter,dc=itellium,dc=net?sub > > nss_base_shadow dc=natter,dc=itellium,dc=net?sub > > nss_base_group dc=natter,dc=itellium,dc=net?sub > > > > =================== > > > > then I called YaST -> Nw -> LDAP-Client > > > > (x) use LDAP > > > > Addresses of LDAP Servers > > localhost > > > > LDAP base DN > > dc=test,dc=example,dc=com > > > > [Advanced Configuration] <= choose this one! > > > > --------------------------------------------------------------- > > > > check > > > > [x] Create Default Configuration Objects > > > > > > => Continue > > (enter the rootdn password ) and you're done. > > > > > > puh.. it's a lot to write.. > > > > I hope this helps.. > > > > Markus > > > A Millliion thx... > WIll try tonight... > > Jerry > > good luck.. ;) Markus

1 0

1280x800 WXGA on SuSE 9.3
by NSK 23 May '05

23 May '05

Hi, I am trying to set up SUSE Pro 9.3 to work with the TFT WXGA 1280x800 (16:10) screen of an Acer TravelMate 2303 laptop. The problem is that although I configure X to use 1280x800 via SaX2, KDE (and GNOME) start in 1024x768. I once managed to make KDE work at a physical resolution of 1024x768 with a virtual resolution of 1280x800, but of course this is not what I want. Because the screen is 16:10 and 1024x768 is 4:3, whatever is shown on the screen under SUSE is distorted and reading is not comfortable. SaX2 does not seem able to solve my problem, and xf86config does not include 1280x800 resolution in its resolution selection menu. Therefore I should edit /etc/X11/xorg.conf manually. I posted my /etc/X11/xorg.conf if you want to see it: http://nsk.wikinerds.org/blog/index.php?p=160 If it of any relevance, during the initial installation of SUSE I chose the 1024x768 resolution from the menu, because there was no 16:10-compatible resolution available in the menu. The graphics card is 32MB. I don't know the screen's horizontal and vertical refresh rates. -- NSK http://portal.wikinerds.org

5 4

Re: [SLE] SUSe 9.3 and LDAP Docu?
by Markus Natter 23 May '05

23 May '05

On 5/23/05, Markus Natter <markus.natter(a)gmail.com> wrote: > On 5/23/05, Jerry Westrick <jerry(a)westrick.com> wrote: > > On Monday 23 May 2005 09:29, Markus Natter wrote: > > > On 5/22/05, Jerry Westrick <jerry(a)westrick.com> wrote: > > > > Is there a step by step docu on > > > > how to get SuSE 9.3 to use openldap > > > > for authorization.... > > > > > > > > I worked my way through the Admin Guide... > > > > but All I get is connection failures.... > > > > > > > > anybody seen a decent how to? > > > > > > > > Jerry > > > > > > > > > > > > > > > > > > > > -- > > > > Check the headers for your unsubscription address > > > > For additional commands send e-mail to suse-linux-e-help(a)suse.com > > > > Also check the archives at http://lists.suse.com > > > > Please read the FAQs: suse-linux-e-faq(a)suse.com > > > > > > Hi Jerry, > > > > > > YaST could do this for you ( see chapter 29.5 SuSE Admin. Guide ).. > > > but on the other hand you need a working LDAP - configuration and and > > > a working database first. > > > > > > Have you already tried to connect and made a successful request with any > > > cmd-line ldap tools ( ldapsearch ... ) or any ldap client? > > > > > > > > > Markus > > Thanks for the answer Markus... > > > > Yes I got ldap running by following the instructions > > at /usr/share/doc/packages/openldap2/admin-guide/quickstart.html > > > > > > There I issued: > > > > ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts > > ldapadd -x -D "cn=Manager,dc=<MY-DOMAIN>,dc=<COM>" -W -f example.ldif > > ldapsearch -x -b 'dc=example,dc=com' '(objectclass=*)' > > > > all of which worked. > > > > I guess is that either the User (as setup by quick installation guide) is not > > yast compatible, or that the security method is not the one that yast > > expects? > > > > Jerry > > > > > > > > > > > > > > > > > > well, > there could be some caveats.. > > could you post your /etc/openldap/slapd.conf & /etc/ldap.conf? (e.g. > did you include the required .schema files, like > yast.schema [as I remember, yast uses member entries instead of > memberUID per default (you could change this behavior-> extended > settings)..]) > > the idea behind this all is, that yast would help you setting up the > other configs correctly.. > (some hints: /etc/pam.d, nss_ldap / pam_ldap, /etc/security, > /etc/nsswitch.conf ) > > another idea is to let yast create the standard objects etc.. [ > extended settings ], if your > setup does not fit into the yast expectations. > And also try one thing after another.. [ e.g. do not start with > TLS/SSL related stuff > before you have fixed the other problems ] > > Markus > well I just tried this by setting up a very simple base.. (only the root-dir, and configured a rootdn and rootpw using slapadd, for setting things up.. then I configured a basic /etc/ldap.conf to point to the new slapd running on the localhost) and yast configured the rest for me.. it was not that difficult.. here are the lines I used for this test: /etc/slapd.conf: ============ # this should be the schema section as it was shipped.. include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/rfc2307bis.schema include /etc/openldap/schema/yast.schema suffix "dc=test,dc=example,dc=com" rootdn "cn=Manager,dc=test,dc=example,dc=com" # Cleartext passwords, especially for the rootdn, should # be avoid. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. rootpw secret base.ldif ( note: be careful with empty spaces at the end of a line, if you copy/paste! ) ======= ## ## TEST.EXAMPLE.COM ## ## Basis of the LDAP-tree test.example.com ## dn: dc=test,dc=example,dc=com dc: test o: example objectClass: organization objectClass: dcObject structuralObjectClass: organization ======= install this ldiff.. you should remove your old database before that.. please, keep your DB_CONFIG!!! rcldap stop cd /var/lib/ldap rm *.bdb log.* __db.* cd /etc/openldap/ # or wherever your base.ldif is slapadd -p -w -l base.ldif rcldap start /etc/ldap.conf ========== # Your LDAP server. Must be resolvable without using LDAP. # if you want tls / ssl later on, you should replace localhost with your fq. hostname host localhost # The distinguished name of the search base. base dc=test,dc=example,dc=com # this could be your anonymous-bind substitute later.. #binddn cn=pam,dc=test,dc=example,dc=com #bindpw another_secret # The distinguished name to bind to the server with # if the effective user ID is root. Password is # stored in /etc/ldap.secret (mode 600) rootbinddn cn=Manager,dc=natter,dc=itellium,dc=net nss_base_passwd dc=natter,dc=itellium,dc=net?sub nss_base_shadow dc=natter,dc=itellium,dc=net?sub nss_base_group dc=natter,dc=itellium,dc=net?sub =================== then I called YaST -> Nw -> LDAP-Client (x) use LDAP Addresses of LDAP Servers localhost LDAP base DN dc=test,dc=example,dc=com [Advanced Configuration] <= choose this one! --------------------------------------------------------------- check [x] Create Default Configuration Objects => Continue (enter the rootdn password ) and you're done. puh.. it's a lot to write.. I hope this helps.. Markus

1 0

SuSE 9.3 installation on IBM x345
by Dan Soare 23 May '05

23 May '05

Hi, I've unsuccessfully tried to install SuSE 9.3 on an IBM x345 server. After the packages were installed and SuSE made a reboot, the machine hangs with the message: "Kernel (hd0,0)/vmlinuz root=/dev/sda3 vga=0x317 selinux=0 acpi=off resume=/dev/sda2 splash=silent [ Linux bzImage, setup=0x1600, size=0x17685b ]" No other kernel messages, nothing. My hardware: IBM x345 (2CPUs) with IBM ServeRAID 5i (1 RAID5 array) Partitions: /dev/sda1 /boot (ext2) /dev/sda2 swap /dev/sda3 / (reiserfs) Bootloader: GRUB 1. I start the rescue system from the dvd and could access the partitions (rw). 2. I started a "new installation", then cancel the installation and then boot installed system. The system comes up without any errors, so I could finish the installation. 3. I already tried the smp, bigsmp and the default kernel with same result; guess the problem is not the kernel rather the bootloader or the initrd. 4. I also "reconfigured" the initrd (registered scsi or/and raid modules in /etc/sysconfig/kernel and started mkinitrd) which brought however nothing. 5. I run for at least 6 months on identically constructed servers SuSE 9,0 (2.4.21), 9,1 (2.6.5) and 9,2 (2.6.8) without any problems. I'm a newbie so I'm out of ideas. Thanks in advance Dan P.S. Sorry about my English.

2 2

SuSE 9.3 Pro 5 CD ISO set
by Bill M. 23 May '05

23 May '05

I want to thank whoever posted the address of the site that has the 5 SuSE 9.3 Pro CD images available for BitTorrent access. BitTorrent is new to me and I've set my Windows XP laptop to use the torrent (and make my downloaded data available for others to download) -- I now have the 5 CD ISO images on my machine. The MD5Sums correspond to the sums listed on the website ( http://www.interknet.net/bt/?torrent=suse93 ). Great! My question is: how do I know that these are authentic, unaltered SuSE distribution CDs? How do I know if these images haven't been tampered with and that the tampered MD5Sums have been included? Of course I verify that posted sum correctly. Please... don't get me wrong, I'm very appreciative that this individual has made this available as a shared resource for us SuSE Linux fans. How do I trust these images? That they don't have an embedded root kit or something else installed? Overly paranoid? Thanks in advance for your comments/feedback. -*-Bill

5 5

9.3 Live, problem with my Prism WLAN adaptor
by Sean Rima 23 May '05

23 May '05

Hello suse-linux-e, I have a Fujitsu-Siemens Amilo L1300 laptop with a ethernet port and a Prism WLAN Wifi as well. I booted the live disk and it seemed to detect both cards okay. In fact the ethernet card worked perfectly. However I could not logon onto my WIFI router. It is currently set to open as there are no security problems with that as I live in a very rural area. However in dmesg I get the following message for it: PRISM54: requested_firmware(): failed for 'isl3886' ETH0: could not upload firmware ('isl3886') ETH0: ISLPCI-reset: failure I had to copy these as I have a Draytek miniVigor USB ISDN PC with the laptop, I am getting a Cisco 801 TA to plug into the router next week. I use the laptop a lot away from home and use various paid/free hotspots around the country and therefore need wifi. Is there a solution to this, will it work with the full version or does Linux not support the Prism WLAN as yet Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie(a)jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped

1 0

time & filesystem problem(s?)
by Dave Howorth 23 May '05

23 May '05

I have a problem I don't understand on a new Opteron box running 9.2. I have two supposedly identical boxes and one is running fine whilst the clock on the other drifts into the future (2 days as of this morning). This morning I've also discovered that the root filesystem has become read-only over the weekend. I don't know whether these symptoms are caused by the same problem or if they are two separate problems? I don't really know where to look. I have ntp running on both machines and that seems like a candidate for the source of the clock trouble at least. The daemon still seemed to be running: ntp 4440 1 0 May19 ? 00:00:00 /usr/sbin/ntpd -p /var/lib/ntp/var/run/ntp/ntpd.pid -u ntp -i /var/lib/ntp I rebooted and /var/log/messages now contains: May 25 04:56:23 suse2 kernel: Losing some ticks... checking if CPU frequency changed. May 23 10:59:01 suse2 ntpdate[4434]: step time server 10.1.0.0 offset -Ã¾|1000Â°^E:Â°9414735363.521992 sec May 23 10:59:01 suse2 ntpd[4439]: ntpd 4.2.0a(a)1.1190-r Wed Jan 26 17:35:54 UTC 2005 (1) May 23 10:59:01 suse2 ntpd[4439]: signal_no_reset: signal 13 had flags 4000000 May 23 10:59:01 suse2 ntpd[4439]: precision = 1.000 usec May 23 10:59:01 suse2 ntpd[4439]: Listening on interface wildcard, 0.0.0.0#123 May 23 10:59:01 suse2 ntpd[4439]: Listening on interface wildcard, ::#123 May 23 10:59:01 suse2 ntpd[4439]: Listening on interface lo, 127.0.0.1#123 May 23 10:59:01 suse2 ntpd[4439]: Listening on interface eth0, 192.168.1.2#123 May 23 10:59:01 suse2 ntpd[4439]: Listening on interface eth1, 10.11.0.1#123 May 23 10:59:01 suse2 ntpd[4439]: Listening on interface eth2, 192.168.4.2#123 May 23 10:59:01 suse2 ntpd[4439]: kernel time sync status 0040 May 23 10:59:01 suse2 ntpd[4439]: frequency initialized 0.000 PPM from /var/lib/ntp/drift/ntp.drift May 23 10:59:01 suse2 kernel: warning: many lost ticks. May 23 10:59:01 suse2 kernel: Your time source seems to be instable or some driver is hogging interupts /var/log/ntp has this (and similar for each previous boot): 23 May 11:02:39 ntpd[4439]: synchronized to LOCAL(0), stratum 10 23 May 11:02:39 ntpd[4439]: kernel time sync disabled 0041 23 May 11:03:51 ntpd[4439]: kernel time sync enabled 0001 and ntpq -p says this: suse2:/var/log # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) LOCAL(0) 10 l 67 64 377 0.000 0.000 0.001 server1.lmb.int 131.111.12.21 3 u 11 1024 377 0.001 -272394 163702. The clock on this machine is about ten minutes fast around 40 minutes after I rebooted. I don't have a clue what all the output above actually means. I'm reading through all the NTP docs, but that's going to take me a while :) Can anybody give me any clues where to start looking? A disk error appears to be another possibility for the ro file system. Here's the last part of /var/log/messages before the reboot: May 25 02:26:24 suse2 -- MARK -- May 25 02:57:04 suse2 -- MARK -- May 25 02:59:34 suse2 /usr/sbin/cron[22122]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) May 25 03:28:42 suse2 -- MARK -- May 25 03:59:36 suse2 /usr/sbin/cron[22245]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) May 25 04:14:36 suse2 /usr/sbin/cron[22283]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.daily) May 25 04:17:11 suse2 su: (to nobody) root on none May 25 04:17:11 suse2 su: pam_unix2: session started for user nobody, service su May 25 04:17:46 suse2 su: pam_unix2: session finished for user nobody, service su May 25 04:17:46 suse2 su: (to nobody) root on none May 25 04:17:46 suse2 su: pam_unix2: session started for user nobody, service su May 25 04:17:12 suse2 su: pam_unix2: session finished for user nobody, service su May 25 04:17:47 suse2 su: (to nobody) root on none May 25 04:17:47 suse2 su: pam_unix2: session started for user nobody, service su May 25 04:17:47 suse2 su: pam_unix2: session finished for user nobody, service su May 25 04:20:25 suse2 kernel: scsi0:0:0:0: Attempting to abort cmd 0000010004851040: 0x2a 0x0 0x0 0x41 0x3a 0x16 0x0 0x0 0x8 0x0 May 25 04:20:25 suse2 kernel: scsi0: At time of recovery, card was not paused May 25 04:20:25 suse2 kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< May 25 04:20:25 suse2 kernel: scsi0: Dumping Card State at program address 0x24 Mode 0x0 May 25 04:20:25 suse2 kernel: Card was paused May 25 04:20:25 suse2 kernel: HS_MAILBOX[0x0] INTCTL[0xc0]:(SWTMINTEN|SWTMINTMASK) May 25 04:20:25 suse2 kernel: SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) May 25 04:20:25 suse2 kernel: SCSISIGI[0x0]:(P_DATAOUT) SCSIPHASE[0x0] SCSIBUS[0x0] May 25 04:20:25 suse2 kernel: LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0] May 25 04:20:25 suse2 kernel: SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x0] SEQINTCTL[0x0] May 25 04:20:25 suse2 kernel: SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] SSTAT0[0x0] SSTAT1[0x8]:(BUSFREE) May 25 04:20:25 suse2 kernel: SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) May 25 04:21:09 suse2 syslogd: /var/log/warn: Input/output error May 25 04:20:25 suse2 kernel: LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] May 25 04:21:09 suse2 kernel: LQOSTAT1[0x8]:(LQOSTOPI2) LQOSTAT2[0xe1]:(LQOSTOP0|LQOPKT) May 25 04:21:09 suse2 kernel: May 25 04:21:09 suse2 kernel: SCB Count = 32 CMDS_PENDING = 1 LASTSCB 0x10 CURRSCB 0x2 NEXTSCB 0xff80 May 25 04:21:09 suse2 kernel: qinstart = 36187 qinfifonext = 36187 May 25 04:21:09 suse2 kernel: QINFIFO: May 25 04:21:09 suse2 kernel: WAITING_TID_QUEUES: May 25 04:21:09 suse2 kernel: Pending list: May 25 04:21:09 suse2 kernel: 2 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] May 25 04:21:09 suse2 kernel: Total 1 May 25 04:21:09 suse2 kernel: Kernel Free SCB list: 16 1 21 25 0 10 6 27 15 17 14 5 9 13 3 26 18 28 4 22 11 31 12 19 30 23 24 20 29 8 7 May 25 04:21:09 suse2 May 25 04:21:09

1 0

Importing a certificate
by David Bottrill 23 May '05

23 May '05

I have a free X509 certificate from www.cacert.org, which I have sucessfully imported into Firefox. From Firefox I've exported the cert as a PKCS#12 backup file. I then used KDE Control Centre (Crypto applet) to import the certificate bundle which works OK, it asks if I want to use the certificate for email signing I say yes and it opens Kleopatra which asks for the passphrase and then complains that it can't decrypt the certificate. Any ideas ? David -- David Bottrill david(a)bottrill.org www.bottrill.org Registered Linux user number 330730 Internet SIP Phone: 1-747-244-2699

1 0

xorg-x11-server rpm verification problem
by Kastus 23 May '05

23 May '05

Hi, Just upgraded 3 machines from 9.2 to 9.3 and encountered a problem with mode of /usr/X11R6/bin/Xorg file on two of them. For some reason SUID bit was missing in the mode and X obviously was failing to start for a regular user. "rpm -V xorg-x11-server" reported no errors. I added SUID bit with command "chmod u+s /usr/X11R6/binXorg" on one machine and after that rpm verification complained that expected mode should be 4711 and it was 4744. OK, chmod again and rpm -V was happy on that machine. On another machine mode of /usr/X11R6/bin/Xorg was 711, after I changed it to 4711, rpm -V complains: rpm -V xorg-x11-server ..?..... /usr/X11R6/bin/Xorg /usr/X11R6/bin/Xorg should be root:root 0711. (wrong permissions 4711) ls -l /usr/X11R6/bin/Xorg -rws--x--x 1 root root 1847788 2005-03-22 09:33 /usr/X11R6/bin/Xorg At the same time, dump of xorg-x11-server rpm reports expected file mode 0100711: rpm -q --dump xorg-x11-server | grep bin/Xorg /usr/X11R6/bin/Xorg 1847788 1111512809 e68e9893c356e15f9ee08a87e01788a5 0100711 root root 0 0 0 X I tried rebuilding rpm db on the second machine but it made no difference. Can anybody explain what's going on here? Why rpm dump reports correct mode of the file matching mode on the file system and rpm -V reports an error contradicting rpm dump? I am using reiserfs 3.6 if it matters. Thanks, -Kastus

1 0

SUSe 9.3 and LDAP Docu?
by Jerry Westrick 23 May '05

23 May '05

Is there a step by step docu on how to get SuSE 9.3 to use openldap for authorization.... I worked my way through the Admin Guide... but All I get is connection failures.... anybody seen a decent how to? Jerry

2 1