From: Chris S. <chr...@gm...> - 2010-01-19 23:14:19
|
I'm guessing there really isn't a problem. As best I can tell from this discussion, the file 18xx.log is only used for program debugging and can be ignored by players. If that is correct, then I think we are done. The issue is that we are running Rails within the shared Dropbox folder, so multiple people can open the same jar at the same time. This causes conflicts when generating the 18xx.log file. Everyone is using a shared my.properties file, so we can't change it on a player-by-player basis. The advantage of running Rails this way is versioning. I'm currently playing one game on 1.1.0 and another on 1.1.2. Keeping a separate copy of Rails for each game makes it easier for me to avoid accidentally opening a game in the wrong version. -- Chris Please consider the environment before printing this e-mail. On Tue, Jan 19, 2010 at 3:04 PM, Erik Vos <eri...@xs...> wrote: > Not sure what the problem is. > Are we talking about log files or save files? > You can set the log file location and name in your copy of my.properties: > log4j.appender.F.File=<path> > > Erik. > > ------------------------------ > *From:* Chris Shaffer [mailto:chr...@gm...] > *Sent:* Tuesday 19 January 2010 23:00 > *To:* Development list for Rails: an 18xx game > *Subject:* Re: [Rails-devel] Log file query > > Right, I understand that, but we are using Rails in the Dropbox directory > and sharing it. We know it is a slight security risk but keeping the > software version synchronized trumped that. > > So, the questions remain: > > 1) Is there any way to prevent Rails from saving the log file on exit if no > actions are taken; > 2) What are the conflicted log files, and what purpose do they serve; > 3) Are 1 and 2 the same question? > > -- > Chris > > Please consider the environment before printing this e-mail. > > > On Tue, Jan 19, 2010 at 1:53 PM, Aliza Panitz <ali...@gm...>wrote: > >> On Tue, Jan 19, 2010 at 1:36 PM, Chris Shaffer <chr...@gm...> >> wrote: >> > One of our players says: >> > >> >> It looks like the 18xx.log file mod. date is updated when you >> >> close a .rails file even if you don't make any changes. Is there >> >> a way to review the game without forcing an update to the >> >> log - other than copying the directory and opening that? >> >> If you use a copy of Rails in one directory to open a savefile in >> another directory, then the logfile is in the same directory as the >> software, not the data. >> >> For example, in my PBEM games the Dropbox shared file area has data >> files only, and we each run our own copies of the Rails software (a >> slightly more secure model, though a bit more error prone if players >> need to keep track of which software version to use with which game.) >> >> - Aliza >> >> >> ------------------------------------------------------------------------------ >> Throughout its 18-year history, RSA Conference consistently attracts the >> world's best and brightest in the field, creating opportunities for >> Conference >> attendees to learn about information security's most important issues >> through >> interactions with peers, luminaries and emerging and established >> companies. >> http://p.sf.net/sfu/rsaconf-dev2dev >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel >> > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > > |