Looking at this code makes me think life would be good with URI::SMB. This particular script would loose the
my $samba_user = "";
my $samba_password = "";
my $samba_remote_host = "";
my $samba_share = "";
my $samba_current_host = "";
#Samba Remote share subdir
#Empty means root share
#Could be combined with $ENV{HOSTNAME}
part. I would then use Getopts::Long to change the interface to something like:
$0 --(daily|weekly|hourly|etc) --smb=smb://user:pass@host/share
If --smb was not set, it could check the env before dieing.
And it would be really helpful if Filesys::SmbClientParser accepted one of these.
Have you thought about use URI's for your db file? That way you can back up not just local files, but files on other smb hosts, webpages, ftp files or hunks of ldap. Well, anything that uri supports and has a client for.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
