|  | | Re: Kde 4 version?
Jul 18 2009 on content K Raid Monitor |
debian stable is still on KDE3, so I do not know when I will port the whole stuff to KDE4.
I have a box with fedora and KDE4 though, so I might start porting actually before Debian hits KDE4.
Just need to get some time for it ... and two spare USB sticks to set up an array.
:( |
| | | Re: Re: Another update d
Jan 12 2008 on content K Raid Monitor |
Thanks for the bug report.
The detection is only run once at program startup, and only if you have not yet a file named ".kraidmonitor" in your home directory. And even then, it only looks for the first raid array it can find.
Adding other arrays is not so difficult that a full autodetection seems to be necessary. In other words: It's a feature, not a bug. ;)
Dang! Now it's done. I could as well get myself hired by Microsoft as chief of the weasel word department.
Joke aside, I know the program should be modified, but I don't have the time right now, and I fear I will not have time for several months to come.
I also plan to include the monitoring of raid arrays on remote computers (for my future home network :) ) and in that case autodetection would no longer be possible anyway. Then my 500 GB array which is currently connected locally will be moved to a server, but I still want to monitor the array. For everybody who will then also want to use this feature it will be manual configuration anyway. I think, providing documentation to how the syntax of the configuration file must look like is sufficient.
On the other hand, I wouldn't turn down any code which makes the program do what you suggest.
Porting to KDE4 is also on my to-do list, I hope they didn't break the API too badly. But for this to happen, I first need a working install of KDE4, and time is short these days (my holidays are over :( ).
If the people, who's only remaining roadblock to KDE4 adoption is the still-not-ported KRaidMonitor, send me a mail to remind me of their needs, I might find time and motivation to start porting right away. The address is:
gerald/dot/pichler/at/chello/dot/at
(the last "at" is to be written as is, I am from Austria and our country-domain is ".at") |
| | | Re: Re: Another update d
Jan 12 2008 on content K Raid Monitor |
Thanks for the bug report.
The detection is only run once at program startup, and only if you have not yet a file named ".kraidmonitor" in your home directory. And even then, it only looks for the first raid array it can find.
Adding other arrays is not so difficult that a full autodetection seems to be necessary. In other words: It's a feature, not a bug. ;)
Dang! Now it's done. I could as well get myself hired by Microsoft as chief of the weasel word department.
Joke aside, I know the program should be modified, but I don't have the time right now, and I fear I will not have time for several months to come.
I also plan to include the monitoring of raid arrays on remote computers (for my future home network :) ) and in that case autodetection would no longer be possible anyway. Then my 500 GB array which is currently connected locally will be moved to a server, but I still want to monitor the array. For everybody who will then also want to use this feature it will be manual configuration anyway. I think, providing documentation to how the syntax of the configuration file must look like is sufficient.
On the other hand, I wouldn't turn down any code which makes the program do what you suggest.
Porting to KDE4 is also on my to-do list, I hope they didn't break the API too badly. But for this to happen, I first need a working install of KDE4, and time is short these days (my holidays are over :( ).
If the people, who's only remaining roadblock to KDE4 adoption is the still-not-ported KRaidMonitor, send me a mail to remind me of their needs, I might find time and motivation to start porting right away. The address is:
gerald/dot/pichler/at/chello/dot/at
(the last "at" is to be written as is, I am from Austria and our country-domain is ".at") |
| | | Another update done!
Jan 9 2008 on content K Raid Monitor |
Everybody who has more than one raid array will be interested in this new release.
It now can handle any amount of locally mounted raid arrays.
Please test it and give me feedback if something does not work.
Have fun!
Gustl |
| | | mdadm, more arrays
Nov 6 2007 on content K Raid Monitor |
Well, getting the status of a raid array without root rights or resorting to inter-process communication stuff (which is way too complex for me) is not the hard part.
In the /sys/.. filesystem tree you can find a directory for each raid array, and inside that the status files for each partition of the array. So all my applet does, is to wake up on a timerEvent, look what is written in the status files, and display a green button when the status is OK, and a red button in all other cases. (And when the array is not found, the button is yellow). Then set the timer to wake up the applet again in 10 seconds.
And now for something completely different:
To support more than one array is definitely one of my goals, I just need to find the time to do it. After all, I then could delete this one line under "shortcomings" :) .
|
| | | Updates done :)
Nov 4 2007 on content K Raid Monitor |
Hi everyone,
v0.3 is here!
As this Sunday was a cold and foggy one, I sat down before my screen and added some of the requested features.
This should now be a better usable and configurable version, with no more need to write your own config file. |
| | | Re: Re: Re: Feedback please
Nov 4 2007 on content K Raid Monitor |
Using mdadm as backend was my first idea too. The problem with making KRaidMonitor a frontend for mdadm is, that mdadm is only available for root (or sudo). But I definitely wanted the tool to work for users without any previleges.
Allowing a user to mess around with mdadm seems to be quite dangerous, given the right type of user.
And making it a whole package with monitoring for users, and a sysadmin mode for managing the array is definitely out of my skill/time reach. |
| | | Thanks for the fish
Nov 4 2007 on content K Raid Monitor |
and the feedback. I actually might add some of the requested features.
I want to tell you the reasons why I programmed this tool:
I read a nice statement by a system administrator who said that the most common reason for data loss on a raid array is manual deletion (translation: plain stupidity ;) ), the second most reason is a disk failure which goes by undetected.
When I bought two 500 GB USB disks to store my digital photos on, I set them up as a raid-1 array. I use this machine as my daily work desktop, and I wanted to recognize a disk failure immediately. The mdadm tool can send me an email, but that was not an option for me, because I read them only once a day. The tool I wanted should notify me immediately and it should work as non-root and non-sudo. It should also take very little space on my kicker bar, but be prominent enough to not get overlooked in case of color change.
From these motivations and requirements stem the features:
* A monocolor button, half an icon wide (therefore: No, I will not use an icon)
* Color change from an unobtrusive dark green to a bright red in case of disk failure.
Feature requests I'd like to pick up:
* Adding of a tooltip.
* If no .kraidmonitor file is available, find the first available raid array and write the .kraidmonitor file.
* If no device is found, the button stays yellow.
* Configuration dialog.
I don't know about playing a sound, because when the machine is under heavy load (hugin), it sometimes happens, that the button switches to red for 10 seconds (would be quite annoying).
Maybe I should log all statuses which currently cause the button to turn red, without actually meaning that one disk is actually gone, and include these statuses into the "green" status. I am pretty much on trial and error here, so any specific tips, when the files in /sys/... change to what status would be welcome.
Also, of course, modifications of the source code are warmly welcome, as I am not a professional programmer by any means.
If anyone can give me a cookbook, walk-through, take-me-by-the-hand-and-drag-me tutorial about how to debug my code, I would be much more efficient. I know that I can start the beast in appletproxy, but that is about it. Currently I help myself by displaying the contents of interesting variables in info-boxes, which, to my opinion, is ingeniously brain-dead ;) . |
| | | Feedback please
Nov 1 2007 on content K Raid Monitor |
Could someone who tried this out please give some feedback to me?
Where are the shortcomings, where should the thing become better, does it not work for your raid array configuration, where did you have troubles?
gustl |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
| |
|
