error time on 0.4.1 (node) about forever

[indexzero]

formats changed from 0.3.x to 0.4.x so

forever stopall && rm -rf /tmp/forever

[weepy]

i'd never had 0.3.x installed . if i do that then it allows me to start - but then stops working - see here :

rrr@xxxxx:/u/apps/example# forever stopall && rm -rf /tmp/forever
info: Running action: stopall
info: No forever processes running
rrr@xxxxx:/u/apps/example# forever start -l log -e log -o log boot
info: Forever processing arguments arg=boot
info: Running action: start
rrr@xxxxx:/u/apps/example# forever stop boot                     
info: Forever processing arguments arg=boot
info: Running action: stop
info: Forever stopped process:
  [0] boot [17335, 17334] /tmp/forever/log 0:0:0:6.717
rrr@xxxxx:/u/apps/example# forever start -l log -e log -o log boot
info: Forever processing arguments arg=boot
info: Running action: start
error: Cannot start forever: log file /tmp/forever/log exists.

[indexzero]

This is by design. I've actually been debating the best thing to do here. You run start, then stop it, then start it again passing explicit paths for the location of the log files.

In this scenario do you want forever to

1. Overwrite those files
2. Append to those files
3. Throw an error telling you to remove those files

Currently it does (3), so that's why it is telling you error: Cannot start forever: log file /tmp/forever/log exists. ... I could change the behavior to be (1) or (2), but I've been unsure what users think.

[weepy]

[2] without a shadow of a doubt.

[indexzero]

ok, for now, just kill the file. I'll add that onto 0.4.2

[indexzero]

Added as an issue: https://github.com/indexzero/forever/issues/33