Reputation
523
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
7 19
Impact
~40k people reached

  • 0 posts edited
  • 0 helpful flags
  • 24 votes cast
Jun
9
awarded  Popular Question
Apr
29
awarded  Notable Question
Mar
20
awarded  Curious
Nov
4
awarded  Popular Question
Aug
1
awarded  Popular Question
Apr
23
awarded  Notable Question
Mar
19
accepted Can't rsync locally on synology NAS
Jan
13
awarded  Notable Question
Nov
26
awarded  Nice Question
Sep
26
asked NFS Performance: Several mounts or mount root directory?
Sep
7
awarded  Popular Question
Jun
18
awarded  Notable Question
Apr
10
awarded  Yearling
Mar
1
comment Can't rsync locally on synology NAS
Unfortunately, no dice. I'm at the most up to date firmware already (new unit).
Feb
28
asked Can't rsync locally on synology NAS
Feb
1
accepted “Cannot Allocate Memory” error when trying to ssh or ping or curl due to unrelated vpn?
Feb
1
comment “Cannot Allocate Memory” error when trying to ssh or ping or curl due to unrelated vpn?
This worked, but I needed to actually turn off these settings for my ethernet port even though I was trying to connect to these computers with my wireless connection. I found that route get name.of.server.edu showed connecting to those machines was for some reason still bound to my ethernet card (which had been using the vpn).
Jan
23
comment “Cannot Allocate Memory” error when trying to ssh or ping or curl due to unrelated vpn?
Thanks. The evanescent problem has resolved itself for now. I'll make sure to update this answer when it reappears and I apply these techniques.
Jan
22
comment “Cannot Allocate Memory” error when trying to ssh or ping or curl due to unrelated vpn?
No warnings or errors appear in any log in /var/log, nothing in Console.app, and I don't have access to the vpn log. The vpn is started with Juniper Network Connect. Not much to go on...
Jan
22
asked “Cannot Allocate Memory” error when trying to ssh or ping or curl due to unrelated vpn?