Perl is making my head explode

perl isn't your immediate issue. Perl is just duct tape. What you first need to figure out is *exactly* how to get the answer you need - is checking last-modified-date the right way to do it? What if the user is syncing the other way, and the activity on the share is read-only? Do you have a record of last-accessed date at all? Log files that show when the share was last accessed? anything like that? Don't even bother figuring out what to write it in until you have the answer to that question. After that, I'd use whatever the standard scripting language is at your employer for this kind of task - that varies from company to company. FWIW, perl is *fantastic* for this kind of stuff, but that's not your immediate issue.

I'll throw in some other stuff. If you do stick with Perl, and you're running this on Windows, please pick up the Dave Roth Win32 Perl Programming book. It is very handy for these sorts of tasks. I'll throw in a hand-waving description of something I wrote in Python, recently, as sort of a curiosity satisfier — given a directory tree, how do I find unique files? First, I recursed through the whole directory tree and built a nice little data structure to house what I had. Then I placed every file in one big group in the data structure. For my first pass, I looked at filesizes — if someone had a different filesize, they went into a different group. At the end of it, I had a bunch of groups based on filesizes. Then on my next pass, I went over each group and took the md5 hash of the first 1% of the files in each, separating groups out that way even more. Then on my second pass, I did it with one of the sha variants. Third pass, 10% into md5. Fourth pass, 10% into sha. Fifth pass, 100% into md5. Sixth pass, 100% into sha. Only on the last pass did I do a binary comparison within the tiny groups left. It was ridiculous overkill, for fun, but I probably saved myself a lot of big expensive binary comparisons. Similarly, I think, I think a multipass (no, not LeLu) approach might help. Compare first on filesizes. If they're different, you don't even need to do a binary comparison. If they're the same, yeah, it might warrant further inspection. Oh, and I think there's a Windows function, buried deep, that allows you to http://msdn.microsoft.com/en-us/library/aa365261%28VS.85%29.aspx. Maybe that is what you want, if you just want to know they touched their syncho-directories. If you get stumped with some Perl network sharing stuff, let me know — I could dust off some old code.

For recursive directory walking, http://search.cpan.org/~jesse/perl-5.12.1/lib/File/Find.pm is your friend. This, for instance, gives you the most recently modified file under some given dir:use File::Find;my $max = 0; sub maxtime { my $mtime = (stat($File::Find::name))[9]; $max = $mtime if $mtime > $max; } find(\&maxtime, "/your/dir/here"); print scalar localtime $max, "\n";

I have no great love for Perl, but this task isn't impossible using it. That aside, define "synchronization." If you mean that "every file in every subdirectory here is identical to every matching file in subdirectories over there with no differences in files," that's far different from just noticing when there's a recent change. The former involves recursing through directories in lockstep and running a binary comparison between each file, as well as looking at the difference of sets between files in directories. Dates aren't perfect for this — someone intent on skirting the system could touch a file to make the date on it current.

This is definitely a task that could easily be accomplished with a shell script. I know for sure I could do it in a few lines of bash. I'm not a Windows guy, but I understand Powershell is similarly capable. A cursory Google search suggests something like: get-childitem –recurse | where-object {$_.lastwritetime etc, etc}

Well, this comes from users not synchronizing their home directory, and then complaining when something happens to their laptop and they lose data. Our company policy is that anything in your home directory is backed up, so if your laptop blows smoke we can get you back up and running as soon as possible. Over the last few months we ran into some users who had forgotten their home folders even existed. We're going through now and trying to be proactive and determine who is not even using their home directory so we can fix whatever is stopping them and/or educate them as needed. http://ask.metafilter.com/154527/Perl-is-making-my-head-explode#2215836: I agree about the perl being duct tape. You're spot on, and I think it's something that was dawning on me as I wrote up the question. It was handed to me as "This is what we want, and here is a recommendation." If I had just taken the "This is what we want," I might have skipped perl altogether. We don't have an official company scripting language. We have people from all over the place, and my supervisors have said - "Use whatever scripting language you feel comfortable with." We just happen to already have a few perl scripts we use. I wish it didn't make my head lock up. Maybe digging into my reticence to learn it will be my next step. http://ask.metafilter.com/154527/Perl-is-making-my-head-explode#2215841: We're not being that specific about it. In fact, my boss hasn't even considered people logging in and changing last-modified date on files. He just wants me to get the first part done, which is "Are they using their home directories?"

I'm finding that in Windows if I look at Last accessed, it's pointless, because as soon as I open the directory to check the last accessed...well. Yeah. Initially I was just looking at the user's directory last modified date. But what I found was that the last modified on the directory isn't always showing up correctly. You would think that if I put a new text file in my directory on 5/20, the last modified for the routergirl directory would be 5/20. But it isn't, which totally threw me off for a bit. It frustrated me, too, because it added the necessity to dig into deeper directories and check all files. Which is where my script is currently getting jammed. If it hits a subdir with space in the name or even a file with a space in the name, it appears to loop indefinitely. If anyone's interested in looking at what I have, I'd be happy to send it out. If you promise not to laugh. Or at least promise that if you do, you'll laugh to my face. I want this to be easy, but it *has* to be accurate. /taking notes on all suggestions. Thanks guys. Keep it coming.

I suspect the answer might actually be to enable auditing on the server for the User folders - and then focusing the scripting (possibly in powershell or vbscript rather than perl.... I know lots about perl but not a lot about perl on windows - as long as you can get at the event logs into something plaintext perl can work with , then perl will do fine). That should give you a pile of auditing data bout all types of access to files and folders to mine the data you want out of.......

TravellingDen's suggestion has a Perl library, Win32::EventLog, to back it up. I'm pretty sure that there's an entry in the Dave Roth book for it. So the good news is that you have at least three ways to approach the problem: 1) Auditing plus processing the Event Log 2) Recursing through files and picking out data 3) Directory change notification