Newbe Dev Stack

Answer : Putting this here for posterity ;) Background: For as long as I’ve been using Windows 2008 R2, I have not been able to change the Message Queuing configuration settings (such as storage limits, storage locations, security, etc.) or access the System Queues (Journal messages, Dead-letter messages, Transactional dead-letter messages); all attempts at doing any of these things resulted in a cryptic “Access is denied” error. Whenever I needed to install Message Queuing on a server in our environment, I used Server Manager to install the Message Queuing Feature. Solution(?): On a whim, rather than install the Message Queuing Feature, I instead choose to add the “Application Server” Role. Adding this role automatically selected and installed the Message Queuing Feature, though it only enabled the Message Queuing Server, not Directory Service Integration and Message Queuing Triggers. I am now able to re-configure Message Queuing settings, as well as access and perform acti...

Answer : Solution 1: If you've got access to the mysql database, you can change the grant tables directly: UPDATE mysql.user SET Host='%' WHERE Host='localhost' AND User='username'; ...and an analogous UPDATE -statement to change it back. Also you might need to make changes to the mysql.db table as well: UPDATE mysql.db SET Host='%' WHERE Host='localhost' AND User='username'; and then flush to apply the privileges: FLUSH PRIVILEGES; Solution 2: Best answer on Stackoverflow suggesting to use RENAME USER which copy the user privileges. Using Data Control Language (statements as GRANT, REVOKE, RENAME and so on) does not require FLUSH PRIVILEGES; and is required in architecture like Galera or Group Replication in MySQL versions having MyISAM tables in mysql database because MyISAM tables are not replicated. Solution 3: I stumbled across this one, too, and the proposed solution didn't work, since the datab...

Answer : if anyone pass through here, this is shorter solution: sudo chown -R $USER $HOME/.composer it seems to me the group information is missing in your command sudo chown -R <user> /home/<user>/.composer/cache/repo/https---packagist.org Shoud be sudo chown -R <user>:<group> /home/<user>/.composer/cache/repo/https---packagist.org But to avoid other permission issues, I would rather advise: sudo chown -R <user>:<group> /home/<user>/.composer/cache (you'll need access to other folders in there) and sudo chown <user>:<group> /home/<user>/.composer To make sure your user has permissions enough on the global composer folder. Mind the missing recursion so the user don't own keys created by root. If you need to find out the group: groups <user>

Answer : Disclaimer: The Update Orchestrator Service is tied to Windows Update. Changing the registry may cause problems with Windows Update and associated services. So if you don't know what the registry does I recommend not to mangle with registry and services. All Windows services have some security to control their permissions and user interactions. Security is managed through HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SERVICE_NAME\Security and RequiredPrivileges registry. If there are some permissions denied in Service Manager (aka. services.msc ) then Startup Type can be changed using the registry. Use the following command to change startup type of that ``UsoSvc` service. set X=UsoSvc reg add "HKLM\SYSTEM\CurrentControlSet\Services\%X%" /V "Start" /T REG_DWORD /D "4" /F What does the command do? reg add command adds (or changes) the Start DWORD registry in HKLM\SYSTEM\CurrentControlSet\Services\UsoSvc registry path. The ...

Answer : On most distribution adduser and addgroup are interactive 'convenience' wrappers around the commands useradd and groupadd . You can find addgroup using the command which addgroup , on my machine (Ubuntu 11.04) this lives in /usr/sbin/addgroup . On my box addgroup is a perl script that prompts for various options (interactively) before invoking the groupadd command. groupadd is usually preferable for scripting (say, if you wan't to create users in batch), whereas addgroup is more user friendly (especially if you are unfamiliar with all the options and flags). Of course addgroup also takes many options via the command when you invoke it, but it is primarily intended as an interactive script. Interestingly on my box addgroup is a symlink to adduser , the script checks the name it was invoked under and performs different actions accordingly. groupadd is more preferable for better cross-linux and sometimes cross-unix systems compatibility. addg...

Answer : If you are going for a console command it would be: chmod -R 777 /www/store . The -R (or --recursive ) options make it recursive. Or if you want to make all the files in the current directory have all permissions type: chmod -R 777 ./ If you need more info about chmod command see: File permission If by all permissions you mean 777 Navigate to folder and chmod -R 777 . You can give permission to folder and all its contents using option -R i.e Recursive permissions. But I would suggest not to give 777 permission to all folder and it's all contents. You should give specific permission to each sub-folder in www directory folders. Ideally, give 755 permission for security reasons to the web folder. sudo chmod -R 755 /www/store Each number has meaning in permission. Do not give full permission. N Description ls binary 0 No permissions at all --- 000 1 Only execute --x 001 2 Only write ...

Answer : Open /opt/lampp/etc/httpd.conf change nobody and nogroup <IfModule unixd_module> # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User nobody Group nogroup </IfModule> to your username and your group Had the same issue and here is what i did: Run this command to stop xampp: sudo /opt/lampp/lampp stop Open /opt/lampp/etc/httpd.conf Change your_folder to the folder you wanna use DocumentRoot "/home/username/your_folder" <Directory "/home/username/your_folder"> Change User & Group value from daemon to: User nobody Group nogroup set chmod to your_folder with this command sudo chmod 777 /home/username/your_folder Save the file and start xampp wi...