January 2005 - openSUSE Users - openSUSE Mailing Lists

Wacom Graphire 2 (USB) on SuSE9.1?
by Frits Wüthrich 04 May '05

04 May '05

I can't get my graphical tablet to work on my new SuSE. On SuSE8.1 it was useable as an USB wheel mouse, but on 9.1 there is no movement visible of the cursor when I choose one of the USB mice. How can I fix this? -- Frits Wüthrich

4 7

POP3 Server start?
by Keith 03 May '05

03 May '05

I installed the imap RPM that comes with SUSE 9.1 Pro. How do I setup & start the pop3 server so people can log in and download their mail? I have gone through YAST and SYSV Level editor and I can't find anything. I used to use dovecot on FC3 so that is my reference point for running a mail server on Linux.

8 11

Slow partition: how to check?
by Pieter Hulshoff 11 Apr '05

11 Apr '05

Hello all, hdparm tells me that one of my partitions is really slow. While hda3 for instance gives me about 40-50 MB/s, hda4 only gives 4-8 MB/s. hda4 is part of a RAID partition together with hdc4. While hdc4 also gives about 40-50 MB/s, hda4 appears to be very slow. Does anyone know what might cause this, and how I might check or correct what is wrong? Regards, Pieter Hulshoff

9 35

SLES9: how to recognize SCSI LUNs >= 8?
by Michael Behrens 07 Apr '05

07 Apr '05

Hi all, does anybody know how i can make the SLES9 to recognize SCSI LUNs >= 8? I have set up a SLES9 (for IA64 architecture) on a DELL 1850 hardware, which has to be connected to a HP EVA3000 SAN via two Qlogic HBAs ql2342. The shipped drivers for the Qlogic HBAs work fine, I'm just not able to recognize virtual disks presented with LUNs >= 8, which I think is due to the module scsi_mod. I tried the parameters "max_luns=128" and "max_reported_luns=128" for module "scsi_mod" both in /etc/modprobe.conf.local and in /boot/grub/menu.lst, but still only LUNs < 8 are recognized by the driver. The qla2*-Modules don't seem to have any options regarding # of LUNs. The HBA's BIOS is configured to see 128 LUNs. It is a fresh installation with all the latest updates from Suse as of 20.1.2005. /proc/cmdline contains: root=/dev/sda6 max_luns=128 max_report_luns=128 vga=0x317 selinux=0 console=tty0 resume=/dev/sda2 elevator=cfq splash=silent -- Regards Michael

3 3

ULB GNOME 2.8.0.2
by James Ogley 05 Apr '05

05 Apr '05

Available today: ULB GNOME 2.8.0.2 This is a minor revision, not a full desktop upgrade. It includes netapplet, the seriously cool network switcher, as well as updated gnome-vfs2 and libgnome packages to use Firefox as the default browser, cos I've just fallen in love with it over the last few months - so it now depends upon SuSE's MozillaFirefox package (from the mozilla apt component) (Note: built for SuSE 9.1) -- James Ogley james(a)usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms

2 4

Re: [SLE] ntop
by matice＠nic.fi 25 Mar '05

25 Mar '05

yep it is > On Sunday 16 January 2005 3:07 pm, matice(a)nic.fi wrote: > > i attempted to reinstall then i got the following error (there shouldnt > > have been probs with user rights because it worked for a while) > > > > > > Starting service ntop /usr/sbin/rcntop: line 69: 11818 Segmentation > > fault sudo -u $NTOP_USER /usr/sbin/passcheck > > > > ntop admin password is not yet set. Run > > ntop -A -u wwwrun > > manually > > unused > > > > > > it complains that i need to manually assign the pass and so i have done > > but i keep getting the same error message, > > > > Make sure that wwwrun is set as the NTOP_USER in /etc/sysconfig/ntop > > Scott > > -- > POPFile, the OpenSource EMail Classifier > http://popfile.sourceforge.net/ > Linux 2.6.8-24.10-default x86_64 > > -- > 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 > >

3 7

win2000/suse
by a.garcia＠imb.uq.edu.au 21 Mar '05

21 Mar '05

I am running win2000 and suse 9.1, it works fine. My win2000 is on a fat partition. suse mounts it automatically, and I can read this partition but I can not writte to it, how can I get this to automatically mount it (the way it is in the moment) and at the same time it allows any user to writte in to that partition? my fstab is /dev/hda1 / reiserfs acl,user_xattr 1 1 /dev/hda3 /windows/C vfat defaults 0 0 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid$ /dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev$ thanks in advance

7 7

Deployment problem of tomcat5.0.27
by manoj＠in.effectsoft.com 16 Mar '05

16 Mar '05

Hello all, I faced following problem when deploying my web application using build.xml, if any one knows the reason please reply. BUILD FAILED: D:\eilnet\build.xml:116: FAIL - Encountered exception java.io.IOException: java.lang.IllegalStateException: Context path /eilnet is already in use. Regards - Manoj

21 42

SuseFirewall2 or IPTables, is there a difference
by Colin Murphy 23 Feb '05

23 Feb '05

Recent events have made me think about firewalls. What is the difference between SuseFirewall2 and the firewalls found in other distros - which I am assuming are referred to as IPTables. Thanks again. -- Colin(a)SpudULike.me.uk As seasons go I especially like pepper.

15 33

Re: [SLE] Time synch problem
by Carlos E. R. 23 Feb '05

23 Feb '05

El 2003-07-09 a las 13:37, C Hamel escribió: (You forgot to post to the list) > I am afraid I don't even know how to ask a question, at this point, but I'll > make an attempt: Exactly where should this ntp thing be called to set the > clock ...or(/and) by what process? It is a very proper question :-) Well, it depends. There are two ways. If your computer is up all the time, and has a permanent network connection, you can use the ntpd daemon, which polls a set of servers about once a minute, and _very_ slowly adjusts the system clock; it can even note the systematic error or drift, and take that in to account to discipline the system clock. There are many options available for the daemon: see full doc in: http://localhost/usr/share/doc/packages/xntp-doc/html/index.htm Or, you may have a temporary network connection, like I do; I will explain this in some detail. We can adjust the clock to "internet" time, once, sometime after we connect to internet. This, apparently, can be done with the daemon, using some option I don't fully understand. Or we can use ntpdate - a program which is to disappear some time in the future, but that I use, and SuSE uses as well in its own script. For this, we can simply call "/etc/init.d/xntpd ntptimeset" - and assume that when "ntpdate" finally disappears SuSE will adjust the script appropriately ;-) Of course, /etc/ntp.conf has to be configured; at least, it must have a list of servers: server IP_address server name_address This is sufficient for "xntpd ntptimeset" to work; just leave the rest of the config at the default values. If you want to use the daemon, then I'm not the person to ask :-) Ok, so when is the appropriate time to make this time adjust? Well, ideally, during system boot-up, after network connection is established. This is done properly by the service xntpd, if enabled. The SuSE script "/etc/init.d/xntpd start" does first a clock set using ntpdate, if the variable XNTPD_INITIAL_NTPDATE is set to "AUTO". Then, it starts the daemon to keep time synchronized. And, if our network connection is not permanent? Then, the script "/etc/ppp/poll.tcpip", which is called from "/etc/ppp/ip-up", will adjust the clock first thing: assuming we have some servers configured, it will be done every time we connect to internet with the modem. I do it differently, only once every five times, and I also update the hwclock. The danger of this method is that the clock might suddenly go forward or backward a bit (seconds or hours, it depends): not very nice on a *nix system, but we can not avoid it. More details to be aware of: what happens to the hardware or CMOS clock? Well, the script "/etc/init.d/boot.clock" (read it, it is documented) does this sequence of things (using the command "hwclock") before starting system services: - Create if it doesn't exist, the file "/etc/adjtime" - Adjust hardware clock (CMOS) for known drift during the time the computer has been off; this depends on the previous file to work. - Copy CMOS clock (hardware) to system time (CPU and OS maintained). After this, the system goes fully up, and maybe, the clock is adjusted from the internet or by hand (danger!). But (and this is very different than windows) the CPU maintained clock has to be copied back to the CMOS, because the kernel doesn't do it. SuSE does it in the script "/etc/init.d/halt" that copies system time to hardware time just before power off. Me, I prefer to do it just after I adjust to network time, inside "ip-up.local", like this: /usr/sbin/rcxntpd ntptimeset /sbin/hwclock --systohc More things to be aware of: a common mistake is manually adjusting the system clock from kde control center (for example), and not updating the hwclock at the same time: the drift adjust algorithm of hwclock thinks that the CMOS clock is fast or slow by the same amount you adjusted the clock, and the next boot it will adjust the time by several hours... The solution is to delete "/etc/adjtime" and call "/sbin/hwclock --systohc" just then (documented on the SuSE sdb). Well, this has been enough chatter on my part; let's hope I didn't make many mistakes :-) -- Saludos Carlos Robinson

3 7