You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(38) |
Jun
(3) |
Jul
(12) |
Aug
(4) |
Sep
(12) |
Oct
(15) |
Nov
(26) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(14) |
Feb
(34) |
Mar
(105) |
Apr
(64) |
May
(56) |
Jun
(97) |
Jul
(180) |
Aug
(103) |
Sep
(54) |
Oct
(21) |
Nov
(44) |
Dec
(27) |
2002 |
Jan
(7) |
Feb
(10) |
Mar
(88) |
Apr
(57) |
May
(29) |
Jun
(12) |
Jul
(13) |
Aug
(35) |
Sep
(12) |
Oct
(16) |
Nov
(48) |
Dec
(94) |
2003 |
Jan
(36) |
Feb
(43) |
Mar
(124) |
Apr
(63) |
May
(77) |
Jun
(12) |
Jul
(7) |
Aug
(40) |
Sep
(41) |
Oct
(19) |
Nov
(22) |
Dec
(46) |
2004 |
Jan
(51) |
Feb
(129) |
Mar
(82) |
Apr
(96) |
May
(34) |
Jun
(28) |
Jul
(107) |
Aug
(87) |
Sep
(21) |
Oct
(50) |
Nov
(202) |
Dec
(110) |
2005 |
Jan
(174) |
Feb
(159) |
Mar
(250) |
Apr
(287) |
May
(159) |
Jun
(139) |
Jul
(305) |
Aug
(291) |
Sep
(558) |
Oct
(628) |
Nov
(539) |
Dec
(396) |
2006 |
Jan
(828) |
Feb
(470) |
Mar
(888) |
Apr
(524) |
May
(518) |
Jun
(424) |
Jul
(527) |
Aug
(208) |
Sep
(257) |
Oct
(276) |
Nov
(308) |
Dec
(342) |
2007 |
Jan
(366) |
Feb
(350) |
Mar
(265) |
Apr
(406) |
May
(481) |
Jun
(354) |
Jul
(195) |
Aug
(219) |
Sep
(506) |
Oct
(434) |
Nov
(467) |
Dec
(399) |
2008 |
Jan
(339) |
Feb
(185) |
Mar
(172) |
Apr
(191) |
May
(126) |
Jun
(149) |
Jul
(424) |
Aug
(317) |
Sep
(164) |
Oct
(246) |
Nov
(110) |
Dec
(123) |
2009 |
Jan
(82) |
Feb
(74) |
Mar
(125) |
Apr
(133) |
May
(51) |
Jun
(52) |
Jul
(37) |
Aug
(48) |
Sep
(60) |
Oct
(69) |
Nov
(52) |
Dec
(60) |
2010 |
Jan
(55) |
Feb
(69) |
Mar
(55) |
Apr
(144) |
May
(309) |
Jun
(318) |
Jul
(114) |
Aug
(128) |
Sep
(122) |
Oct
(96) |
Nov
(274) |
Dec
(219) |
2011 |
Jan
(223) |
Feb
(241) |
Mar
(266) |
Apr
(286) |
May
(251) |
Jun
(214) |
Jul
(308) |
Aug
(312) |
Sep
(192) |
Oct
(61) |
Nov
(20) |
Dec
(35) |
2012 |
Jan
(165) |
Feb
(70) |
Mar
(102) |
Apr
(96) |
May
(101) |
Jun
(125) |
Jul
(59) |
Aug
(108) |
Sep
(246) |
Oct
(372) |
Nov
(456) |
Dec
(374) |
2013 |
Jan
(215) |
Feb
(402) |
Mar
(386) |
Apr
(274) |
May
(117) |
Jun
(52) |
Jul
(125) |
Aug
(106) |
Sep
(188) |
Oct
(139) |
Nov
(74) |
Dec
(52) |
2014 |
Jan
(301) |
Feb
(62) |
Mar
(229) |
Apr
(85) |
May
(275) |
Jun
(138) |
Jul
(143) |
Aug
(121) |
Sep
(147) |
Oct
(278) |
Nov
(86) |
Dec
(100) |
2015 |
Jan
(113) |
Feb
(92) |
Mar
(96) |
Apr
(273) |
May
(122) |
Jun
(128) |
Jul
(41) |
Aug
(33) |
Sep
(161) |
Oct
(21) |
Nov
(71) |
Dec
(18) |
2016 |
Jan
(243) |
Feb
(35) |
Mar
(98) |
Apr
(102) |
May
(29) |
Jun
(7) |
Jul
(25) |
Aug
(25) |
Sep
(10) |
Oct
(10) |
Nov
(19) |
Dec
(8) |
2017 |
Jan
(18) |
Feb
(8) |
Mar
(4) |
Apr
(18) |
May
(22) |
Jun
(13) |
Jul
(12) |
Aug
(4) |
Sep
(3) |
Oct
(6) |
Nov
(5) |
Dec
(2) |
2018 |
Jan
(6) |
Feb
(2) |
Mar
(1) |
Apr
(4) |
May
(3) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
(4) |
Oct
(2) |
Nov
|
Dec
|
2019 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(2) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
(1) |
Apr
(4) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Nicholas L. <nj...@pl...> - 2000-09-17 06:50:09
|
Some step towards first stage modulisation. Made to modifications to clarify the scope needed for some of the wikicfg.pm variables. Goal: reduce dependency on global (use var) variables, maybe something like the perl Config.pm module. Added wikistore.pm as the access point for revCmd* variables. Probably move some more of the functions from wiki.pm to wikistore.pm as I consider them. Goal: make it easy to figure out the dependencies in order to work on PackegeTWikiStore. Replaced cpCmd with File::Copy from std library. Unless people disagree, I also intend to move wiki.pm to Wiki.pm. In order to more match the perl std module naming method. As time permits I'll be creating things like Wiki::* modules to replace wiki*.pm. Once that is done it might be possible to create a Makefile.PL install process. Include checking for binary locations. Eventual goal would be to create some upgrade mechanism. Nicholas |
From: Peter T. <pe...@th...> - 2000-09-10 08:15:05
|
Dear TWiki mailing list subscriber, the following email will go out to all registered Beta users momentarily. (If you are on both lists you will get it twice, sorry!) ----- Dear TWiki Beta team, I am sending this email because you requested the TWiki source in the past and asked to be notified of new TWiki Beta releases. Please drop me a line if you do not wish to receive further TWiki announcements. A new TWiki Beta version is available: Beta release 09 Sep 2000. Download instructions follow. Changes since the last production release (01 May 2000) * Advanced search features for searching multiple webs; sorting by topic name / modified time / author and more. * Fixed security issue to prevent a server side %INCLUDE% of arbitrary files. * More forgiving Wiki syntax. * Some other changes and fixes. The complete change history is at http://TWiki.SourceForge.net/cgi-bin/view/TWiki/TWikiHistory Upgrading from the 01 May 2000 version is described in http://TWiki.SourceForge.net/cgi-bin/view/TWiki/TWikiUpgradeNotes Check out also the TWiki add ons at http://TWiki.SourceForge.net/cgi-bin/view/Codev/FeatureAddOn There is a drawing applet that lets you embed editable images in a TWiki page! The place to collaborate on the TWiki development is at http://twiki.sourceforge.net/cgi-bin/view/Codev/WebHome . ReadmeFirst tells you more about our development process. If interested you can subscribe to the TWiki.Codev web and also to the TWiki-Dev mailing list. You are welcome to use the latest Beta or Alpha releases. To get a Beta you need first to create an account at http://TWiki.SourceForge.net/cgi-bin/view/TWiki/TWikiRegistration if you have not done already. Then you can download the Beta releases from http://TWiki.SourceForge.net/release/ Directory README: > ==================================================== > T W i k i R E L E A S E S > ==================================================== > > This URL contains the source code releases of TWiki: > > TWiki<yyy><mm><dd>.zip -- Production releases > TWiki<yyy><mm><dd>beta.zip -- Beta releases > > Beta releases are usually quiet stable, but are not > announced. Codevelopers are invited to bookmark this > URL and download the latest releases when needed. > > NOTE: Please do not link this URL from a public > web site. Also, please do not announce this URL > anywhere, it is reserved for TWiki codevelopers. > Users should request the TWiki source from > http://TWiki.SourceForge.net/ If you use the Beta for your production you need to change the tool name from TWikibeta to TWiki in wikicfg.pm. (The current Beta is stable, ready for production use) You can get Alpha releases from the CVS repository. ReadmeFirst in the TWiki.Codev web has more on that. TWiki is getting more and more popular. We have now many downloads per day. TWiki is mainly used behind corporate firewalls, including many major companies, like 3Com, AMD, Alcatel, Amazon.com, AT&T , .... through Xerox. TWiki got some good marks in the press, i.e check out the Software Carpentry, JonUdell, Internet Groupware for Scientific Collaboration at http://software-carpentry.codesourcery.com/Groupware/report.html . More to come soon... :-) Also, word of mouth is a good way of spreading the TWiki tool; any help is appreciated! If you have a successful deployment of TWiki we would *really* appreciate if you could support the TWiki community by writing a TWiki success story. This helps in promoting the tool, which in turn will result in a better product. More on that at http://TWiki.SourceForge.net/cgi-bin/view/Main/TWikiSuccessStories Best regards and happy TWiki'ing, Peter -- http://TWiki.SourceForge.net/ |
From: Nicholas L. <nj...@pl...> - 2000-08-09 05:57:58
|
On Tue, Aug 08, 2000 at 10:34:45PM -0700, Adam Montville wrote: > I'm not sure if this is the proper place for me to be asking this, but > I'm having a problem installing Twiki on my linux box. The environment > is as follows: Generally you can ask these questions via TWiki itself. > I have everything configured such that I can see what I am > supposed to see, not see what I am not supposed to see, BUT, the > scripts never execute within Apache. That is to say, if I pull up > http://www.mydomain.com/twiki/bin/view, I see the actual script rather > than what that script is supposed to output. Are the permissions set correctly? I've noticed in on my debian box that I do have to set the owner excute bit. In contra to what it said in the documentation: " The scripts execute as nobody . Set the file permission of all Perl scripts in the twiki/bin directory as executable to -rw-r-xr-x . " YMMV > > Any help and/or direction is appreciated, and I thank you in advance > for your time. Generally in these situations is best to post your configuration details as well. {srm,access}.conf, etc. Nicholas |
From: Adam M. <mon...@fl...> - 2000-08-09 05:52:33
|
I do apologize for the last message -- that problem appears to be fixed = by swapping the Alias and ScriptAlias directives in srm.conf (as = indicated at = http://twiki.sourceforge.net/cgi-bin/view/Codev/KnownIssuesOfTWiki01May20= 00). I happened across that page immediately after I had sent the last = e-mail. Now, however, I have the problem of an Internal Server Error. The = Apache error log tells me: "Premature end of script headers: = /home/httpd/twiki/bin/testenv". This is an example. The same thing = happens when I type in "view" instead of "testenv". I believe that I = should not need to set the SCRIPTSUFFIX twiki variable, because I can = execute the scripts at the command line without the suffix. =20 Any ideas? Thanks again, and, once again, I apologize for the inconvenience. Adam |
From: Adam M. <mon...@fl...> - 2000-08-09 05:38:35
|
I'm not sure if this is the proper place for me to be asking this, but = I'm having a problem installing Twiki on my linux box. The environment = is as follows: apache: 1.3.12-2 mod_perl: 1.21-10 perl: 5.00503-10 I have everything configured such that I can see what I am supposed to = see, not see what I am not supposed to see, BUT, the scripts never = execute within Apache. That is to say, if I pull up = http://www.mydomain.com/twiki/bin/view, I see the actual script rather = than what that script is supposed to output. The Apache directives have been placed in access.conf and srm.conf as = indicated by the TWikiDocumentation.html file that is supplied with the = distribution. It appears that this may be an Apache problem, but I = thought that someone with Twiki experience might be able to make an = assist in this case. Any help and/or direction is appreciated, and I thank you in advance for = your time. Regards, Adam Montville |
From: Peter T. <pe...@th...> - 2000-08-03 05:08:29
|
FYI, I will be travelling abroad and will come back in mid August. I will read my email but have limited time to contribute on TWiki during that time. Regards, Peter -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Peter T. <pe...@th...> - 2000-07-15 18:01:41
|
Hi, I am resending below email because I sent it with Japanese font encoding, and not all clients can display this. I apologize for the "spam". Regards, Peter -------- Original Message -------- Subject: Re: [TWiki-Dev] Recent problems - solved Date: Sat, 15 Jul 2000 03:18:43 -0700 From: Peter Thoeny <pe...@th...> Organization: http://www.thoeny.com/peter/ To: Wol...@ic...,twi...@li..., alt...@ie...,za...@ma... Dear TWiki development team, SourceForge did not respond in time to restore the data that got corrupted during the raid failure. Rather then waiting any longer I decided to restore the data manually. TWiki is now online again, please start using it! I could not restore all changes in TWiki.Codev that have been done between 05 Jul 2000 and 07 Jul 2000. People who contributed in that time frame should check the content if some of their content is missing. In particular: * TWikiPresentation (WolfgangSteinke) * PackageTWikiStore (NicholasLee et al) * WikiClusters (MichaelSparks et al) * BetterFileLocking (PeterThoeny et al) * RenameTheMainWeb (PeterThoeny et al) * UseHtmlEditorOfChoice (KevinKinnell et al) * ManagementTools (JohnAltstadt et al) Also people who updated topics in the Main web should review the content: * TWikiClones (MichaelSparks et al) * MichaelSparks (MichaelSparks) * JohnAltstadt (JohnAltstadt) Regards, Peter Peter Thoeny wrote: > > To summarize, here is what happened. > > * Beginning of July: SourceForge switches from one > project web server to two load balanced web servers > (oakenfold and nirvana). Each SourceForge project > gets one IP address, and each incoming request is > diverted to one of the two web servers. Both servers > read project data from the project file server over > NFS. > > * 07 Jul 2000: SourceForge had a Raid failure where > two harddisk crashed and about 100 MB of data got > lost or corrupted. > > TWiki data got corrupted: Some .txt and .txt,v files > are missing, some files are replaced by some arbitrary > content like source code. I first I suspected that it > had to do with the load balancing. However, several > issues point to the Raid failure as being the cause: > * Static HTML files and one cgi file got also corrupted. > * Files got corrupted where the likelihood of > simultaneous update is extremely low, i.e. the > JonUdell page. > * Only files got corrupted that have been changed > since 06 Jul 2000. > * I did about 30 successive saves today in the Test > web (edit is renamed to edit.disable) without any > hitch. > > I requested SourceForge several times to restore > the TWiki project from backup, I am still waiting. > I do have an about 3 weeks old backup. SourceForge > does a daily full backup, so they should have the > data of last Thursday. I also made a backup of the > (partially corrupted) data on Saturday. Once > SourceForge restored from backup I can merge the > latest updates. We just have to wait some more. > > Do we really need a network file locking, now that > SourceForge is using two web servers accessing the > same one file server via NFS? There should be no problem > as long as we don't save the same file at the same time. > This theoretically happens only if someone breaks the > lock, and both save at the same time, very unlikely to > happen. > > Regarding Perl version, how common is 5.005? If deployed > by over 80% I would go for the it. What is special that > you would like to require 5.005? > > Regards, > Peter -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Peter T. <pe...@th...> - 2000-07-15 10:19:02
|
Dear TWiki development team, SourceForge did not respond in time to restore the data that got corrupted during the raid failure. Rather then waiting any longer I decided to restore the data manually. TWiki is now online again, please start using it! I could not restore all changes in TWiki.Codev that have been done between 05 Jul 2000 and 07 Jul 2000. People who contributed in that time frame should check the content if some of their content is missing. In particular: * TWikiPresentation (WolfgangSteinke) * PackageTWikiStore (NicholasLee et al) * WikiClusters (MichaelSparks et al) * BetterFileLocking (PeterThoeny et al) * RenameTheMainWeb (PeterThoeny et al) * UseHtmlEditorOfChoice (KevinKinnell et al) * ManagementTools (JohnAltstadt et al) Also people who updated topics in the Main web should review the content: * TWikiClones (MichaelSparks et al) * MichaelSparks (MichaelSparks) * JohnAltstadt (JohnAltstadt) Regards, Peter Peter Thoeny wrote: > > To summarize, here is what happened. > > * Beginning of July: SourceForge switches from one > project web server to two load balanced web servers > (oakenfold and nirvana). Each SourceForge project > gets one IP address, and each incoming request is > diverted to one of the two web servers. Both servers > read project data from the project file server over > NFS. > > * 07 Jul 2000: SourceForge had a Raid failure where > two harddisk crashed and about 100 MB of data got > lost or corrupted. > > TWiki data got corrupted: Some .txt and .txt,v files > are missing, some files are replaced by some arbitrary > content like source code. I first I suspected that it > had to do with the load balancing. However, several > issues point to the Raid failure as being the cause: > * Static HTML files and one cgi file got also corrupted. > * Files got corrupted where the likelihood of > simultaneous update is extremely low, i.e. the > JonUdell page. > * Only files got corrupted that have been changed > since 06 Jul 2000. > * I did about 30 successive saves today in the Test > web (edit is renamed to edit.disable) without any > hitch. > > I requested SourceForge several times to restore > the TWiki project from backup, I am still waiting. > I do have an about 3 weeks old backup. SourceForge > does a daily full backup, so they should have the > data of last Thursday. I also made a backup of the > (partially corrupted) data on Saturday. Once > SourceForge restored from backup I can merge the > latest updates. We just have to wait some more. > > Do we really need a network file locking, now that > SourceForge is using two web servers accessing the > same one file server via NFS? There should be no problem > as long as we don't save the same file at the same time. > This theoretically happens only if someone breaks the > lock, and both save at the same time, very unlikely to > happen. > > Regarding Perl version, how common is 5.005? If deployed > by over 80% I would go for the it. What is special that > you would like to require 5.005? > > Regards, > Peter -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Nicholas L. <nj....@ki...> - 2000-07-15 00:29:34
|
This is pretty cool. 8) Might be useful in bits of TWiki, although not sure if it will help s/// much. http://prometheus.frii.com/~gnat/yapc/2000-stages/slide48.html http://prometheus.frii.com/~gnat/yapc/2000-stages/slide49.html Nicholas |
From: Kevin K. <ke...@ne...> - 2000-07-10 16:03:19
|
At 11:10 PM 7/9/00 -0700, Peter Thoeny wrote: >Regarding Perl version, how common is 5.005? If deployed >by over 80% I would go for the it. What is special that >you would like to require 5.005? Mainly it's the availability of the ``qr//'' quote-like operator. Being able to compile an arbitrary regexp is really nice, and makes coding the Pure-Perl grep functions much nicer. The rest of the search enhancements get much easier and faster. --kevin BTW: My edit got lost in the raid problem, but there is a very interesting piece of software at http://www.indigostar.com/indigoperl.htm This is a win32 perl5.6.0 with a built-in apache server. It's freeware. --kk |
From: Peter T. <pe...@th...> - 2000-07-10 06:18:55
|
To summarize, here is what happened. * Beginning of July: SourceForge switches from one project web server to two load balanced web servers (oakenfold and nirvana). Each SourceForge project gets one IP address, and each incoming request is diverted to one of the two web servers. Both servers read project data from the project file server over NFS. * 07 Jul 2000: SourceForge had a Raid failure where two harddisk crashed and about 100 MB of data got lost or corrupted. TWiki data got corrupted: Some .txt and .txt,v files are missing, some files are replaced by some arbitrary content like source code. I first I suspected that it had to do with the load balancing. However, several issues point to the Raid failure as being the cause: * Static HTML files and one cgi file got also corrupted. * Files got corrupted where the likelihood of simultaneous update is extremely low, i.e. the JonUdell page. * Only files got corrupted that have been changed since 06 Jul 2000. * I did about 30 successive saves today in the Test web (edit is renamed to edit.disable) without any hitch. I requested SourceForge several times to restore the TWiki project from backup, I am still waiting. I do have an about 3 weeks old backup. SourceForge does a daily full backup, so they should have the data of last Thursday. I also made a backup of the (partially corrupted) data on Saturday. Once SourceForge restored from backup I can merge the latest updates. We just have to wait some more. Do we really need a network file locking, now that SourceForge is using two web servers accessing the same one file server via NFS? There should be no problem as long as we don't save the same file at the same time. This theoretically happens only if someone breaks the lock, and both save at the same time, very unlikely to happen. Regarding Perl version, how common is 5.005? If deployed by over 80% I would go for the it. What is special that you would like to require 5.005? Regards, Peter Kevin Kinnell wrote: > > The staff at Sourceforge have been very forthcoming during the recent > difficulties, which has made them easier to bear. But, it looks like > our difficulties may be due to more than just one raid failure. Nicholas > Lee pointed out that TWiki is not really ready for NFS. There is a > recipe in the Ram that makes an attempt to address network file locking > (7.21. Program: netlock, pp. 264-266) BUT the authors don't appear to have > much faith that it will work no matter what. It may be the best hope > for now. > > Since we can't rely on TWiki for the moment, we may need to work out > what to do on the mailing list... > > Currently, I'm trying to make the netlock work with TWiki; but I'll > abandon that if we are going to end up hosting elsewhere for a while. > (We'll end up having to address this, regardless.) Should I keep > going? > > Also, what perl should we require for TWiki to operate? I vote 5.005. > > -- > Kevin Kinnell <ke...@ne...> > perl -e 'print unpack("u",q,9`#`@(&430$%:1C4W<APD/"-T!BHD(2(F00``, > )^($_=(join" ",reverse(qw/HACK ANOTHER PERL JESTER..../) > )[0],s/ //g)[0];' > > _______________________________________________ > TWiki-Dev mailing list > TWi...@li... > http://lists.sourceforge.net/mailman/listinfo/twiki-dev -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Nicholas L. <nj....@ki...> - 2000-07-10 06:15:09
|
> Lee pointed out that TWiki is not really ready for NFS. There is a > recipe in the Ram that makes an attempt to address network file locking > (7.21. Program: netlock, pp. 264-266) BUT the authors don't appear to have > much faith that it will work no matter what. It may be the best hope > for now. NFS is like that I guess. The only issue at the moment AFAI can tell with NFS and loaded balanced server like sourceforge have at the moment is if a user (browser) stops and restarts a save attempt. It can become a race condition if the web/nfs servers are loaded. TWiki's soft locking should be sufficent in most other cases. One potential way around it is to do something like qmail: save to WebName.txt:User.PID.Time, then rename to WebName.txt. All stuff I'm trying nutting out in my head at the moment for the TWiki::Store package. Of course the other problem I'm not so sure about is how 'NFS-safe' is rcs. > Currently, I'm trying to make the netlock work with TWiki; but I'll > abandon that if we are going to end up hosting elsewhere for a while. > (We'll end up having to address this, regardless.) Should I keep > going? There are potentially two points of issue: saveFile and the write to ".changes" in saveTopic. The first is probably alright currently because of the topic locking. The later generally because writes are are rare. However, a couple flocks at those two locations aren't going to hunt anything. Since the web enviroment is pretty straightforward a BLOCKING flock should be sufficent. In the worse case a user will reload, and the CGI exiting will close any open file handles/locks. Closing files handles in mod_perl and flocks in win32 is a different issue. Nicholas |
From: Kevin K. <ke...@ne...> - 2000-07-10 04:59:39
|
The staff at Sourceforge have been very forthcoming during the recent difficulties, which has made them easier to bear. But, it looks like our difficulties may be due to more than just one raid failure. Nicholas Lee pointed out that TWiki is not really ready for NFS. There is a recipe in the Ram that makes an attempt to address network file locking (7.21. Program: netlock, pp. 264-266) BUT the authors don't appear to have much faith that it will work no matter what. It may be the best hope for now. Since we can't rely on TWiki for the moment, we may need to work out what to do on the mailing list... Currently, I'm trying to make the netlock work with TWiki; but I'll abandon that if we are going to end up hosting elsewhere for a while. (We'll end up having to address this, regardless.) Should I keep going? Also, what perl should we require for TWiki to operate? I vote 5.005. -- Kevin Kinnell <ke...@ne...> perl -e 'print unpack("u",q,9`#`@(&430$%:1C4W<APD/"-T!BHD(2(F00``, )^($_=(join" ",reverse(qw/HACK ANOTHER PERL JESTER..../) )[0],s/ //g)[0];' |
From: Nicholas L. <nj....@ki...> - 2000-07-08 22:49:19
|
> > Now we have even a more serious problem - corrupt data. I haven't been very active, but how recent was the corruption? Looks like this might be the most recent cause: http://sourceforge.net/forum/forum.php?forum_id=24823 "100Mb of corrupted data". Contact pre...@so... to backup restores. > Lets give it some more days. If it does not improve we > will take some actions, like move somewhere else. I've found http://sunsite.auc.dk very good in my travels. They don't offer shell access though. Might be a good mirror site though. Looks like we'll have to come up with some sort of hacked together mirroring process. Nicholas |
From: Peter T. <pe...@th...> - 2000-07-08 20:34:55
|
I updated index.html as you suggested, see http://TWiki.SourceForge.net/ See also Support Request #103294, https://sourceforge.net/support/?func=detailsupport&support_id=103294&group_id=1 What does it mean "to get rooted"? Peter Kevin Kinnell wrote: > > Peter, can you add a link to your service request into the main page > (http://twiki.sourceforge.net/index.html)? I'm very interested in seeing > how they explain this latest fiasco [*if* they explain it, they're not > very good about feedback.] For the record, I couldn't even hit the site > last night, let alone the cgi. My guess is that twiki.sourceforge.net > got ``rooted'' and that's why all the files are messed up; but we have no > way to check. > > -- > Kevin Kinnell <ke...@ne...> > > > Message: 1 > > From: "Nicholas Lee" <nj....@ki...> > > To: <twi...@li...> > > Date: Sat, 8 Jul 2000 23:26:01 +1200 > > charset="iso-8859-1" > > Subject: [TWiki-Dev] Sourceforge stability > > > > Sourceforge has been very flaky recently. I can't access TWiki right at the > > moment. Maybe we need to i) move elsewhere, ii) sort out some mirroring, > > and/or iii) figure out if we can do/code anything to improve the situation. > > > > Nicholas > > > > --__--__-- > > > > Message: 2 > > Date: Sat, 08 Jul 2000 11:06:58 -0700 > > From: Peter Thoeny <pe...@th...> > > Organization: http://www.thoeny.com/peter/ > > To: Nicholas Lee <nj....@ki...>, twi...@li... > > Subject: Re: [TWiki-Dev] Sourceforge stability > > > > Very flaky indeed, and this has been going on for weeks. > > > > Now we have even a more serious problem - corrupt data. > > Some .txt files are missing or corrupt, some .txt,v > > files as well. For example TWikiUsers.txt is blank and > > TWikiUsers.txt,v is missing, or JonUdell.txt is replaced > > by some source code! For now I disabled edit, attach and > > register in TWiki. > > > > I will file a support request with SrcF. > > > > Lets give it some more days. If it does not improve we > > will take some actions, like move somewhere else. > > > > Peter > > _______________________________________________ > TWiki-Dev mailing list > TWi...@li... > http://lists.sourceforge.net/mailman/listinfo/twiki-dev -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Kevin K. <ke...@ne...> - 2000-07-08 20:12:26
|
Peter, can you add a link to your service request into the main page (http://twiki.sourceforge.net/index.html)? I'm very interested in seeing how they explain this latest fiasco [*if* they explain it, they're not very good about feedback.] For the record, I couldn't even hit the site last night, let alone the cgi. My guess is that twiki.sourceforge.net got ``rooted'' and that's why all the files are messed up; but we have no way to check. -- Kevin Kinnell <ke...@ne...> > Message: 1 > From: "Nicholas Lee" <nj....@ki...> > To: <twi...@li...> > Date: Sat, 8 Jul 2000 23:26:01 +1200 > charset="iso-8859-1" > Subject: [TWiki-Dev] Sourceforge stability > > Sourceforge has been very flaky recently. I can't access TWiki right at the > moment. Maybe we need to i) move elsewhere, ii) sort out some mirroring, > and/or iii) figure out if we can do/code anything to improve the situation. > > Nicholas > > --__--__-- > > Message: 2 > Date: Sat, 08 Jul 2000 11:06:58 -0700 > From: Peter Thoeny <pe...@th...> > Organization: http://www.thoeny.com/peter/ > To: Nicholas Lee <nj....@ki...>, twi...@li... > Subject: Re: [TWiki-Dev] Sourceforge stability > > Very flaky indeed, and this has been going on for weeks. > > Now we have even a more serious problem - corrupt data. > Some .txt files are missing or corrupt, some .txt,v > files as well. For example TWikiUsers.txt is blank and > TWikiUsers.txt,v is missing, or JonUdell.txt is replaced > by some source code! For now I disabled edit, attach and > register in TWiki. > > I will file a support request with SrcF. > > Lets give it some more days. If it does not improve we > will take some actions, like move somewhere else. > > Peter |
From: Peter T. <pe...@th...> - 2000-07-08 18:16:40
|
Very flaky indeed, and this has been going on for weeks. Now we have even a more serious problem - corrupt data. Some .txt files are missing or corrupt, some .txt,v files as well. For example TWikiUsers.txt is blank and TWikiUsers.txt,v is missing, or JonUdell.txt is replaced by some source code! For now I disabled edit, attach and register in TWiki. I will file a support request with SrcF. Lets give it some more days. If it does not improve we will take some actions, like move somewhere else. Peter Nicholas Lee wrote: > > Sourceforge has been very flaky recently. I can't access TWiki right at the > moment. Maybe we need to i) move elsewhere, ii) sort out some mirroring, > and/or iii) figure out if we can do/code anything to improve the situation. > > Nicholas -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Nicholas L. <nj....@ki...> - 2000-07-08 11:35:59
|
Sourceforge has been very flaky recently. I can't access TWiki right at the moment. Maybe we need to i) move elsewhere, ii) sort out some mirroring, and/or iii) figure out if we can do/code anything to improve the situation. Nicholas |
From: Peter T. <pe...@th...> - 2000-06-22 05:23:33
|
Dear TWiki folks, the SourceForge web site is still unreliable since the server move on Sunday. CGI scripts sporadically do not run (Internal Server Error). This happend to me sometimes on Monday. many times on Tuesday and now again on Wednesday. Note that the scripts of the main installation have not been changed in a while, and that the same problem happens also with other projects. I filed a support request today, see https://sourceforge.net/support/?func=detailsupport&support_id=102783&group_id=1 I guess we have to wait for SourceForge to take some actions. Anyway you can try to contribute, just wait for a minute or so if you get the error message ans try again. FYI, Peter Kevin Kinnell wrote: > > What's up with the twiki.sourceforge.net site? > I haven't been able hit it for a couple of days, now. > > -- > Kevin Kinnell <ke...@ne...> -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Peter T. <pe...@th...> - 2000-06-18 20:32:13
|
SourceForge finished the server move. Everything should be restored by now. You can start contributing again. FYI, the project name changed to lower case, e.g. from /home/groups/TWiki to /home/groups/twiki . Symbolic links make the upper case version still accessible, but this is only temporarily. Peter Peter Thoeny wrote: > > Dear TWiki developer, > > In the passed week we had some sporadic "Server not responding" > or "Internal Server Error" when trying to access a TWiki page > at SourceForge. > > SourceForge is currently moving the open source projects to a > new hardware, the URL will not change. Anything you write now > will be lost. Please wait with contributions until about Sunday > evening. I will send an email when everything is restored. > > Best regards, > Peter -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Peter T. <pe...@th...> - 2000-06-18 00:46:02
|
Dear TWiki developer, In the passed week we had some sporadic "Server not responding" or "Internal Server Error" when trying to access a TWiki page at SourceForge. SourceForge is currently moving the open source projects to a new hardware, the URL will not change. Anything you write now will be lost. Please wait with contributions until about Sunday evening. I will send an email when everything is restored. Best regards, Peter -- ||| Peter Thoeny mailto:Peter@Thoeny.com (o o) 7203 Via Vico +---oOO--( )--OOo---+ San Jose, CA 95129, USA | If it is to be | Phone: +1-408-255-1477 (UTC -8h) | It is up to me | http://www.thoeny.com/peter/ +==oOO====v====OOo==+ |
From: Peter T. <Peter.Thoeny@WindRiver.com> - 2000-05-23 22:02:55
|
I agree. Collaborating the Wiki way is more organized then email. May I suggest to use the mailing list for "volatile" information only. -- PeterThoeny - 23 May 2000 Alain Penders wrote: > > I just reread all the comments on Twiki and CVS, and added some new ones > to TWikiWithCVS and TWikiXML. (Seemed like a better idea than writing > them in an email.) > > Alain |
From: Nicholas L. <nj....@ki...> - 2000-05-23 12:35:05
|
Here is a quick patch to remove at least two system calls per view. Basically gets the author, date and reversion fields directly from the rcs files. I'm not sure how rcsfiles differ from unix to unix. The patch is pretty straight forward. Just a matter of getting the right regexp. The trickier part of grabbing the HEAD reversion requires more work. I probably wont worry about it too much. Since I'm not 100% about the portability yet, I wont put it up on twiki just yet. I'd be interested if people with loaded systems see any improve with this patch. Nicholas |
From: Alain P. <al...@pu...> - 2000-05-22 23:57:10
|
I just reread all the comments on Twiki and CVS, and added some new ones to TWikiWithCVS and TWikiXML. (Seemed like a better idea than writing them in an email.) Alain On Tue, May 23, 2000 at 10:25:22AM +1200, Nicholas Lee wrote: > >> While reading all the documents online, I ran into the discussion on using >> CVS for TWiki instead of RCS. What is the status of this? Is it still >> being worked on? > >The verision I was working on is on the back burner at the moment. I had >some problems with storing the Author name I was sure how to work around. I >think I might have a solution to that. > >Long term I want to create some native tools. That way I avoid system pipes >and it makes it easier to design non-www interfaces to the information. > >> We're having the following issues for which using CVS would provide a good >> solution: >> >[...] >So you basically want access to the text files for people to edit? > >I've got a very pre-alpha version of the cvs code I'll send seperately if >you want to look at it. It 'barely' works and its the code discussed (by >myself) in the TWikiWithCVS web. > >Its really not much change the base code, but some things need to be >redesigned. I'm swamped at the moment so I haven't really had the chance >to think it much. > >Nicholas > > >_______________________________________________ >TWiki-Dev mailing list >TWi...@li... >http://lists.sourceforge.net/mailman/listinfo/twiki-dev |
From: Nicholas L. <nj....@ki...> - 2000-05-22 22:30:46
|
> While reading all the documents online, I ran into the discussion on using > CVS for TWiki instead of RCS. What is the status of this? Is it still > being worked on? The verision I was working on is on the back burner at the moment. I had some problems with storing the Author name I was sure how to work around. I think I might have a solution to that. Long term I want to create some native tools. That way I avoid system pipes and it makes it easier to design non-www interfaces to the information. > We're having the following issues for which using CVS would provide a good > solution: > [...] So you basically want access to the text files for people to edit? I've got a very pre-alpha version of the cvs code I'll send seperately if you want to look at it. It 'barely' works and its the code discussed (by myself) in the TWikiWithCVS web. Its really not much change the base code, but some things need to be redesigned. I'm swamped at the moment so I haven't really had the chance to think it much. Nicholas |