Hot answers tagged


Why can't the OpenSSH configure script detect OpenSSL explains the possible cause that might have occured in your case. Several reasons for problems with the automatic detection exist. OpenSSH requires at least version 0.9.5a of the OpenSSL libraries. Sometimes the distribution has installed an older version in the system locations that is detected ...


I got my system updated by downloading 4.3 bash source code and patches from and compiling it to replace the existing code. It works, now waiting for more patches.


OK, found it. That now makes sense. the behaviour is Nexenta-specific and explained at GNU and not GNU The default behavior of Nexenta is to prefer GNU utilities, which are installed in /usr/bin and /usr/sbin and so on. The Sun versions of these utilities are installed in /usr/sun/bin and /usr/sun/sbin. Nexenta uses ...


In any case, sed "0,/^local/{s/md5/trust/}" Is GNU specific (the 0 address and the missing ; before }) and won't work with any other sed implementation (and Solaris doesn't ship with GNU sed by default). Portably/standardly: sed '/^local/,$!s/md5/trust/' to replace only on the lines up to (but not included) the first one starting with local. Or: awk ...


No, there is no way to watch it, directly via ZFS send or receive. Solaris 11.2 does have some verbosity available in zfs send that would allow you to gauge process. If you have access to the script, you could pipe the zfs send through 'pv' to watch progress, if that would be helpful enough.


I suspect you are using NFSv3 which underlying protocol limits to 16 the number of groups a user can belong to. See that blog for an explanation.

Only top voted, non community-wiki answers of a minimum length are eligible