If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I swear, I think these people think computers work using pixies and elves, with the IT department being the magicians that wave our magic wands over it all to get them to work.
Reminds me of a sayng I used all the time. "My hourly rate for technical support is $xx.xx. If you insist it is magic, I charge $xxx.xx for miracles and charms.'
When we ran our own business for a month, it felt like I should have had a wand and a book of wierd scribbling, with the things people thought a 'technician' could fix.
If it is going to require a reboot when memory is low, and it's a random occurrence (but as a memory leak, it shouldn't be, those normally take some time to build up), then you could (at least I know how to do this on windows) run a memory detection algorithm that reboots the system if it's below, oh, 10% of total resources (that would be configurable of course, so if you wanted it to be 1%, it could be).
If I recall correctly, you should be able to set System Monitor/Performance Monitor/whateverit'scalled to monitor memory usage (definitely) and reboot the system (possibly builtin, or with some sort of script).
I get the "magic computermachine box" people, too. Unfortunately, some of them are in my technical college courses.
Since there seems to still be interest in the subject, I'll let you know that we've narrowed the server issue down to a bit of RAM going bad. It doesn't always fail, which made it so maddening to nail down. Now we just need to order some new in and do a little trail-and-error testing to figure out which unit has the bad section. Thanks for the advice anyway.
The Rich keep getting richer because they keep doing what it was that made them rich. Ditto the Poor.
"Hy kan tell dey is schmot qvestions, dey is makink my head hurt."
Hoc spatio locantur.
Heh, sure. I didn't mean to make light of the suckiness, just that I've run into memory leaks before. Glad it's something as simple as buying and installing new RAM though.
Dria: I was thinking along the lines of a .NET service that would poll memory useage every 1/2 hour or so. It does use the system monitor, but it does it behind the scenes. It wouldn't leak memory because it's managed, and it would take up very little space (assuming of course you've already got the .NET framework installed).
i'd say... if it happens a lot, you might want to just schedule a reboot for once a week, most likely when there's the least amout of users on the system.
since it doesn't sound like a 247 place, i'd suggest... first thing monday morning before they start work. might have to come in an hour or two early tho.
and yeah there's a possibility it won't work...but i figure... it can't hurt to try.
besides, i'm sure you have to back up your data sometimes too yes? why not do both at the same time...backup and then reboot?
why not do both at the same time...backup and then reboot?
Its a decently big system, so backups are done "live" and take around 36 hours per run. I run them every two days, starting as early as I can. I think we would be fine with a daily incremental setup, and only doing a full backup on the weekends, but the boss is paranoid for some reason, and want to do full backups each run. He signs my payslip, so I do what he wants. He has my input on the subject.
The Rich keep getting richer because they keep doing what it was that made them rich. Ditto the Poor.
"Hy kan tell dey is schmot qvestions, dey is makink my head hurt."
Hoc spatio locantur.
Comment