On 14 Nov., 19:44, Hajo Ehlers <serv...@metamodul.com> wrote:
> On Nov 13, 11:05 am, bine <sabine.hubrig-schaumb...@sungard.de> wrote:
>
>
>
>
>
> > 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
>
> 1 )Provide a stripped down version of your scripts which does
> reproduce the problem
> 2) AFAIK is csh depreciated for shell programming. Go at least for the
> tcsh and see if you have the same problem.
> 3) You are really sure that no process is writing with > to your
> output file ?
> 4) I believe i have seen some problems with csh and pipes and grep
> where the buffer was not flushed if the data was not getting larger
> then 4k meaning the script output never left the buffer.
>
> hth
> Hajo- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -

thanks to you guys, I will have a look into all those ideas ...
just some quick answers to some of your questions:

- AIX is not avoidable (due to our customers requests) as much as I'd
like ;-(

- I'm not the administrator so I can't try everything, but
unfortunately there's no other expert than me ;-) [or to more precise
";-(" ]

- mylog is not on NFS

- the csh starting the process using >>& is running "long" that is
normally some hours as it's kind of a demon to serve requests when
they are entered in the databasetables (and start script to do so,
which fail to put their (short) messages into the same mylog

- using tcsh would mean to change a lot of scripts which now start
with #!/bin/csh (because I couldn't rely on csh being linked to tcsh
on all [customer's] machines...) but of course it would be worth a try
for testing the effect only with my environment to eliminate that idea

- I'm sure that no process does >mylog because the start-messages of
the process the csh starts and others of that ARE in the file, only
those of other processes writing >>mylog fail to do so, so there's no
"over"writing of mylog but just a "non"writing to mylog

- hajo's 4th point is my favourite, that is: a buffer of 4K which
never gets

thank you guys so far
and if I detect something I'll post it