|
What you want to happen is generally not what ends up happening.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
The first victim after making contact with the enemy always is the plan.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I look upon this as job security and possibly a part time job to fund my retirement.
To err is human to really mess up you need a computer
|
|
|
|
|
Is a serial killer better or worse than a parallel killer?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Well he finishes one job, before starting another...
|
|
|
|
|
Most killers probably don't have a standard constructor and therefore are not serializable.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Oh that was a baud one!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
I enjoy your byting wit!
/ravi
|
|
|
|
|
Stopbit Ravi you're making me blush.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Uh oh - are you seeing RAID?
/ravi
|
|
|
|
|
but still much be careful choosing victims in case causes a dead Lach.
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
All I know is that I would rather be a cereal killer then a surreal killer.
... such stuff as dreams are made on
|
|
|
|
|
Quote: cereal killer Yeah! Stomp on those cornflakes!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
The parallel killer gets less resistance...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Daniel Pfeffer wrote: he parallel killer gets less resistance... RESISTANCE IS FUTILE
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
I'm SATA undecided on this one. Perhaps it port-ends some future event, although that's a bit of a stretch.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Parallel killer can have support many contracts so more money if the killer is a contract assassin Parallel killer than a serial.
|
|
|
|
|
Out of curiosity, do any of you (in a professional capacity, as in, the company you work for) have various automated jobs that run at night the still execute batch files? And said jobs are put into a workflow with predecessor / successor dependencies, such that if one of the .bat processes (which can be, say, an EXE or a SQL SP call) fails, the whole dependency chain fails?
Or does your company use a more sophisticated way of dealing with automating workflows and dependencies?
|
|
|
|
|
At my previous job we were using BMC Control-M[^] and I found it a nice tool when in the right hands. We had lots of independent and interdependent pipelines and while I preferred a code-oriented approach, our sysadmins liked it a lot, especially for processes that spanned different architectures (file exchanges-.net code-remote queues-mainframe jobs-etc).
Of course, sysadmins had no clue of what to do when processing jobs failed - except sending an automated warning email or restarting them to retry, but that was not really their fault...
Luca
The Price of Freedom is Eternal Vigilance. -- Wing Commander IV
En Það Besta Sem Guð Hefur Skapað, Er Nýr Dagur.
(But the best thing God has created, is a New Day.)
-- Sigur Ròs - Viðrar vel til loftárása
|
|
|
|
|
No - I use scheduled tasks to run apps, which I write for specific tasks if it's not just command line switches on an existing app.
Mostly because I've had too many .BAT files that "just failed" and you can't get much of a clue as to why or even how far it got ... at least with an app you can add progress logging and fault information.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
you can still redirect the output of bat files from scheduled tasks, the old
cmd.exe /c start xxx >>log.txt 2>&1 but I agree, properly handling what happens next gets real messy real fast ... way verbose, harder to understand such scripts and no easy way to run in any sort of testing / simulation or debugging mode.
(Dare I mention spaghetti code, GOTO included, pretty much becomes SOP to achieve meaningful results.)
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
Marc Clifton wrote: And said jobs are put into a workflow with predecessor / successor dependencies, such that if one of the .bat processes (which can be, say, an EXE or a SQL SP call) fails, the whole dependency chain fails? Automated a build at a previous company, but that excludes the whole chain-fail thingy; you simply check the errorlevel-variable.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
We have enough Control-M batch jobs that we have a small team supporting them.
|
|
|
|
|
We have various 'scheduled tasks' that process customer uploaded files or perform sql backups/ftp functions. All of them use custom exes that I wrote. In the case of sql backups, the exe gets started with a job number that links to a text file with configuration info.
Why custom executables?
0: the tasks are much too complicated to handle with a batch file
1: security...if I'm decrypting/encrypting/password protecting stuff, I'd hate to have my sensitive info stored in a text file.
2: exes are what I know/deal with every day
3: easy to debug
"Go forth into the source" - Neal Morse
|
|
|
|
|
The key phrase for me is "at night". I have nightly batch files on each of our department servers that handle backups and other routine stuff. For me, this is an application of KISS.
Our automated build process OTOH is a Windows service written in C#. A base class executes all the steps required for the build, from retrieving source code from source control to archiving the build folder at the end in an .ISO file. Product-specific classes derived from the base class handle situations unique to each product. The process itself is fairly granular, and can be paused and resumed or canceled easily. If the service is running on one of our build servers it performs a production build. If it's running on a developer's machine, certain steps are omitted to reduce the build time.
Software Zen: delete this;
|
|
|
|