You can subscribe to this list here.
2004 |
Jan
(32) |
Feb
(18) |
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
(8) |
Sep
(8) |
Oct
(6) |
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(1) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2006 |
Jan
|
Feb
(3) |
Mar
(10) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(2) |
Dec
(2) |
2007 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
2008 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(14) |
Aug
(6) |
Sep
(7) |
Oct
(4) |
Nov
(20) |
Dec
(1) |
2009 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Mark W. <mw...@iz...> - 2005-05-06 12:38:14
|
Hello everyone, I'd like to not have to install perl on my target cronw machines. I've compiled cronservice.pl into cron.exe and installed it as a service with tools from aintx. But alas, I only get an error when I try to start the service. Perhaps I'm missing something simple. Any ideas regarding what I'm possibly missing? Are there other dependencies that I'm not considering? Thanks Mark |
From: Robert K. <mai...@ro...> - 2005-04-03 12:01:46
|
Hi all! I started work on the Installer for CRONw this weekend. The chosen installer is InnoSetup, available from <http://www.jrsoftware.org/isinfo.php>. I decided against NSIS because InnoSetup is much more easy while providing the same (or even more) functionality as/than NSIS. I incorporated a new module in CVS called "Installer", whose main (and atm only) script file is CRONw.iss. The script, when compiled, packs together CRONw's files and forms an executable from it. After installing the files on the system it tries to install the needed Perl modules, register and start the service. Atm, this goes wrong, so the installer is not complete by now. In the module "Installer" you'll find a INSTALL.txt describing briefly how to build the .exe by yourself. Feel free to test the script that builds the installer and report your experiences. Work will go on, I expect to have the installer in a stable and working state the end of April. The things to do include these points: * make installation of the Perl modules work * make installing and starting the service work * provide an update mechanism * better error checking There's probaby more to do. With kind regards, Robert Kehl |
From: Felix S. <fe...@sc...> - 2005-03-01 20:13:30
|
Hi all! Finally I just released CRONw 2.0. Basically it's just a rename of RC1 so no need to upgrade if you are using RC1 already. new features of CRONw 2.0 * complete rewrite of cronw which includes better source file naming and provides a solid basis for future extensions * greatly improved logging - increase logging output without the need to restart the service * use mnemonics inside crontab.txt (e.g. say "Mon-Fri" instead of "0-5") * cron dir support: If you want to execute a job one time a day just put it into the dir cron.daily (same goes for cron.weekly and cron.monthly) * syntax checking for crontab.txt * lower system payload - crontab is only parsed if it has changed * scripting features supported by CMD.exe - write "echo "Hello World" > C:\testfile.log" in the crontab Hopefully no old features got lost such as: * 1,15 in the day field means execution on the 1st and 15th of every month * 1-10 is equivalent to 1,2,3,...,10 * */5 in the minutes fields means that the command should be executed every five minutes. * the ability to combine all the above features. Please note that version 2.0 is to be taken as incompatible with an existing installation of CRONw 1.x (allthough the crontab format hasn't changed). Please read the INSTALL.txt file _before_ installing. Unfortunately the graphical installer for CRONw (NSIS based) doesn't made it for this release, maybe we can get it ready for 2.1. Help wanted! Release planning for 2.1 main items (2.1 won't be published before they are finished): * some internal refactorings to keep the code clean * run perl files directly - write C:\test.pl instead of C:\perl\bin\perl.exe C:\test.pl * run jobs only once (at start of the service) features that *may* be included: * support for the w2k runas command * mail output of jobs to a specified address * NSIS based installer * separate the NT/2k/XP specific parts so that it is possible to run CRONw on Windows 95,98 and ME. This will help for debugging, too. wishlist features (probably not in the next release) * Logging to eventlog[1] [1] Generally speaking this is already possible but for real support we have to register a dll so that there is no standard windows warning in the eventlog. Someone who wants to fight with the Microsoft message compiler wanted! estimated release date: ??? After all main items are completed. I want to shorten the time between two releases but I can't promise anything. If you have some cool ideas or want to help: Now is the time to do it! We really appreciate code reviews and comments how to improve the code! Hope you have fun with CRONw 2.0! :-) -- Felix |
From: Felix S. <fe...@sc...> - 2005-02-16 12:35:44
|
Hi all, After fixing some bugs related to module installation and the exit code 1 problem we decided to release a release candidate to ensure getting a high quality 2.0 release. If no further problems are found we will release 2.0 in 1-2 weeks. Please test this release, especially comments on Windows XP SP2 are welcome! Changes + create dirs cron.daily, cron.weekly, cron.monthly if they don't exist + small fixes + if no crontab.txt is found by cronHelper.pl when installing the CRONw service it checks for 'crontab' existance + fixed several modules that didn't installed correctly + execution of command through CMD.exe works now much better -- Felix |
From: Felix S. <fe...@sc...> - 2005-02-13 22:15:42
|
Hi, just a short update of the release status: - module installation fixed - use crontab if crontab.txt doesn't exist Currently I'm tackling the "exit code 1" problem and have some working code (although I don't know _why_ it fixes the problem) but hesitating to commit as I refactored some code in the process so maybe a new beta is needed to ensure that we get a high quality 2.0 release. bye (have to learn for my exams) -- Felix |
From: Robert K. <mai...@ro...> - 2004-11-15 20:58:18
|
Felix Schwarz schrieb: > how to proceed for RC1? I'm seeing four bugs (the wxp guy in the bug > tracker, three cronService.pl warnings and the exit code 2 in the > forum). After that I think we can release RC1. I did test CRONw on XP, and cannot reproduce any of the errors in the bugs. Nonetheless we should solve them, if they are solvable. > IIRC you wanted to add an easy to use installer. Do you think you can > finish that in the next 1-2 weeks? Otherwise I think we should release > 2.0 (that means: get some release candidates out) and include it in > 2.1. I'm at it, but work is going slowly, as I have to work on another project which pays me, so be patient. I hope to get something going towards the end of the week. > My current 2.1 plans: > - Squash all bugs! > - Improve the documentation if needed > - 103578 start jobs at service start > - 103293 Log4Perl and external logger configuration > - 107757 Execute perl files directly > - 91885 cron.d Directory parsing > - squash even more bugs! Good plans. Do we have a task for implementing a component to perform actions on the output of the scripts? Say, mail it, in the first place? Regardds, Robert Kehl |
From: Felix S. <fe...@sc...> - 2004-11-15 17:18:01
|
Hello Robert, how to proceed for RC1? I'm seeing four bugs (the wxp guy in the bug tracker, three cronService.pl warnings and the exit code 2 in the forum). After that I think we can release RC1. IIRC you wanted to add an easy to use installer. Do you think you can finish that in the next 1-2 weeks? Otherwise I think we should release 2.0 (that means: get some release candidates out) and include it in 2.1. My current 2.1 plans: - Squash all bugs! - Improve the documentation if needed - 103578 start jobs at service start - 103293 Log4Perl and external logger configuration - 107757 Execute perl files directly - 91885 cron.d Directory parsing - squash even more bugs! -- Felix |
From: Felix S. <fe...@sc...> - 2004-11-06 16:51:32
|
Hi all, We noticed some little bugs in the beta release therefor I decided to release a beta2 version before the release candidates. Fixes: + CRONw doesn't fail to start if it is installed into a path which contains spaces. + source files using windows line breaks. Thanks to all testers. We'll appreciate all installation reports. Please test the new release: http://prdownloads.sourceforge.net/cronw/CRONw_2.0_beta2.zip?download -- Felix |
From: Felix S. <fe...@sc...> - 2004-10-31 20:38:19
|
Hallo Robert, Robert schrieb: > Felix Schwarz schrieb: >> I tried to update the website with CVS using cvs checkout but that >> failed (connection timed out). I can ping cvs.sf.net but it seems that >> the cvs port is unreachable. >> >> Robert, do you know how to circumvent these limitation? > I'm seeing updates on the cvs-log ML - which files didn't succeed? [scfe@sc8-pr-shell1 test]$ cvs -d:pserver:ano...@cv...:/cvsroot/cronw login Logging in to :pserver:ano...@cv...:2401/cvsroot/cronw CVS password: <time out> [scfe@sc8-pr-shell1 test]$ telnet cvs.sourceforge.net 2401 Trying 66.35.250.207... <timeout again> Seems as they installed a packet filter... -- Felix |
From: Robert K. <mai...@ro...> - 2004-10-31 20:19:39
|
Felix Schwarz schrieb: > I tried to update the website with CVS using cvs checkout but that > failed (connection timed out). I can ping cvs.sf.net but it seems that > the cvs port is unreachable. > > Robert, do you know how to circumvent these limitation? I'm seeing updates on the cvs-log ML - which files didn't succeed? Did you check sf.net's Site Status? See: http://sourceforge.net/docs/A04/ Did take into regard sf.net's maintenance schemes? Does it work again? hth, Robert Kehl |
From: Felix S. <fe...@sc...> - 2004-10-31 15:40:10
|
Hi all, I tried to update the website with CVS using cvs checkout but that failed (connection timed out). I can ping cvs.sf.net but it seems that the cvs port is unreachable. Robert, do you know how to circumvent these limitation? -- Felix |
From: Felix S. <fe...@sc...> - 2004-10-26 17:42:13
|
Hi all, I released a beta version of CRONw 2.0 some minutes ago. As soon as I get access to the website I'll update these sites, too. Please test the new release: http://sourceforge.net/project/showfiles.php?group_id=87160&package_id=106736&release_id=278045 -- Felix |
From: Felix S. <fe...@sc...> - 2004-10-26 16:41:35
|
Hallo Robert, Robert schrieb: > Ja, stimmt ja - wofür gibt's denn die Betas? Hau's raus! Eine Sache noch: Damit ich die Webseite aktualisieren kann, wäre es nett, wenn du der Gruppe cronw auch Schreibrechte auf die Dateien in htdocs geben würdest. -- Felix |
From: Felix S. <fe...@sc...> - 2004-10-03 09:47:15
|
Hallo Robert, okay finally I put some last fixes together. The new website is in CVS - currently only the main site, I'll do INSTALL and UPDATE later if everybody is satisfied with the contents of INSTALL.txt and UPDATE.txt. I changed the suffix from php to html as I didn't see any use of php so switching to html saves resources on the sf site. Please review my changes. After your okay I'll publish the new website and put a beta release together. -- Felix |
From: Robert K. <mai...@ro...> - 2004-09-17 19:19:03
|
On Friday, September 17, 2004 11:06 AM Felix Schwarz <fe...@sc...> wrote: > Can we check out the website manually? Yes, we can. > If so wouldn't it be easier to set up a cron job that logs in > automatically on the sourceforge servers and check the website out? Yes, we'd have to incorporate a cron server to do so. I will. Es grüßt fröhlich Robert Kehl -- Wenn ich den Martin Schneider weiter aufstelle, glauben die Leute am Ende wirklich noch, ich sei schwul... Friedel Rausch |
From: Felix S. <fe...@sc...> - 2004-09-17 09:06:36
|
Hallo Robert, Robert schrieb: > So, because of cron not running, we cannot synch CRONw's website > automagically. What a joke, but never mind. We have to update the > website manually then. Can we check out the website manually? If so wouldn't it be easier to set up a cron job that logs in automatically on the sourceforge servers and check the website out? That would automatize the whole process. -- Felix |
From: Robert K. <mai...@ro...> - 2004-09-17 07:17:17
|
On Wednesday, September 15, 2004 9:22 PM Robert Kehl <mai...@ro...> wrote: > The module isn't (yet) automagically synched to the webspace, because In fact, it wouldn't work at all, because sf.net disabled the cron service on the shell servers, see the News update of 2004-07-29 05:23:35 - Project Shell Service: "As of 2004-07-22, cron has been taken offline on the project shell servers. We are currently pursuing a resolution to a significant performance problem on the shell servers related to cron jobs. At this time, the project shell server is typically handling more than 1000 crontabs, many with poorly-scheduled cronjobs; we are working to determine a way to reduce system performance impact of these cronjobs (through better management) as to make this particular service offering (cron service) continue to be viable." http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1 So, because of cron not running, we cannot synch CRONw's website automagically. What a joke, but never mind. We have to update the website manually then. This is how I do it: I'm building the website on my Windows PC, storing it on a Samba share on an inhouse linux server, from which I check in the changes to cvs.sf.net and in the following connect to sf.net's shell servers to copy the content via scp. To faciliate things, I created an alias 'htcronw' in my $HOME on the shell servers pointing to /home/groups/c/cr/cronw/htdocs/, the actual webspace. So the copy command looks like this: # scp -r /path/to/sf-website/* use...@sh...:~/htcronw/ Just try it out, it's kinda easy. Tell me if I should update the site otherwise, no problem. Best wishes, Robert Kehl -- In erster Linie stehe ich voll hinter dem Trainer, in zweiter Linie hat er recht. Olaf Thon |
From: Robert K. <mai...@ro...> - 2004-09-16 19:15:01
|
On Thursday, September 16, 2004 4:53 PM Felix Schwarz <fe...@sc...> wrote: > There is only one error I can't fix: Log-Dispatch.tar.gz seems to be > corrupted allthough there was no error message during the > installation. Nevertheless there are no Log::Dispatch files on my > harddisk and I can't open the tar.gz with my archive programs. > @Robert: Can you fix it? Done. Es grüßt fröhlich Robert Kehl -- Wir wissen alle, dass Mario nicht gesagt hat, was er gesagt haben soll, dass er es gesagt hat. Berti Vogts |
From: Robert K. <mai...@ro...> - 2004-09-16 17:55:23
|
On Thursday, September 16, 2004 4:53 PM Felix Schwarz <fe...@sc...> wrote: > Hi all, btw: is there anyone besides us two? ;-) Never mind... > as I wrote yesterday I installed cronw on a fresh system. The > installer.pl worked but I noticed some small errors which I fixed > today. I hope I manage to work it out on my box tomorrow. > There is only one error I can't fix: Log-Dispatch.tar.gz seems to be > corrupted allthough there was no error message during the > installation. Nevertheless there are no Log::Dispatch files on my > harddisk and I can't open the tar.gz with my archive programs. > @Robert: Can you fix it? I noticed this right now. I will, prio A. > I also tried to improve the existing website (not in CVS yet). I tagged the current sf-website version as 'CRONw-1_4_0_beta' now, so feel free to spoil ;) Besides: automatic synching isn't working yet, so it doesn't matter if you check in now or later. Any ideas about auto synching the module to the website? With kind regards, Robert Kehl PS: Thank you, dear Felix, for your good work now and in the past, I really appreciate it! |
From: Felix S. <fe...@sc...> - 2004-09-16 14:53:23
|
Hi all, as I wrote yesterday I installed cronw on a fresh system. The installer.pl worked but I noticed some small errors which I fixed today. There is only one error I can't fix: Log-Dispatch.tar.gz seems to be corrupted allthough there was no error message during the installation. Nevertheless there are no Log::Dispatch files on my harddisk and I can't open the tar.gz with my archive programs. @Robert: Can you fix it? I also tried to improve the existing website (not in CVS yet). -- Felix |
From: Robert K. <mai...@ro...> - 2004-09-15 19:25:26
|
On Wednesday, September 15, 2004 12:26 PM Felix Schwarz <fe...@sc...> wrote: > I wrote a small installer.pl which I'll want to test today on a clean > system. If the preliminary installer works I think we should get 2.0 > Beta out ASAP. You're so impatient ;) > Robert: Do you have the time to release a beta this week? May I > release a beta myself? (before that I'll send a mail to get you ok of > course) Unfortunately, my time scheme is as narrow as never this month, but... you already own the status of a release technician, meaning you can release packages yourself. Best is to tell me beforehand, as you promise. Btw, name the next release 'Sapphire Gloss', if nothing stands against it. :) > Website: > I think we can create a new module in CVS for that. No big, fancy > stuff. Editing the website means editing the files in CVS and putting > it on the server. Maybe we can create an automatic checkout later. For > the next things just let us use low tech. Check out the new module 'sf-website', it is low-tech. *ggg* The module isn't (yet) automagically synched to the webspace, because I didn't manage to checkout the module from within my sf.net shell account (every developer owns one, check it out, - it's cool!). It seems as if the shell server cannot connect to the cvs server, the connection timed out. They were made as anonymous, as I don't want to upload my private key to shell.sf.net. But, as a developer, who you are, you can access the website space from within your shell account. See: ls -l /home/groups/c/cr/cronw/htdocs/ Es grüßt fröhlich Robert Kehl -- Telefonieren Sie mit uns oder rufen Sie uns an! Jörg Wontorra |
From: Felix S. <fe...@sc...> - 2004-09-15 10:27:03
|
Hi Robert, I wrote a small installer.pl which I'll want to test today on a clean system. If the preliminary installer works I think we should get 2.0 Beta out ASAP. Robert: Do you have the time to release a beta this week? May I release a beta myself? (before that I'll send a mail to get you ok of course) Website: I think we can create a new module in CVS for that. No big, fancy stuff. Editing the website means editing the files in CVS and putting it on the server. Maybe we can create an automatic checkout later. For the next things just let us use low tech. your comments? -- Felix |
From: Robert K. <mai...@ro...> - 2004-08-31 07:18:44
|
On Saturday, August 28, 2004 5:38 PM Felix Schwarz <fe...@sc...> wrote: > who will update the cronw website appropriately in order to reflect > our new plans? Can every cronw developer edit the website? Do we have > a version control for it? Not at current. What I can do towards the end of the week is: Create a new module 'web', check-in the current source code and implement some kind of automatic update mechanism. Es grüßt fröhlich Robert Kehl -- Die Schweden sind keine Holländer - das hat man ganz genau gesehen. Franz Beckenbauer |
From: Robert K. <mai...@ro...> - 2004-08-31 07:14:19
|
On Saturday, August 28, 2004 5:23 PM Felix Schwarz <fe...@sc...> wrote: > I propose to use a .txt suffix for all documentation files so it will > be easier for windows users to open them. Any contrary opinions? Good idea. Robert Kehl |
From: Robert K. <mai...@ro...> - 2004-08-31 07:14:16
|
On Saturday, August 28, 2004 5:36 PM Felix Schwarz <fe...@sc...> wrote: > I updated some documentation today. I consider cronw (CVS head) as > ready for beta release as my plate is clean. > >> I'm with you, go ahead. I'll be going to build >> a) a .bat that installs needed modules in the current Perl >> environment, and >> b) an installer to do the same. > > @Robert: What is your status? > Maybe we can create a very simple .bat (only setting ppm) and release > an beta? I think we can add an installer later. That's true. Atm, I'm a bit stuffed with (paid) work. I hope to find the time towards the end of the week. Es grüßt fröhlich Robert Kehl -- 2+2=5 |