Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • Replies 8 replies
  • Subscribers 666 subscribers
  • Views 1840 views
  • Users 0 members are here
Related

raspberry pi sakis3g software script for automatic startup

Former Member

guys, I wanted to run sakis 3g automatically on startup. I have already written the code for configuration using sudo nano /etc/sakis3g.conf.

 

 

Whenever I type sudo ./sakis3g connect, the usb modem gets connected within a minute.

Now, I want this command to be executed on the boot up of the raspberry pi.

 

 

So, I tried adding this command " sudo ./sakis3g connect " to rc.local, it did not work.

 

 

So , I wrote this script below which also did not work .

 

 

1st, I executed sudo nano /etc/init.d/sakis3g

 

 

[code]

#! /bin/sh

# /etc/init.d/foobar

 

 

# The following part always gets executed.

echo "This part always gets executed"

 

 

# The following part carries out specific functions depending on arguments.

case "$1" in

  start)

    sudo ./sakis3g connect

    motion

    ;;

  stop)

    sudo ./sakis3g disconnect

    echo "camera is dead"

    ;;

  *)

    echo "Usage: /etc/init.d/sakis3g {start|stop}"

    exit 1

    ;;

esac

 

 

exit 0

 

 

[/code]

 

 

I have also included motion command above in order for the motion software to start on bootup.

 

 

After this I executed these two commands .

 

 

sudo chmod 755 /etc/init.d/sakis3g

sudo chown root:root /etc/init.d/sakis3g

 

 

The internet is not getting connected.

I have to do it manually by typing  sudo ./sakis3g connect for it to connect.

Please help with this script.

  • Not that I've done this, but generally you should put the entire path to the file in your script, i.e. not ./sakis.. but instead something like /usr/local/bin/sakis.. (or wherever it is located).

    Also, you may not need the 'sudo' in your script. Finally, it's worth checking to see if the /<path>/sakis3g (whatever that is) is a script too, or an executable. If it is a script, check that too, to ensure it's not relying on environment variables that may not exist at startup.

  • in reply to shabaz

    Sir, sakis3g is an executable file. Thats why I tried putting the sudo command in the script. When I enter the command sudo ./sakis3g manually, it gets connected. So , in order for it run automatically I wrote it in the script.

     

    Sir, what changes should I do now in the script ???

     

    Could please specify?

  • in reply to Former Member

    The dot signifies current folder. Executables don't sit in /etc/xx so having a dot in the script is not a good idea - how will the script know which folder you mean?

    Tha's why you need to put the entire path as described earlier.

  • in reply to shabaz

    Sir, I am a newbie! Dont have much knowledge abt scripts.

     

    I included the command "sudo ./sakis3g connect" in the script , and not the location of the folder that sakis is in.

     

    I wanted this command to be executed on boot up, and so I included this in a script.  (this command worked well when I typed it in manually in the command window)

     

    I hope you got my point and idea.

  • in reply to Former Member

    I do get your point. But, as mentioned, just because it works on the command line with a dot doesn't mean that's the case from a script. You need to locate where the software is installed (e.g. /usr/local/bin) and put the entire path in your script.

  • in reply to shabaz

    I think what you're looking for is:

    1) move your sakis3g script to somewhere publicly accessible (/usr/local/bin would be the traditional location).  It's a good idea to set the owner to root and the permissions to read-only for everyone else (ie, chmod 755 /usr/local/bin/sakis3g).

    2) add a line such as "/usr/loca/bin/sakis3g" to your /etc/rc.local

     

    That should cause your script to be executed on each reboot.

  • in reply to bprewit

    I think you want to add the /usr/local/bin/sakis3g line to:

     

    /etc/init.d/rc.local

     

    instead of:

     

    /etc/rc.local

     

    /etc/init.d/rc.local is one of the last start up scripts run by init from the run level directories (/etc/rc2.d, /etc/rc3.d, etc).

     

    I' not sure if or when /etc/rc.local is run (user login ?).

     

    Edited to add:

     

    I just did some checking and /etc/rc.local is run at system initialization (by /etc/init.d/rc.local) so the original instructions

    should work. I know I tried using /etc/rc.local before to create the link /dev/ttyS0 for the Raspberry Pi serial device /dev/ttyAMA0

    and it didn't work until I moved it to /etc/init.d/rc.local. At the time I had no idea why it didn't work, and I still don't. Permissions ?

  • in reply to bprewit

    Thanks a lot sir!

     

    It works perfectly now!

     

    You rock!!