Hot answers tagged solaris
I see couple of more options from the answer here. Option 1: -o "UserKnownHostsFile /dev/null" Option 2: If you want this behavior because you're working with cloud servers (AWS EC2, Rackspace CloudServers etc.) or you're constantly provisioning new images in Vagrant you may want to update your SSH config instead of adding bash aliases or more options ...
GNU sed is bundled with releases newer than Solaris 10. Otherwise, you can easily build it from source or retrieve it from opencsw or other freeware repositories. Solaris 10 packages are listed in this pdf: http://docs.oracle.com/cd/E19253-01/pdf/817-0545.pdf
Netstat -an , netstat -rn, and lsof (before, and during the problem) may give clues. (Do they show too many open connections?). tcpdump may help too: start it just before establishing the connection and see what happens around the time connections start to die (and also a few minutes before the timeouts). And see if the NFS options are non default and ...
try to mount the filesystem you are trying to set acls on with acl options. something like this in fstab: /dev/rootvg/filesystem /filesystem ext4 defaults,acl 1 2
I believe you are making it more complex than it needs to be. No need for awk or ancient version of ps command. Try this: for x in `ps -ed -o pid=`; do echo -n "$x " ; pargs -l $x; done Or when pretty printed: for x in `ps -ed -o pid=`; do echo -n "$x " pargs -l $x 2>/dev/null # don't want to see err msg for procs that no longer exist done ...
I had a similar problem with Solaris x86 after upgrading QEMU from 1.5.3 to 2.0.0. A quick git bisect session on QEMU source repository proved this commit to be the culprit: target-i386: Set model=6 on qemu64 & qemu32 CPU models Apparently Solaris 10 doesn't like this a lot (Solaris 11 works fine). While this probably doesn't help your case a lot, ...
Only top voted, non community-wiki answers of a minimum length are eligible