Hi Aleks et al,
your observation is correct. The usual way this can be handled is
through redirecting sdtout and/or stderr to a device or file that you
want the messages to go to.
If you prefer to just discard the messages, then you can do something
like calling (assuming ksh here):
su - appuser -c "command args" > /dev/null 2>&1
This would redirect both, stderr and stdout to /dev/null. We use this in
existing agents a lot, sometimes to collect some of the output either in
logfiles or to collect them and later send them to syslog.
Greets
Thorsten
Aleks Feltin wrote:
> Hi,
>
> I am running 3.2u1 with few configured GDS resources. My problem is that
> application processes, invoked from startup script open /dev/console for
> a write (checked with lsof/pfiles).
> This happens, because the script contains 'su - appuser -c "command
> args"' and the script itself is launched by cluster with superuser
> privileges. As a result, console is flooded with application messages
> and it is practically impossible to do any kind of operations.
> How is it possible to prevent application (GDS), started by cluster
> daemon to write to /dev/console? Btw, this happens with each
> application, which is registered as GDS resource.
>
> greets,
>
> Aleks F.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
