WatchDirectory home page
WatchDirectory Startseite (Deutsche Version)
Site WatchDirectory (Français)
  Welcome, Guest. Please Login or Register
YaBB - Yet another Bulletin Board
   
  HomeHelpSearchLoginRegister  
 
Page Index Toggle Pages: 1
UNC paths, not a bug, probably a feature request (Read 1618 times)
David Hostetter
YaBB Newbies
*
Offline



Posts: 8
UNC paths, not a bug, probably a feature request
Nov 17th, 2014 at 11:11pm
 
Hi, when monitoring UNC paths

\\server_name\share_name\parent\target\

There doesn't seem to be any Dynamic Naming variables that contains the server name, share name or the full location being monitored.  More specifically, the server and share name seem "invisible" to the dynamic naming variables.

So in the example above, the dynamic variables are set like:

Drive            = ""
Dir                    = "\parent\target\"
MonitoredDir      = "\parent\target\"
RelativeDir              = ""
FirstDir              = "target"
ParentDir          = "target"

Even "OriginalFull" is something like "\parent\target\myfile.txt"

Nowhere does the server or share name appear.

However %WD_DIR% and %WD_FILE% do contain the full UNC path and file name.

So I am wondering if Dynamic Naming could include a new variable that would contain either the local drive or the server name depending on what you are monitoring.  You could call it 'Volume', or 'Source' or (shudder) 'Root'.

Also have the other dynamic directory variables like "MonitoredDir" and "OriginalFull" be adjusted to contain server and share names when monitoring UNC paths.

I suggest the new variable, let's call it 'volume',  would also contain the necessary syntax for example either 'c:' or '\\server_name' so that it will work in either scenario - monitoring local or UNC paths:

Monitoring c:\monitor\parent

{volume}\{MonitoredDir} = {c:}\{monitor\parent} = c:\monitor\parent

Monitoring \\server\share\parent

{volume}\{MonitoredDir} = {\\server}\{share\parent} = \\server\share\parent

I realize that any Task is monitoring an actual server and actual share which will not change, so these values can be hardcoded in any dynamic rename within that task.  So this isn't a bug and doesn't really limit you much, but for cloning tasks or copying tasks between servers, this might be nice and would give you less customization per task.
Back to top
 
 
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2233
The Netherlands
Re: UNC paths, not a bug, probably a feature request
Reply #1 - Nov 18th, 2014 at 6:19am
 
Hello David,

You make some good points and I am not sure why those extra variables were not implemented before. We will see what can be done for the upcoming 4.8.9 release.

Gert
Back to top
 

Gert Rijs - gert (at) gdpsoftware (dot) com
Blog: http://blog-en.gdpsoftware.com/
End Alzheimer's: http://www.alz.org&&...
WWW WWW GdPSoftware  
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2233
The Netherlands
Re: UNC paths, not a bug, probably a feature request
Reply #2 - Nov 18th, 2014 at 12:33pm
 
The current {drive} variable is only set for local disks (C, D, ...). For the next release, when you monitor a network share it is set to \\server\sharename.

WD 4.8.9 will be released later this week or this weekend.
Back to top
 

Gert Rijs - gert (at) gdpsoftware (dot) com
Blog: http://blog-en.gdpsoftware.com/
End Alzheimer's: http://www.alz.org&&...
WWW WWW GdPSoftware  
IP Logged
 
Page Index Toggle Pages: 1