Posted: Wed 24 Oct 2007, 17:12 Post_subject:
Struggling to control access to a server using cron[SOLVED]
I have the abyss webserver (very neat -- can someone update the .pet to the latest version pls?) running on puppy 3.0.
The idea is to make some large photo albums available to friends.
My ISP provides lots of bandwidth between 00:00 and 16:00 and little between 16:00 and 00:00.
I want to exclude access between the latter times for obvious reasons.
Ideally I'd have the port on which abyss is running closed during that time but my router is not sophisticated enough to do that.
I have iptables set up (via wizard -- i'm not clever enough to understand how to manually craft it) with all ports except that one closed.
So I think that the only way I am going to be able to do this is to start abyssws on boot then run a cron job to kill it at 16:00 every day.
Or is there way to have a script that will reconfigure iptables "on the fly" and use cron to control that?
Or is there a "better" solution that someone knows of?
Pschedule is a frontend to cron that is easier to use than gcrontab...here is the link maybe it will help you get started.. http://www.murga-linux.com/puppy/viewtopic.php?t=22166&search_id=1530290542
zigbert is pretty open to sugestions if you can think of ideas how to make his programs better _________________ Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
BeOS Max-Vectorgamma: Tyan thund 2 512 ram 2x PII 300
Vectorsigma (laptop): Gentoo Athlon II X2 2Ghz 4Gb ram radeon 4200 mesa-git
i finally got cron working satisfactorily; i opened /var/spool/cron/crontabs/root with e3vi and found what appeared to be an "extra" character at the end of the file; removing this and saving the file seemed to cause cron to spring into life.