I have a .bat file to perform maintenance on machines. I put the .bat file on a network attached server for all workstations to access it.
If I were to use the windows scheduler to make that .bat file run at 12:00:00.000 on say... 50 workstations, will they all be able to run it or will it error out?
P.S. don't ask me to try it =P
Suppose one is running an SSH session into a GNU/Linux box of a client and he asks you to see "what you are doing". How can you allow this other party to see what's going on in your session?
Is there any way to mount a remote CIFS/SMB/SAMBA share as a folder/directory and not as a drive letter. For example, I want this map:
\\Server\ShareName -> C:\Folder\ShareName
Instead of the usual map like this:
\\Server\ShareName -> Z:\
The server is Linux/Samba and the client is Windows 7 Professional 64-bit. The closest I've found is being able to mount a local volume as a subfolder using the Windows disk manager, but it doesn't appear to handle remote CIFS shares (see http://support.microsoft.com/kb/307889).
So we have a file share that was started 10 years or so ago and it started off with the best intentions. But now it's gotten bloated, there's files in there that nobody know who put them there, it's hard to find information, ect ect. You probably know the problem. So what I'm wondering is what do people do in this situation. Does anyone know of a decent program that can go through a file share and find files that no body has touched? Duplicate files? Any other suggestions on cleaning this mess up?
Well the file share is windows based and it's almost over 3TB. Is there a utility out there that can do some reporting for me. We like the idea of being able to find anything older then 6 months and then taking it to archive, only problem is with a file share this big that could be really hard to do by hand.
I have a Git repository on a staging server which multiple developers need to be able to pull to. git-init seems to have a flag very close to what I'm looking for: --shared, except I'd like multiple people to pull to that repository, as well. The git-clone's --shared flag does something entirely different.
What's the easiest way to change an existing repository's permissions?