Is AIX locking files used to redirect stdout+err to in shellscripts and prevents them to be written to by other processes explicitly? I have the confusing fact that in contrary to Linux (UnitedLinux or
SuseEnterpriseServer)
I miss some informations I write to a file.
It seems that defining this file to be used for stdout+stderr in a csh-
call like in
myprog ... >>& mylog
prevents later in the callhirarchy,
that is by things called from myprog,
and other scripts running in parallel as well
(because this csh is running with nohup parallel to those)
to put their output explicitly, e.g. by
echo ... >> mylog
into the same file.
Is there some parameter or "set" command to make AIX behave like the
others?
I know that if those messages REALLY come in parallel, there MUST be
some conflict
due to the serialization of the output, so I might get things in a
"wrong" order
(I really don't want to discuss if this application is very
sophisticated
or should be modernized/recoded to a certain extent ;-),
but I miss EVERYTHING of the other processes, not only some of the
letters,
so the question occurs if it's a configurable behavior of AIX?
The highest level of any bos.*-module of the machine in lslpp-output
is 5.3.0.61,
but I think the behaviour hasn't changed and was the same (and always
frustrating) in former releases?
Thanks in advance
bine |