TZUTC: -0600   
   MSGID: 53313.sync@1:103/705 2bce28b6   
   REPLY: 1459.fidonet_synchronet@1:3634/58 2bcca255   
   PID: Synchronet 3.20a-Linux master/6dbd2fec6 Dec 09 2024 GCC 11.2.0   
   TID: SBBSecho 3.23-Linux master/f9ad15e85 Dec 21 2024 GCC 12.2.0   
   BBSID: PALANTIR   
   CHRS: CP437 2   
   -=> Errol Casey wrote to Gamgee <=-   
      
    EC>   Re: Re: Error when disk full error occurs   
    EC>   By: Gamgee to Amessyroom on Mon Dec 23 2024 12:18 am   
      
    -=>> Amessyroom wrote to nightfall <=-   
      
    Am>> Ran into an error with SlyEdit and Vim when I filled my main partition.   
      
    Ga> Did you mean to write this to "NightFox"?  The auther of SlyEdit?   
      
    EC> Yes.  Rather than bothering him with direct netmail; thought I would   
    EC> use the echo for a general support item.   
      
   Right, but you didn't actually address it to him.  Got it.   
      
    Ga> You "filled your main partition"?  That wasn't a good idea.   
      
    EC> Nope. It was filled with backups.   
      
   So...... just so I understand this - you're writing your backups to the    
   same partition that the data comes from?  Does that seem like a wise    
   option to you?  Even one step further - should you be writing backups to    
   the same *disk* that the data lives on?   
      
    Am>> I've lost the exact error message. But may want to check space where the   
    Am>> temporary file is written, and capture even and display relevant message   
    Am>> and exit.   
      
    Ga> Or maybe keep an eye on your system, and don't fill up a partition.   
      
    EC> Yep . Expected it to happen but have not put in a cron job to clean   
    EC> things automatically.   
      
   Wow.  So you knew it would happen, but couldn't be bothered to prevent    
   it, either by writing the backups to some other location, or doing the    
   (5-minute) task of writing the cron entry?   
      
   Please tell me you're not a SysAdmin by trade...   
      
    Ga> You sure make a lot of mistakes, that seem to be caused by not paying   
    Ga> attention; and/or not bothering to read instructions properly.   
      
    EC> I'm only human. Not perfect.  I can see where you get that impression.   
      
   I'm not perfect either, but that isn't what this is about.  It's about    
   doing things in a reasonable manner.   
      
    Ga> At least your nick/handle makes some sense.   
      
    EC> Glad you find the nick applies.   
      
   Well I admit that is an assumption, but probably right.   
      
   Just so you don't think I'm a complete asshole, here's some advice:     
   It's really a *BAD* idea to be doing backups the way you are.  Send them    
   to another location such as another drive somewhere on your LAN, or even    
   to an off-site location such as the cloud.  Or both.   
      
   Also, pay attention to details.  Sometimes that's all it takes to make    
   the difference between success and failure.  Read instructions and    
   follow them correctly.  Sometimes you need to read those instructions    
   more than once.  Sometimes it takes 20 times to read them before getting    
   the full picture.  Take the time that's needed to understand.   
      
   Good luck and Happy Holidays.   
      
      
      
   ... Nothing is so smiple that it can't get screwed up.   
   --- MultiMail/Linux v0.52   
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 310/31   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 467/888 633/267 280 281 384 410 418 420 2744 712/848 770/1   
   SEEN-BY: 902/26 5020/400 5075/35   
   PATH: 103/705 280/464 633/280 229/426