Hot answers tagged share
Permissions are a pest. Basically, you need to make sure that all of those developers can write to everything in the git repo. Skip down to The New-Wave Solution for the superior method of granting a group of developers write capability. The Standard Solution If you put all the developers in a specially-created group, you can, in principle, just do: ...
This has not been said, so I want to quickly add it. To ensure that permissions issues do not crop their ugly head, make sure to set the following on your git shared repository's config file: [core] sharedRepository = true This will ensure that your system's "umask" settings are respected.
Just to map a network share directory you would use this command: net use \\Server\ShareName\Directory This mapping would not be persistent and would have to be established and authenticated at user login, and you would access the share using the UNC path and not a local drive letter. If you want to access the network share through a location on your ...
We counsel Customers to "scorch the earth" and start fresh, oftentimes. I have yet to see a good solution that works that doesn't involve have non-IT stakeholders involved. The best scenario I've seen yet is a Customer that has had management identify "stewards" of various data areas and delegated control of the AD groups that control access to those shared ...
You really would be better off setting up a pair of nameservers if you can. I've never really seen a situation where you couldn't replace a cumbersome hosts file situation with a couple of DNS servers (Really, they are easy to setup and run). However, to answer your question, you can use something like either puppet or cfengine to keep these in sync. ...
Dominic D's explanation of what is going on is correct: Vista, Windows7, and Windows2008 r2 use NTLMv2 by default. Older implementations of Samba don't support this and will return a password failure. Fortunately you can tell Vista and Windows 7 (and I presume Server 2k8) to use the v1 protocol if the v2 is not available. These are my notes for Vista, they ...
The Git User Manual describes how to share a repository in several ways. Exporting via the Git Daemon. Exporting via HTTP. CVS/SVN style, a single shared repository where developers push/pull. More complicated, though feature-full ways to share repositories are: Gitosis GitHub (or GitHub Firewall Install) We use GitHub for a team of 6 developers.
You could try using the "screen" command. This will allow you to run a multiuser session which 2 users can connect and share. First you'll need to set the suid bit. screen comes with it turned off, and it is necessary for multiuser mode: sudo chmod +s /usr/bin/screen sudo chmod 755 /var/run/screen The first user connect, running screen -S shared The ...
Windows7 and Windows2008 r2 use NTLMv2 by default. Older implementations of Samba don't support this and will return a password failure. We had this exact same problem on our NAS. Two solutions Bug your NAS vendor to update their implementation (we've just received a patch). Push a policy change either via GPO or via Local Policy. The setting you ...
This should work so long as the account you run the scheduled task using has correct access to the network share where the bat file is located. Depending on what the script does, I'd stagger the run times by department. You only need a minute or two of variance to minimize the odds of a staggering hit right at 12. Regarding the commenter above who mentions ...
When you added yourself to the group, did you log out of your workstation and log back in? Security Group membership is a component of the access token granted to your user ID at logon and changing group membership requires a log out and log in order to get a new access token that reflects the new membership.
Also look at gitolite for hosting your git repository. Gitosis apparently isn't being developed anymore.
quoting and answering your questions: > "...I want it's localhost to be available from other computers" Sorry, but "localhost" (meaning "this computer") is the standard hostname given to the address of the loopback network interface. The name is also a reserved domain name, so you can't make computer's localhost to be avalible from other computers. > ...
You may be able to clear the cached credentials by using the Credential Manager in the Control Panel. Try browse into the Control Panel, enter "Credential Manager" into the search bar on the top right, then click on the "Credential Manager" result. You may find your cached credentials under the "Windows Credentials" section, if so you can click "Remove from ...
Sounds like tokens aren't being issued at logon. Are you sure that there isn't a connectivity or AD issue with that machine? I suspect you're logging in with cached credentials and aren't actually authenticating against a DC from that one machine. klist.exe will show you if you have any Kerberos tickets. You should disconnect any manually mapped drives, ...
The ldconfig command will show these paths for you... ldconfig -v | grep -v ^$'\t' The paths are set in /etc/ld.so.conf and /etc/ld.so.conf.d.
This is entirely possible with NTFS rights, but it is far from a standard configuration. We had to do something similar, create drop-boxes: directories where students could copy in files, but couldn't delete them once there, or see any other directories. Doable with some custom work. The key is understanding how different rights behave when set on files and ...
Shares are listed in SYSTEM\CurrentControlSet\Services\LanmanServer\Shares registry key, you can delete the entries there, after a backup of the key (source)
Github is commonly used for this sort of thing as is bitbucket.
This can be done by modifying the advanced security permissions of the folder and make sure that the users do not have the "Delete Subfolders and Files" and "Delete" permissions. The following rights should work: Traverse Folder/Execute File List Folder/Read Data Read Attributes Read Extended Attributes Create Files/Write Data Create Folders/Append Data ...
I agree with Evan that starting over is a good idea. I've done 4 "file migrations" over the years at my current company, and each time we set up a new structure and copied (some) files over, backed up the old shared files and took them offline. One thing we did on our last migration might work for you. We had a somewhat similar situation with what we ...
If you're sharing your system disk then all sensitive system information will be shared. If you provide write access, things could get even worse! Remote users will be able to get to the registry and at least check it's contents for possible passwords, keys and other "secret" information. If you give them write access, your whole system might be formatted by ...
Try DFS. Here's an article I found that goes into detail.
Please reference the MS KB regarding this issues: http://support.microsoft.com/kb/870964 Basically: Make the Server service dependent on the iSCSI Initiator service. For information about how to do this, see the "Make the Server service dependent on the iSCSI Initiator service" section
The problem you have is that to get duplexing and other features, you need to use the native features of the print driver. Things like ghostscript will get you the basic printing features, but to get more advanced features, you really need a proper driver for the printer.
Your procedure as indicated above should work
I'd recommend plugging it into the network with the network socket, allocating it a fixed IP, then creating a print queue on the server that points to the printer. Clients can then connect to the queue on the server (via a nice friendly network name), and they'll have the correct drivers served automatically (assuming this is a windows server). You'll be ...
Only top voted, non community-wiki answers of a minimum length are eligible