Re: Blacklisted Shell Script? --- not quite SOLVED ---

Mike, and Brad, I am proceeding on the assumption that  somehow, the 
end-of-rope limit on my system for bash script size changed recently. My 
previous bash script (with comments and other crud) was 10.2KB, and a 
primitive barebones collection of essentials (lines cannibalized from 
the original) is so far 1.6KB, and it runs. I'll creep upwards from 
there, but hints on a more "scientific" method of how to determine the 
size limit would be welcomed.

What am I up to? http://web.ncf.ca/carpe.machinam/NCF/Static.html  and 
http://web.ncf.ca/carpe.machinam/NCF/sanitized-ST-585-restore.sh tell 
the story. A big concern is testing for the case where the NCF ftp 
service fails silently, and without testing for this situation 
periodically, I'll be unaware what my home IP address is.

Changes to this system? Yes, Fedora 10 is frequently pushing patches and 
fixes (including offers to head to Fedora 11), and recently I flirted 
with replacing the onboard video with a PCI Nvidia GeForce 8400GS. The 
new video card was a treat to the eyes, between frequent system lock-ups.

These lock-ups required hard-reset, and then wait for the software 
RAID-1 to repair itself. After much consternation, I am back to the 
onboard intel video.

Again, the most logical explanation I can think of for size making a 
difference, is that somewhere, there is a changed limiting number for 
script-size stored - thoughts?

Thanks;
Dave
PS SELINUX restored to "permissive" from "disabled" - _that_ takes a lot 
of time!

Mike wrote:
> On July 2, 2009, Dave wrote:
>   
>> A few days ago a bash shell script that had been working reliably for
>> months, suddenly quit working. The script has not been changed.
>>
>> I see no error messages either from cron, or from manual invocation of
>> the script. It's as if I hadn't invoked it.
>>
>> I wrote a trivial test script that works both manually, or via cron
>> (invoked via my crontab entry). But my desired script  produces nothing.
>>
>> Where do I look to see a hint? Nothing in /var/log/cron or
>> /var/log/messages suggests any problem.
>>
>> Given that a shell script will work as demonstrated by my test script
>> (both from a terminal or via cron), why did my desired script suddenly
>> quit working, silently? Has my OS blacklisted it?
>>     
>
> Maybe a recent update introduced a script with same name, or changes 
> permissions on it.  One of the securty scripts used to disable setuid 
> programs. 
>
> Does your trivial script have the same name as the blacklisted one?
> What does ` which blacklisted script `  return 
> What are the permissions on the blacklisted script   ls - l  blacklisted 
> script
>
>
>   
-- 
OCLUG general discussion list
[email protected]
http://oclug.on.ca/mailman/listinfo/oclug