Tag Info

New answers tagged

0

If you want to perm a route in 10.10 Yosemite. here You should create a quick script with "#!/bin/bash" sudo /sbin/route add -net x.x.x.0/24 xxx.xxx.xxx.xxx save it in a path chmod a+x the file Then type this,.. sudo defaults write com.apple.loginwindow LoginHook /Path/To/Your/Script POW .. Yosemite perm route with edit file .


0

I ran into a similar problem after updating to Yosemite 10.10.1 Could you please check the output of tcpdump in another Terminal window, while you are connecting to your remote ssh server? I have the suspicion you're hitting the same redirect-error I am seeing on my box recently :-/ How to get the information: Open Terminal type "sudo tcpdump -vv" --> ...


1

opentracker.net is a service provider that offers analytics. My guess is that your redirection happens when you are connected to a network provider that internally uses opentracker.net. I suggest you try again from another network provider.


2

When you want to connect to an unroutable address like link-local you need to specify the interface. This is because for unroutable addresses your system can't determine the outgoing interface by looking at the routing table. Unroutable destinations include link-local addresses (fe80::) and link-local multicast (ff02::) and more.


0

You can also schedule your system to reboot at certain times of the day using options within System Preferences, or by use of a bash script that will handle this when the symptoms you described above are detected. When you notice this happening, have your monitors also gone into standby mode r shutdown from inactivity?


1

You will need to use a program called PuttyGen.exe on the Windows side to generate a public and private key. Using the "Generate" button, generate the keys using the above program. You will then need to move the public key that is generated to your mac. Save a copy of the private key to use later using the "Save private key" button. On your windows ...


0

Check for local keep alive settings on your mac. These were mine...: sysctl -a | grep tcp.keep net.inet.tcp.keepidle: 3600 net.inet.tcp.keepintvl: 150 net.inet.tcp.keepinit: 75000 net.inet.tcp.keepcnt: 8 I needed to change the keepintvl setting to some higher value: sudo sysctl -w net.inet.tcp.keepintvl=7500 Then the ssh "write failed: Broken pipe" ...


0

Did you try to add your variable to your .bash_profile: export MYVAR="Whatever" $ . .bash_profile $ echo $MYVAR Whatever $ ssh localhost Password: Last login: Tue Nov 18 18:58:41 2014 from localhost $ echo $MYVAR Whatever $


0

the password for your key is managed by ssh-agent and it defaults to ask for your password using the GUI you mentioned. You could: Unlock your key using the shell frontend to ssh-agent by calling ssh-add. In this case you might want to lock your key with ssh-add -D before you log out of the box. Circumvent ssh-agent by temporarily unsetting the ...


0

I've got the same situation: a server with log files and my local machine I want to be notified on on errors and warnings. What I do is to fetch the log files periodically to my local machine and watch them with a tool called Logistic (www.logtastic.net). The command fetching my log files from the server is: while true ; do FONTDEFDEFAULT='\033[0m' ; ...


0

Terminal only defaqltly supports 16 colors. I would recommend using a different terminal client, like iTerm2. Another way to to use this program to make terminal show all colors. [In iTerm 2] The recommended way is to set your terminal type to xterm-256color in Preferences->Profiles->Terminal->Report Terminal Type. You may also need to put set ...


0

I'm pretty sure I understand what you are trying to accomplish, but saying "I want to forward a computer to port 22" does not make any sense. You are trying to forward incoming packets addressed for port 22 from your router to your Mac, is what you mean to say (I am assuming). In any event, port forwarding is done in your router's settings, not your Mac's. ...


0

Order of execution is based on PATH order - locations put first are searched first, if match is found it is executed, HOWEVER, programs mapping are cached so you need to refresh the cache before changes will take place (if you've used that app before). See http://www.thegeekstuff.com/2010/08/bash-shell-builtin-commands/ (point 3.): hash command maintains ...


1

Transmit by Panic - http://panic.com/transmit/ Configure as an SFTP server, click the Key icon. I'm not sure of the specific implementation (SFTP vs SCP), but testing onto another standard OS X host with SSH keys setup works fine. The other box isn't running a special SFTP setup - appears to work fine. Transmit is a great OS X app for any sort of file ...


0

config.vm.boot_timeout - The time in seconds that Vagrant will wait for the machine to boot and be accessible. By default this is 300 seconds. (got this from) ServerFaqs I'd increase this until you are able to vagrant ssh in.


-1

I had the same problem. I deleted everything from SystemPrefereces->Security->Firewall and removed all services from SystemPreferences->Shared. Then I enabled remote login again. That fixed the problem in my case.


1

You need to create a "bare" git repo: a repository that can never have files checked out. Everyone pulls and pushes from the server like normal, but nobody can actually work on the server (unless they make a non-bare clone). If you are creating a new repository called "my_bare_repo.git", you can make it bare like so: cd /Users/git (or whatever) git init ...


1

sudo systemsetup -setremotelogin on sudo systemsetup -setremotelogin off



Top 50 recent answers are included