On Thu, 13 Sep 2012, Alain Reguera Delgado wrote: >> echo "$MESSAGE"> /dev/stderr > Yes. These are error messages. Where else does they should go to but the > standard error output? Isn't it the usual way of printing error messages? no: echo "$MESSAGE" 1>&2 is the usual way, so that it follows the stderr file handle assigned to that sub-shell, rather than (as here in your approach) trying to write directly to a device to which it does not have rights > For some reason are you running the whole script through `sudo'? no -- I 'su -' 'd down to an end user account from root to run the script. No console login on that box > message telling you that, so you can fix the problem. If we don't do > such printing finding errors would be even harder, don't you think? I am not against error logging, but the unusual way it is attempted, in view of the Unix and CentOS rights model as to selected devices -- Russ herrold _______________________________________________ CentOS-docs mailing list CentOS-docs@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-docs
