On 2018-09-16 05:27, G.W. Haywood via BackupPC-users wrote:
Once again, thank you for your input. Do consider some restraint.
That's fair. Consider the context: you've already admitted to breaking
BackupPC after an upgrade and instead of methodically going through the
steps of getting it working again, you upgrade to a completely new
version, misunderstand how it works, and start mucking about with
internal tools from the command line, while demonstrating that you don't
know the side effects.
Is there a quick fix for this? Not if you're trying to solve one
problem with a completely unrelated tool: if you want to solve taking
too much space, there are better ways to do it. If you want to solve
rsync problems, there are better ways to do it.
You do have my apologies for any confusion I have caused -- so yes,
BackupPC_backupDelete is capable of removing directories from a share
that were backed up. Will this solve your problem, or is it a good
idea? No. Are you interpreting what it's doing and its side effects
properly? No. Did you get the syntax right? Hard to say, as you've
edited the command line and its responses -- and as I've already pointed
out, most people wouldn't run it from the command line, so if there are
quirks in how it handles directory input, a test case would be
warranted.
In many years of helping users who have wide variety in degrees of
expertise, I do struggle with people who demonstrate an incomplete
understanding of the tool they're trying to use, while insisting on
doing things that are, at best, orthogonal to their problem. It is
usually coupled with a healthy dose of failing to follow reasonable
steps up until that point, and unwinding that is difficult, if not
impossible. It is often unclear whether it is a problem of attention to
detail, ability to comprehend, missing fundamentals, poor
troubleshooting techniques, or an outsized ego.
Tech Support: "Okay, let's see what's in the directory. Type 'ls -l' "
Customer: [typing sounds continue for several minutes]
Tech Support: "Uh. Do you have a directory listing yet?"
Customer: "I read that hard drives need fsck'ing every now and then"
Tech Support: "It would help to know what's in that directory"
Customer: "It's rebooting now"
I'm open to suggestions as to how to be helpful in such situations. If
obliquely pointing toward the documentation doesn't work, would it be
better to be more direct? Would you prefer no response? What is the
best way to gently suggest that leaping to a solution before
understanding the problem is unlikely to yield satisfying results?
Thanks
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
