Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  System / Utilities  |  Other System / Utilities  |  CronniX  |  Too ban I can't download

CronniX

CronniX

allows scheduled execution of Apple- & shell scripts

Version:  3.0.2

   [ Views: 882 ]

Too ban I can't download

Feedback Type:  Commentary

Contributed by: tombovo Thursday, June 22 2006 @ 06:42 AM PDT

Product Platform: MacOSX

Used Product For: Over One Year

Recommend Product: YES

I'm having no luck either downloading from the VersionTracker link, or even getting to the developer's web page. The web site seems unresponsive, which is a shame as I have used CronniX for quite some time and have found it to be useful.   

0 of 2 users found this helpful.

Rate this Commentary

Was this Commentary helpful? Yes | No

Comments

5 comments |

Just TRY AGAIN... - Andreas..

...because not the slightest problem here with either the d/load or the site.

Reply to This

Thursday, June 22 2006 @ 07:31 AM PDT


Re: Just TRY AGAIN... - it isn't that simple - tombovo

I've tried at various times, from various machines (at home and at work), and still having no success--attempting to reach the web site times out. It may me a firewall issue (the developers new site uses port 9080, which isn't a standard). This means I have to open up that port on my firewall at home, but I will have no way of doing that at work.

Reply to This

Thursday, June 22 2006 @ 12:25 PM PDT


Re: Just TRY AGAIN... - it isn't that simple - tombovo

I've tried at various times, from various machines (at home and at work), and still having no success--attempting to reach the web site times out. It may me a firewall issue (the developers new site uses port 9080, which isn't a standard). This means I have to open up that port on my firewall at home, but I will have no way of doing that at work.

Reply to This

Thursday, June 22 2006 @ 12:26 PM PDT


Re: non-standard web port - tombovo

The developer for this is using port 9080 for his web site, and that was what was failing. At work, I couldn't open the port in the firewall and therefore couldn't reach the site. At home, I never thought to open port 9080 in my firewall. What I actually did at work--and just completed--was to ssh into a third party machine I can access that is less restricted, curl the file (using the link that appears in versiontracker.com) to that machine, and then scp the file to my work machine.

Reply to This

Thursday, June 22 2006 @ 12:43 PM PDT


Thanks 4 explaining - Andreas..

...and well done. Pleased you found a 'route'.

Reply to This

Thursday, June 22 2006 @ 02:08 PM PDT