Joe,

 

I have a question, I have the app called Jungle Disk being installed on reboot by running the following command from the go file "installpkg /boot/packages/backup.tgz which is working fine.

 

Then I have a line to start Jungle Disk "/boot/packages/mysecurebackupserver"

 

I have set permissions on the file by running chmod -x "mysecurebackupserver"

 

If I log in to the console and type "/boot/packages/mysecurebackupserver" it starts fine

 

So why does this line not work in the GO FILE??

 

 

Joe,

 

I have a question, I have the app called Jungle Disk being installed on reboot by running the following command from the go file "installpkg /boot/packages/backup.tgz which is working fine.

 

Then I have a line to start Jungle Disk "/boot/packages/mysecurebackupserver"

 

I have set permissions on the file by running chmod -x "mysecurebackupserver"

 

If I log in to the console and type "/boot/packages/mysecurebackupserver" it starts fine

 

So why does this line not work in the GO FILE??

It probably does not have the same $PATH

 

Or, you did not put a trailing newline on the command.

 

If you like, zip up your "go"' file and attach it.  Perhaps a prior command is not finishing so it never gets to "mysecurebackupserver"

 

Joe L.

Here is my go file

go.zip

Here is my go file

Is unmenu starting itself when you reboot?  (it would assure you the script is getting past the line above it)

Joe,

 

Yes, unmenu is starting fine. I fixed the issue, I tried this yesterday and it did not work, but I guess it could have been a typo on my part yesterday. I think the problem was the install of the license file was not happening fast a enough before it would try to start Jungle Disk. I added this back in today and it is working!!!

 

echo "/boot/packages/mysecurebackupserver" | at now + 1 minute

 

Are there any to add a simple GUI to add cron jobs in the feature?

 

Thanks for you follow up...

 

SV

 

Joe,

 

Yes, unmenu is starting fine. I fixed the issue, I tried this yesterday and it did not work, but I guess it could have been a typo on my part yesterday. I think the problem was the install of the license file was not happening fast a enough before it would try to start Jungle Disk. I added this back in today and it is working!!!

 

echo "/boot/packages/mysecurebackupserver" | at now + 1 minute

 

Are there any to add a simple GUI to add cron jobs in the feature?

 

Thanks for you follow up...

 

SV

 

I've always wanted to write one.  It is a little more complicated than it looks to make it easy for beginners since cron is so flexible.

Joe,

 

I will leave that to the professionals, nominations start on the left. You get my vote….

 

I did have thought, based on the following example:

 

echo "/boot/packages/mysecurebackupserver" | at now + 1 minute

 

The process is started in approximately 1 minute so this is base on time.

 

So would this line work in the go file? and could it be looped some how?

 

Echo “cp /etc/mysecurebackupserver/*.xml /boot/packages/” | at now + 60 minute

 

Joe,

 

I will leave that to the professionals, nominations start on the left. You get my vote….

 

I did have thought, based on the following example:

 

echo "/boot/packages/mysecurebackupserver" | at now + 1 minute

 

The process is started in approximately 1 minute so this is base on time.

 

So would this line work in the go file? and could it be looped some how?

 

Echo “cp /etc/mysecurebackupserver/*.xml /boot/packages/” | at now + 60 minute

 

If you have a task that you would like performed once an hour, there is already a directory on the system for that.

 

Put any script of commands you would like in a file in this directory:

/etc/cron.hourly

then change it to be executable, and it will be run once an hour at 47 minutes past the hour.

 

So, put these two lines in your "go" script

echo "cp /etc/mysecurebackupserver/*.xml /boot/packages/" >/etc/cron.hourly/copy_xml_files

chmod +x /etc/cron.hourly/copy_xml_files

The first line will create the script.  The chmod command will mark it as executable.

 

Cron is set up to run tasks in that directory (/etc/cron.hourly) once an hour.  Any executable files found there will be invoked in turn.

 

In the same way, there are

/etc/cron.daily 

/etc/cron.weekly

/etc/cron.monthly

directories for tasks on a daily (4:40 AM), weekly (4:30 AM, first day of the week), and monthly (4:20AM first day of month)

 

Joe L.