That's too close to an answer the company would like to see to be bullshit. You'd be surprised how naive non-technical types are about new technology and/or mediums. A better bullshit answer would have been something cute like "My wife made me" or "The cover was pretty"
Note: I have never tried this before. Try it on a non-production machine first!!! you have been warned...
On the backup machine, write a script that repeatedly does the following actions:
1) mounts filesystem on shared disk read-only 2) if the mount fails becase of an inconsistency, skip to 9 3) checks the mdate of a file called/.watchdog 4) determines if "too long" a period has gone by since that
time... if not, go to 8 5) remounts the filesystem read-write 6) creates a file called "/.failover" 7) starts the application assuming the other computer has died, stops this script loop 8) umounts the filesystem 9) sleep for a short period of time 10) go back to 1
The main machine does the following things in a loop: 1) Update the date of/.watchdog 2) sleep for a short time (shorter than the one in the above loop) 3) Check for the existance of/.failover. If it exists, panic! This means the other machine decided to take over. Ideally you umount everything EXCEPT that disk and halt.
Now, a better idea might be something like this: Create a small partition on the disk (1 cylinder) in addition to the shared partition. Have the main machine write timestamps directly into the partition (date +%s >/dev/hdz3 or something). The backup machine would read that directly rather than trying to syncronize on a file (whose mtime will only be updated when the main machine's buffer cache is flushed to disk).
Also, you may want to consider some way to avoid needing a script loop on the host machine; a custom device driver that fits into Linux's watchdog timer framework is probably better.
1) Watch the user constantly over his/her shoulder, and keep a notebook.
2) Turn the program into a trampoline that emails the person every time they use it. Also, it gives you the Klez virus for redundancy and accountability.
3) Mope around for days until they give you Solaris with BSM.
4) Mope around for days some more and contemplate why you are replying to this AC.
Holy crap, don't say that. I love Space Ghost. I'll always remember that episode when he had Beck on... and towards the end he offered SG a taco that had been sitting on his dashboard. A not-so-subtle homage to that lo-fi classic, "Satan Gave Me a Taco". ^_^
I could appreciate the animators just having a good time. And the unsuspecting guests putting up with it.
I had a plan for about a week to make a cron/at replacement and call it "UniCRON" in your honor. I swear I'm totally friggin' serious. You're on my friends list too...
You can probably tell I wasn't really into transformers.
It depends on how hard you try to prevent the accidental access of the information. If you have been clearly trying hard to prevent the access, then you may have a case (legal recourse). However, I submit you this:
http://www.intentia.com/w2000.nsf/pages/ which is a link to all of the press releases, etc. Why this is publically accessable, I don't know. I just took the last part of a link on the frontpage off. I could do THAT just by mistyping. (It appears to be down now... the whole website maybe... oh well, slashdot strikes again).
If you visit http://www.intentia.com/w2000.nsf/pages/ you will see a list of all available documents that can go in the "frame", including press releases.
It took me 2 minutes to stumble on that, and Reuters probably did the same. How was Reuters to know what Intentia's "schedule" for releasing that document was? They probably bookmarked that index of PRs for quick reference some time ago, at recently saw something new, and publicized it.
How that constitutes "hacking" I do not understand. I put full blame on the webmaster.
Let him know what you think! webmaster@intentia.com
Slashdot Mirror
That's too close to an answer the company would like to see to be bullshit. You'd be surprised how naive non-technical types are about new technology and/or mediums. A better bullshit answer would have been something cute like "My wife made me" or "The cover was pretty"
Note: I have never tried this before. Try it on a non-production machine first!!! you have been warned...
/.watchdog
/.watchdog /.failover. If it exists, panic! This means the other machine decided to take over. Ideally you umount everything EXCEPT that disk and halt.
/dev/hdz3 or something). The backup
On the backup machine, write a script that repeatedly does the following actions:
1) mounts filesystem on shared disk read-only
2) if the mount fails becase of an inconsistency, skip to 9
3) checks the mdate of a file called
4) determines if "too long" a period has gone by since that
time... if not, go to 8
5) remounts the filesystem read-write
6) creates a file called "/.failover"
7) starts the application assuming the other computer has died, stops this script loop
8) umounts the filesystem
9) sleep for a short period of time
10) go back to 1
The main machine does the following things in a loop:
1) Update the date of
2) sleep for a short time (shorter than the one in the above loop)
3) Check for the existance of
Now, a better idea might be something like this:
Create a small partition on the disk (1 cylinder) in addition to the shared partition.
Have the main machine write timestamps directly into the partition (date +%s >
machine would read that directly rather than trying to
syncronize on a file (whose mtime will only be updated when
the main machine's buffer cache is flushed to disk).
Also, you may want to consider some way to avoid needing a script loop on the host machine; a custom device driver that fits into Linux's watchdog timer framework is probably better.
1) Watch the user constantly over his/her shoulder, and keep a notebook.
::Uncontrolled Sobbing::
2) Turn the program into a trampoline that emails the person every time they use it. Also, it gives you the Klez virus for redundancy and accountability.
3) Mope around for days until they give you Solaris with BSM.
4) Mope around for days some more and contemplate why you are replying to this AC.
5)
HOW DO THEY KNOW ABOUT THAT?!?!?!
Sometimes I get this eerie feeling that there are PEOPLE watching ME!
No.... ::blushes::
Funny story tho.
But if that _was_ me, I don't know whether I'd give you a hug in pity or hit you with a LART.
I'm from the Mid Atlantic, and we don't have many EBs around here. Where you from?
Holy crap, don't say that. I love Space Ghost. I'll always remember that episode when he had Beck on... and towards the end he offered SG a taco that had been sitting on his dashboard. A not-so-subtle homage to that lo-fi classic, "Satan Gave Me a Taco". ^_^
I could appreciate the animators just having a good time. And the unsuspecting guests putting up with it.
...was a cross between Unicorn and Unix's cron.
I had a plan for about a week to make a cron/at replacement and call it "UniCRON" in your honor. I swear I'm totally friggin' serious.
You're on my friends list too...
You can probably tell I wasn't really into transformers.
Remove the "PR_5BBD3A" bit from the URL you provided, and surprise surprise, where do you think Reuters picked up that press release...
Don't mod this up, I've metioned it like 3 times now because I want to clarify that Intentia's webmaster is the BIGGEST FINGER POINTING IDIOT EVER.
It depends on how hard you try to prevent the accidental access of the information. If you have been clearly trying hard to prevent the access, then you may have a case (legal recourse). However, I submit you this:
http://www.intentia.com/w2000.nsf/pages/
which is a link to all of the press releases, etc. Why this is publically accessable, I don't know. I just took the last part of a link on the frontpage off. I could do THAT just by mistyping. (It appears to be down now... the whole website maybe... oh well, slashdot strikes again).
So who's trying to fool who here...
See my previous post
If you visit http://www.intentia.com/w2000.nsf/pages/ you will see a list of all available documents that can go in the "frame", including press releases.
It took me 2 minutes to stumble on that, and Reuters probably did the same. How was Reuters to know what Intentia's "schedule" for releasing that document was? They probably bookmarked that index of PRs for quick reference some time ago, at recently saw something new, and publicized it.
How that constitutes "hacking" I do not understand. I put full blame on the webmaster.
Let him know what you think!
webmaster@intentia.com
I'm going to hunt you down...
::glowers::
Posting AC cannot save you.