[1596] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next last

Re: Error message returned to console when @backup is called

daemon@ATHENA.MIT.EDU (Tue Jun 27 21:02:19 2000 )

Date: Tue, 27 Jun 2000 15:37:01 -0700 (PDT)
From: Jeremy Weatherford <xidus@xidus.net>
To: coldstuff@cold.org
In-Reply-To: <000001bfdee0$ea5d8020$0200a8c0@nycap.rr.comDEST>
Reply-To: coldstuff@cold.org


All I can tell you is that it happens to me too, and I haven't bothered
figuring it out yet, since I'm in the process of writing my own core.  :)

BTW, I've finally found a useful place to use frobs.  I'm still working
out my own implementation, but I'll try to make the frob-related code
available for people interested.  The core I'm working on will eventually
be available itself, as well.  I'm using frobs to store exit information
in rooms right now, and it's working out very well.

Happy hacking,

Jeremy Weatherford
xidus@xidus.net
http://xidus.net

On Sun, 25 Jun 2000, Peter Bombard wrote:

> I've done a pretty standard install on Caldera Openlinux 2.3
> 
> Whenever I issue the @backup command I see the following on the console:
> 
> mv: binary.bak: No such file or directory
> tar: Cannot add file binary-25Jun100: No such file or directory
> tar: Error exit delayed from previous errors
> /bin/cp: binary-25Jun100.tar.gz: No such file or directory
> /bin/cp: binary-25Jun100.tar.gz: No such file or directory
> /bin/cp: binary-25Jun100.tar.gz: No such file or directory
> /bin/cp: binary-25Jun100.tar.gz: No such file or directory
> 
> -pete (PBombard@altavista.net) 
>