Tag Info

New answers tagged

0

The straight out way of doing this is: Create a new temp account with sudo rights: sudo adduser temp sudo adduser temp sudo Log out from your current account and back in with the temp account. Rename your username and directory: sudo usermod -l new-username -m -d /home/new-username old-username Rename your username default's group: sudo ...


-1

This is for Windows 8, not sure will this help. Just have a look and inform me the result.


-1

Is there a way to find out who was logged on a Windows server in a past year? Yes, by checking the logs. Security log is only 1 month old or less and user profiles were deleted. Well, you're out of luck. You can find out who's logged in in the past month, though.


1

If you're not hard-set on just one user, you might consider the following setup: Each user has their own UID. umask for all bzr users is 002. Each repository has an owner UID and a unique write-permissions group. Each repository has a directory based within the owner UID's tree. Each repository directory is sgid (chmod g+s <repo>). Each repository ...


2

Actually puppet has a very easy to implement local config for small environments and is one of the best tools for this. This page has info on a very very quick and easy setup. http://projects.puppetlabs.com/projects/1/wiki/simplest_puppet_install_pattern


0

Disclaimer - much opinion herein. With that out of the way, my first question would be, "How big will this application become?" If the answer is >10 servers, I'd suggest biting the bullet and going the Puppet/Chef/Ansible route. If <10 servers, just reproduce manually looking at package manifests, and taking notes as you build your second server.



Top 50 recent answers are included