Kevin Bach
New Member
I have managed servers for years, automatically starting BASH scripts and Perl scripts to rectify certain situations. Lately, I have had a rash of these not starting at all. My first idea was the thought that everything inside these scripts needed an absolute path, as something had changed in the evolution of Linux (Fedora, my fav distro), provoking the need for a lot more absolute paths. It seemed to help with some, but apart from picking through every single line of a few hundred scripts I have written over the years (a few hundred others that were retired but saved for reference), I just don't know where to start to diagnose this problem. Many of the problems started with rc.local lines being executed, but I have forked dozens of tiny baby BASH scripts, some are service monitoring (watchdogs of daemons).
(By the way, I hate the way the Linux OS has attempted to sabotage the rc.local concept in recent years.)
Any thoughts, musings, critiques, criticisms, comments, questions, concerns, would be received with an open mind.
Kevin
(By the way, I hate the way the Linux OS has attempted to sabotage the rc.local concept in recent years.)
Any thoughts, musings, critiques, criticisms, comments, questions, concerns, would be received with an open mind.
Kevin