On 10/29/2014 09:06 PM, Angelo Moreschini issued this missive: > Hi Ed, > > I also thought that I setting controls the command in a different way > could be the solution. > But it did not was so. > The question is now, however, morelimited: it is about understanding why > a script that can be run from the command line, does not run inside the > file /etc/rc.d/rc.local Because the /etc/rc.d/rc.local script does not have your login environment. The odds are that the path to one or more of your commands is missing. If you want to prove this, modify your script to do something like echo $PATH >/tmp/path.txt and reboot. Compare the contents of /tmp/path.txt and "echo $PATH" at the command line and I'll bet the paths are different. This is incredibly common for startup scripts and crontab entries. If you wish to avoid them, ensure you have a "PATH=" command in the top of your script or specify the full path to each command inside the script: /usr/bin/rsync........ NOT rsync..... because "/usr/bin" may NOT be in the crontab or initscript's PATH. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - After a shooting spree, they always want to take the guns away - - from the people who didn't do it. - - -- William S.Burroughs - ---------------------------------------------------------------------- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
