February 2007 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Simple appointment manager -- what do you use?
by Joachim Schrod 21 Feb '07

21 Feb '07

Hi, What do you guys use for a simple appointment or reminder manager? Nothing fancy; I'd like to input a date/time and get a popup or an email some time ahead that the appointment is up. Integration in email or some other personal information manager is not needed; in fact, I would prefer a standalone application since I use Emacs for mail and actually manage my appointments on another system. It's just that I don't want to forget the next telecon when I'm deeply buried in work. ;-) I.e., Evolution or Kontact are too heavy for my taste. iCal object support would be nice, but is not a must. I would prefer a GUI, but that is neither a showstopper. Up to now, I have used plan (http://www.bitrot.de/plan.html) for that task, but that has been thrown out of SUSE for some time. Before I install it manually again on a new system, I'd like to get some opinion about potential substitute applications. Thanks in advance for any opinions, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

10 16

[opensuse] Suse 10.2 + KDE 3.5.6 windows in KDE panel dissappeared
by Oliver König 21 Feb '07

21 Feb '07

Hello, all open programs (windows) used to be visible in the KDE panel (task bar). All of a sudden open programs are not visible anymore in the KDE panel. I clicked "Configure panel" > "Taskbar". Show windows from all desktops is checked [X]. What shall I do? Regards, -- Oliver König -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Suse 10.3 + KDE 3.5.6 windows in KDE panel dissappeared
by Oliver König 21 Feb '07

21 Feb '07

Hello, all open programs (windows) used to be visible in the KDE panel (task bar). All of a sudden open programs are not visible anymore in the KDE panel. I clicked "Configure panel" > "Taskbar". Show windows from all desktops is checked [X]. What shall I do? Regards, -- Oliver König -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] backup data from server
by Evan Ingram 21 Feb '07

21 Feb '07

Hi all I want to setup a backup system for a server where the data is backed up to my laptop which connects wirelessly on the network. There should be 1 day a week where it does a full backup and the other days just incrementals to a separate directory not affecting the full backup. I tried using a script i found called "simplebashbu", google that and you'll find it. It seemed like it should do what i wanted, but the incrementals didnt work. Nothing would be put in the tar's. The full backup would be ok. I don't know whether it was because the directories i was backing up were nfs mounted and the script didnt like it or something and is mainly meant for local directories. Any advice on a tool that will do what i want? thanks all ~Evan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

7 7

Re: [opensuse] Failure Trends in a Large Disk Drive Population [ Was: About Backing Up]
by Tom Peters 21 Feb '07

21 Feb '07

At 04:53 PM 2/20/2007 -0500, you wrote: >On 2/20/07, David Brodbeck <gull(a)gull.us> wrote: >>Stevens wrote: >> > Auto manufacturers try to predict how their interiors and their paints >> will >> > last, too, but until both are subjected to the Texas sun they are only >> >>Sure. As anyone who's ever had a couple of hard disks fail can attest, >>MTBF numbers are mostly fiction. > >I don't know about that, it is amazing how often disk drives fail >shortly after the warranty expires. > >Actually, the Google paper on this is very interesting. >http://216.239.37.132/papers/disk_failures.pdf I've rarely had a drive fail on me before I could get the data off it. I had a drive near to failure, yet still was able to order a replacement and transfer the data, before it became unusable. How? By using SmartMonTools http://sourceforge.net/projects/smartmontools/ Since using this, I have had no data loss at all. The old name of the project was SmartMonTools, I should be calling it S.M.A.R.T. now. ATA Drives, both serial and parallel (and most SCSI drives) have been self-monitoring and accumulating their own statistics and performance metrics, for the main reason of predicting failure, for decades. That's right, the drive itself monitors itself. You just need to get the data and schedule tests. But the only place most of us have ever heard of it is in the BIOS of many modern machines, where there's a single question as to whether you want it on or not. All THAT does in most cases is perform the most basic test (drive health check) that S.M.A.R.T. is capable of, and only when you boot. How often do you boot your Linux machines? I though so. On the other hand, if you have S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) the smartd daemon is continuously watching your drives for signs of failure, performing non-invasive tests every (insert your desired test frequency here) and logging any anomalies. I run short self-tests every night, and long ones on the weekend. This tool can "see" the individual drives on RAID cards from a limited group of cards: 3Ware, CCISS, Highpoint. I like being able to get stats on each drive, even though they are a single array. Works on many Firewire, USB and other drives that adhere to ATA/ATAPI-4, -5, -6, -7, and -8. Works on older drives too, but the information it returns is less useful. But that shouldn't be a problem unless your drives are more than a dozen years old, maybe even older than that. I think the ATA-4 spec dates from March of 1996. SmartMonTools runs on: Operating System: Cygwin (MS Windows), 32-bit MS Windows (95/98), 32-bit MS Windows (NT/2000/XP), All 32-bit MS Windows (95/98/NT/2000/XP), All BSD Platforms (FreeBSD/NetBSD/OpenBSD/Apple Mac OS X), All POSIX (Linux/BSD/UNIX-like OSes), FreeBSD, Linux, NetBSD, OS X, Solaris, Win2K, WinXP, IBM OS/2 License: GNU General Public License (GPL) [Huh?] Outside a photographer's studio: OUT TO LUNCH: IF NOT BACK BY FIVE, OUT FOR DINNER ALSO --... ...-- -.. . -. ----. --.- --.- -... tpeters(a)nospam.mixcom.com (remove "nospam") N9QQB (amateur radio) "HEY YOU" (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2" N by 88° 6' 28.9" W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Failure Trends in a Large Disk Drive Population [ Was: About Backing Up]
by Greg Freemyer 21 Feb '07

21 Feb '07

On 2/20/07, David Brodbeck <gull(a)gull.us> wrote: > Stevens wrote: > > Auto manufacturers try to predict how their interiors and their paints will > > last, too, but until both are subjected to the Texas sun they are only > > guessing. The North has salt that kills cars; in the South it is the sun. > > Only when they obtain empirical data can they be sure and that data takes > > a long time to gather. The same goes for optical media manufacturers. Any > > longevity rating is a SWAG, at best, which is the reason for my cynical > > view. > > > > Sure. As anyone who's ever had a couple of hard disks fail can attest, > MTBF numbers are mostly fiction. I don't know about that, it is amazing how often disk drives fail shortly after the warranty expires. Actually, the Google paper on this is very interesting. http://216.239.37.132/papers/disk_failures.pdf To grossly simplify, commodity disk drives fail at a rate of roughly 10% per year starting in the 3rd year, independent of activity, temperature, etc. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 6

[opensuse] Re: OpenSUSE updater
by Robert Lewis 21 Feb '07

21 Feb '07

In addition, why does it hang for a very long time at the end of an updater operation at 99%. In fact often it goes to 100% and then drops back to 99%. During this time top reports: 7222 root 25 0 82432 44m 6248 R 91.7 4.4 5:09.40 update-status That's 91.7% CPU utilization for a very very long time. This is ridiculous. Is it a race condition or what? I am hopeful that we don't get into a long email storm over this. I just am really looking for quality feedback from the developers that might result in some future good news. Keep it positive folks.. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

18 45

[opensuse] When will YOU respect protected status?
by Carlos E. R. 20 Feb '07

20 Feb '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have: xine-lib-1.1.4-1 xine-ui-0.99.4-1 compiled by me, and in protected state (keylock icon). However, Yast YOU wants to downgrade (!) to xine-lib 1.1.2-40.1! How come? :-/ When will Yast be taught manners and respect our orders? I even tell it to "keep" and it responds with a waring icon! How does he dare? :-/ My version is newer and with a bigger number than suse's! - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF2uW4tTMYHG2NR9URAtSfAJ0e4nHliMRwb2Y+8489uoT8/YKXuwCfbYGN pWF3hR3Jo3upyHytX64MP4s= =Lcbr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 5

[opensuse] X system random crashes
by Gary Gapinski 20 Feb '07

20 Feb '07

How should I pursue correcting the subject problem? This is an Opteron 175 DFI LANPARTY UT nF4 with dual XFX GeForce 6800 XT graphic adapters driving four monitors in Xinerama mode. Neither the motherboard or the graphic adapters are overclocked. Linux chipotle 2.6.18.2-34-bigsmp #1 SMP Mon Nov 27 11:46:27 UTC 2006 i686 athlon i386 GNU/Linux NVIDIA Driver Version: 1.0-9631 Xorg.0.log shows Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80cbf81] 1: [0xb7f5c420] Fatal server error: Caught signal 11. Server aborting (II) Screen 0 shares mem & io resources (II) Screen 1 shares mem & io resources (II) Screen 2 shares mem & io resources (II) Screen 3 shares mem & io resources (EE) NVIDIA(3): Failed to tear down DAC /var/log/messages shows Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0400 ffffffff 0000d938 00000000 ff211c1c Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 1, Channel 00000002 Method 00000000 Data 01047c01 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:33 chipotle kernel: NVRM: Xid (0002:00): 6, PE0002 0000 01047c01 00000000 00000000 00000000 Feb 11 08:30:35 chipotle kdm[4764]: X server for display :0 terminated unexpectedly The crashes are always associated with bus ID 2:0:0, which nvidia-settings identifies as GPU 1 (5:0:0 is GPU 0).) There are of course many more possibly pertinent files, but I'll wait for suggestions before posting long config files. Regards, Gary -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Postfix and clock weirdness.
by Carlos E. R. 20 Feb '07

20 Feb '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I just have seen something in the warn log and I'm investigating. See the detailed log: Feb 12 12:26:54 nimrodel postfix/local[29204]: ED7FE86F23: to=<cer(a)localhost.nimrodel.valinor>, relay=local, delay=62, status=sent (delivered to command: /usr/bin/procmail) Feb 12 12:26:54 nimrodel postfix/smtpd[29128]: connect from localhost[127.0.0.1] Feb 12 12:26:52 nimrodel postfix/smtpd[29126]: disconnect from localhost[127.0.0.1] Feb 12 12:26:52 nimrodel amavis[26348]: (26348-06-28) FWD via SMTP: <opensuse-es+bounces-6521-robin.listas... Notice the clock jumping back two whole seconds? Well, postfix gives notice: Feb 12 12:26:52 nimrodel postfix/qmgr[4707]: warning: backward time jump detected -- slewing clock ... Feb 12 12:27:34 nimrodel postfix/qmgr[4707]: warning: backward time jump recovered -- back to normality Now, why did the clock jump back two whole seconds? Is postfix adjusting the clock, or is it just noticing it? I'm using ntp, it shouldn't do that! But it does. See the xntpd log: 12 Feb 03:02:53 ntpd[4635]: offset -0.003808 sec freq 10.337 ppm error 0.010344 poll 10 12 Feb 03:03:28 ntpd[4635]: synchronized to 193.127.101.30, stratum 2 (here the system was suspended to disk, thus the lap, from 03:39 to 11:34) 12 Feb 11:35:45 ntpd[4635]: synchronized to 194.146.227.112, stratum 2 12 Feb 11:39:39 ntpd[4635]: synchronized to 193.225.14.163, stratum 2 12 Feb 11:49:13 ntpd[4635]: synchronized to LOCAL(0), stratum 10 12 Feb 11:52:47 ntpd[4635]: synchronized to 194.150.121.14, stratum 2 12 Feb 11:57:24 ntpd[4635]: offset 0.000000 sec freq 10.363 ppm error 0.122509 poll 10 12 Feb 12:26:52 ntpd[4635]: time reset -2.125240 s <====== 12 Feb 12:26:52 ntpd[4635]: system event 'event_clock_reset' (0x05) status 'leap_none, sync_unspec, 15 events, event_peer/strat_chg' (0xf4) 12 Feb 12:26:52 ntpd[4635]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_unspec, 15 events, event_clock_reset' (0xf5) 12 Feb 12:26:54 ntpd[4635]: peer 193.127.101.30 event 'event_reach' (0x84) status 'unreach, conf, 2 events, event_reach' (0x8024) Notice that it is almost one hour after wake up when ntp decides to jump the clock back by two whole seconds, instead of adjusting it slowly. Why? Supposedly, the suspend routines should restart ntp, but it is not happening. I have, in /etc/sysconfig/powersave/sleep: SUSPEND2DISK_RESTART_SERVICES="autofs slmodemd irda ntpd" Obviously, the service has not been restarted, but it was left in memory, thus the error on wake up. Why? How to force it to be stopped and restarted with suspend/wakeup? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF0FSytTMYHG2NR9URAo6lAJ0VeeNxZ3UiceCrmK1uNNQbGUT/YgCcCgAx br3nfp3dB2497EeNukj+JPs= =Y6Gl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 6