Sebastian Smith wrote:
- Multi-source, and Multi-destination (including to/from remote hosts
via ssl tunnel)
- Optional Parallelized execution
- Copy referent of symlinks - Preserve permission, ownership, etc
- Quiet operation (no output to stdout, stderr)
- Error handling
- Notification of errors
- Detailed logging
- Easy modification of scripts
It sounds like you covered the two biggest concerns from my perspective:
symlinks and flexible source/destination settings. What scheme are you
implementing for accessing a live file system? Especially with directory
structures like /var that will be constantly changing in a high-activity
environment (like the ones I work with), dealing with the volatility of the
environment consistently without effecting stability is vital.
I'm currently scripting in Bash, but will probably release in Perl, and
Python as I need practice in all.
If you would like any help with either of these languages, just ask. I write
most of my administrative scripts in one of these two languages (sh being the
third in line... ubiquitous as it is).
---
Brandon "smokey" Mitchell
_______________________________________________
RLUG mailing list
[email protected]
http://lists.rlug.org/mailman/listinfo/rlug
