Re: rc.local not start at the boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I made now another try ...
I modified the file /etc/rc.d rc.local in this way :
- - - - - - - - - - - -
#! / bin / bash
# This the the file /ctc/rc./rc.local

/usr/bin/sol

- - - - - - - - - - - -

the file “sol”: (-rwxr-xr-x. 1 root root 62480 Mar 5 2014 /usr/bin/touch)


is an executable (a card game that can run seamlessly from the command line). 


At the boot, the program “sol” has not been launched yet.

I am a beginner with Linux, so my question perhaps is silly, but it seems logical to ask :
because instead /usr/bin/touch was run ?


On Wed, Oct 29, 2014 at 3:07 AM, Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
On 10/29/14 08:36, Joe Zeff wrote:
> On 10/28/2014 04:18 PM, Ed Greshko wrote:
>> Since /tmp/rc.local.log exists and contains
>>
>> + /home/angelo_dev/bin/syncronize-java_srcs.sh
>>
>> it is obvious that rc.local is being executed.
>>
>> If I were going to assume something I would assume the systemctl failure is related to the failure in the syncronize-java_srcs.sh script.
>
> My guess is that one of the scripts being called failed, causing rc.local to abort.  Maybe it would help to put a line like this just at the end of each script called:

Let me say this again....  rc.local *did not* abort.  It exited and the last exit code was that returned by syncronize-java_srcs.sh

>
> echo "$FOO.sh completed" >> /temp/rc.local.log
>
> If something in the script fails, the script doesn't complete and the line isn't written in the log.  Adding print statements to help debugging is a very old technique, but it's helped me find out just where things went wrong many times over the decades.

What I've asked for from the OP will help *me* to determine what is failing when "rsync" is being called.

If you want him to do something else....talk to him.

--
If you can't laugh at yourself, others will gladly oblige.
--
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

-- 
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
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux