Re: SL errors with scim_bridge_client
On Tue, Feb 3, 2009 at 2:29 AM, Craig Moore wrote: > I hope this is the right forum for this. I'm having a major problem with > Scientific Linux. I believe the problem may be due to scim_bridge im > agent but I am not sure. It seems that if I try to run any GUI programs > like: firefox, gedit, gthumb, etc... I get warning/error messages like > the following: > $ rpm -q scim-bridge.x86_64 > scim-bridge-0.4.5-8.el5.x86_64 > > $ rpm -q scim-bridge-gtk.x86_64 > scim-bridge-gtk-0.4.5-8.el5.x86_64 > > $ rpm -q scim-bridge-gtk.i386 > scim-bridge-gtk-0.4.5-8.el5.i386 > --- > I've no idea if there is any other information which might be useful. If > so, then please let me know. I would really, really appreciate any help > you can provide. You have both x86_64 and i386 versions of scim-bridge-gtk. Try removing the i386 one. Or, do you really need scim-bridge? Try removing scim-bridge-gtk and scim-bridge and see if that stops the errors. Another suggestion is to ask in the scim forums at http://www.scim-im.org/forums . It seems to be quite active, so you'd have a better chance to get answers. Akemi
Re: samba on SL5
Hi Devin, Wouldn't it be best to run SAMBA on the machines that actually have the disks? regards, Stephen. On Tue, 3 Feb 2009, Devin Bougie wrote: On Feb 3, 2009, at 4:10 PM, Dr Andrew C Aitchison wrote: On Tue, 3 Feb 2009, Devin Bougie wrote: Hi, All. We are using samba on an SL5.2 server to share filesystems with our Windows systems. Everything works properly when sharing a filesystem that is local to the samba server. When sharing an nfs filesystem, however, we see locking issues with *some* file types. Which kernel are you using on the *NFS* server ? We had NFS locking issues with the kernel shipped with SL5.2 and some of the updates. We don't seem to get them with 2.6.18-92.1.22.el5 It may be that your macs don't see the problem because they are being less picky with the locks. We see the same problem with all of the NFS shares we've tried, and none of the NFS servers are running SL5. One is Solaris 10, one is SL4 with the 2.6.9-67.0.1.ELsmp kernel, and several are SL3 with the 2.4.21-37.EL.XFSsmp kernel. If anyone else is serving nfs shares over samba on SL5 and isn't seeing this problem, I would be very grateful for a glimpse of your smb.conf file. If anyone is curious, I would be happy to provide ours. Many thanks for the reply, Devin For us the broken locking made mutt very unhappy with an NFS mounted /var/spool/mail but we found no problems with pine. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge a.c.aitchi...@dpmms.cam.ac.uk http://www.dpmms.cam.ac.uk/~werdna -- /+-\ |Stephen J. Gowdy | CERN Office: 8-1-11| |http://cern.ch/gowdy/| CH-1211 Geneva 23| | | Switzerland | |EMail: go...@cern.ch | Tel: +41 76 487 2215 | \+-/
Re: samba on SL5
Hi Stephen, On Feb 4, 2009, at 3:36 AM, Stephen J. Gowdy wrote: Wouldn't it be best to run SAMBA on the machines that actually have the disks? Our home disk server is currently running Solaris 10. When we moved the home disks from an Alpha running Tru64 to this new Sun box, our Solaris Admin attempted to get Samba running on the Solaris box. Of course I don't know the details, but he was never able to make it work. He is no longer employed by the lab and was our sol "Solaris admin" (with many years of experience supporting Solaris), so I am not hopeful about making Samba work when he couldn't. Moreover, until we get the home disks migrated over to a linux server (who knows when we'll have time for that), we are inclined to touch the current home disk server as little as possible. After moving our home disks from the aging Alpha to the Sun box, we continued to make the home disks accessible over Samba using the Alpha (which accessed the disks over NFS). This Alpha recently died, prompting us to finally move the samba service over to linux. In addition, we were hoping to limit the proliferation of Samba servers by having a single "samba" server that users could browse to for access to all of the required unix filesystems. Unless there are any other suggestions, we will move the samba service to an SL4 box where everything just works (using the same smb.conf as on SL5). Thanks, Devin
Reminder: Java update tonight
Hello, We are pushing out a security update for java tonight. We are only going from java 1.6.0-10 to 1.6.0-12, so there isn't to much of a problem with incompatibilities. But there are some people who have several version's of sun's jdk installed, and when you update one, it uninstalls the rest. So if you have multiple copies of jdk installed, and you plan on keeping them, then you should exlude it in your yum cron exludes line, or on your yum.conf excludes line. To exclude jdk and java-1.6.0-sun-compat for the nightly automatic updates. Edit the file /etc/yum.d/yum.cron.excludes and append to it, all on one line. so it looks like exclude=kernel* openafs* jdk java-1.6.0-sun-compat To exclude jdk and java-1.6.0-sun-compat for all yum update. Edit the file /etc/yum.conf and add the line exclude=jdk java-1.6.0-sun-compat Hopes this helps some people. Most people won't have any problem with the update, but I just wanted to make sure for the others. One other note. We were able to sign the i586 jdk rpm, but not the x86_64 one. The x86_64 one still breaks when you sign it. Thanks Troy -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LCSI/CSI DSS Group __
