[Ilugc] Any open source Unix shell script editor available for windows?
- From: binand@xxxxxxxxx (Binand Sethumadhavan)
- Date: Mon May 22 18:08:26 2006
On 22/05/06, Bharathi Subramanian <sbharathi@xxxxxxxxxxxxx> wrote:
On Mon, 22 May 2006, Suraj wrote:
But, why do you need unreadability of your scripts?
We came across one situation. One script is used to parse the log file
and generate reports. An enthu field guy saw the code and took a copy
and modified it.
He used the modified script to generate the reports. That was the
disaster. Bcoz he commented an important step, which is used only by
developer to some specific debugging. It took a week to find that.
So sometime it is needed and is nothing to do with secrete or hiding
of the code. :)
Whoa. Hang on...
1. Enthu guys, just because they are enthu, shouldn't be allowed on
production boxes. Access to production boxes should be carefully
controlled. You need an access control policy.
2. They certainly should not be able to edit stuff on those production
boxes. They should be editing scripts on workstations, checking their
changes into a version control system, testing their modifications on
test data and only then deploying them on production systems.
3. Debugging code, when commented out, should not cause such a major
mess. The presence or absence of debugging code should not alter the
behaviour of any program in any way.
You should not choose SHC to overcome these gaps in your internal
processes. These gaps will certainly make themselves conspicuous
another day, with probably far more disastrous consequences.
Binand
Other related posts: