Hot answers tagged permissions
2
An easier and less confusing way to trap cmdlet specific errors to a file is by using the -Errorvariable parameter. It is built into most cmdlets. It is not reliable to look at the $Error variable as it is a global variable and has a high chance of being stained by other unmitigated errors in the powershell process.
The code below will log the errors in 2 ...
1
You can also start rsync using sudo on the remote machine to run it with root privileges. The option you can use for this is --rsync-path:
rsync -avL --progress -e "ssh -i /home/me/myhosts.pem" --rsync-path="sudo rsync" source-folder ubuntu@ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com:/var/www/
1
What is you rsync version on client and server? run
rsync --version
It should be the same on both client and server side.
Try increasing log verbosity on SSH Server (Loglevel debug in sshd_config and /etc/init.d/ssh restart) and assure the connection is not related to a single user (User clause should be empty or contain root if you want to log in ...
1
I've seen this issue manifest itself in a few different ways. It almost always goes back to either old printer drivers or specialized drivers that do not fully support UAC.
A couple of general things to check:
Are you using a Print Server? If so, make sure the driver-specific options are enabled in the Printer Preferences for the print queue on the print ...
1
There are a lot of different ways to do this. Here is something I just cooked up.
$Error.Clear() # This is a global variable!
$Errors = @()
$Items = Get-ChildItem C:\ -Recurse -ErrorAction SilentlyContinue
ForEach($Err In $Error)
{
$Errors += $Err.Exception
}
ForEach($Item In $Items)
{
Try
{
$Item | Get-ACL -ErrorAction ...
Only top voted, non community-wiki answers of a minimum length are eligible
