* C. Bensend <[EMAIL PROTECTED]> [2004-10-15 08:14:51 -0500]:
> Concurrency shouldn't be an issue - this is a perl script running
> from cron. The only concurrency that will ever happen is if I'm a
> bonehead and I run the script manually right as cron kicks off
> another copy.
Even cron'd script
> Even cron'd scripts can run amok. Lock files are great as a CYA
> measure even if you're relatively certain there will be no opportunity
> for one copy to step on the next.
Yes, you are absolutely correct, of course. :)
I should be more specific - I'm working on a personal project, and I'm
no
Hai,
How to take Database backup from an application developed in Visual
Basic thats running at Windows Client and Database resting at Linux
Server. THanx
Sreejith
---(end of broadcast)---
TIP 6: Have you searched our list archives?
* sreejith s <[EMAIL PROTECTED]> [2004-10-17 08:49:44 +0530]:
> How to take Database backup from an application developed in Visual
> Basic thats running at Windows Client and Database resting at Linux
> Server. THanx
pg_dump -U your_username your_database > your_database.sql
--
Steven Klassen
"C. Bensend" <[EMAIL PROTECTED]> writes:
> The risk of a cron gone wild is acceptable to me at this moment.
Gee, now I have images of late-night advertisements for bofh-porn video tapes
of Cron Jobs Gone Wild(tm) dancing through my head... thanks.
--
greg
---(end of b
> Gee, now I have images of late-night advertisements for bofh-porn video
> tapes
> of Cron Jobs Gone Wild(tm) dancing through my head... thanks.
Wow. THERE'S something I didn't need before hitting the sack. ;)
Benny
--
"Even if a man chops off your hand with a sword, you still have two nic
