[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Vanilla job crashing segmentation fault due to ioctl [Sec=Unclassified]
- Date: Thu, 08 Mar 2007 20:29:59 +0100
- From: Johan Bengtsson <johan.bengtsson@xxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Vanilla job crashing segmentation fault due to ioctl [Sec=Unclassified]
On Thu, 2007-03-08 at 19:05 +0000, o c wrote:
> It is stdin that is missing (see the 0 for file
> descriptor). You get ENOTTY as the job is not
> connected to the terminal.
The matter is a little bit more complicated than that. The program in
question does not only require that stdin exists, it also requires that
stdin is connected to a terminal (or pseudo-terminal). I am not sure if
it is possible for condor to trick the program that this is the case, or
even if it is a good idea. In most cases the program usually has a good
reason for requiring that stdin is a terminal.
> Maybe post the job submit script?
> --- Dimitri Maziuk <dmaziuk@xxxxxxxxxxxxx> wrote:
> > Troy Robertson wrote:
> > > Job also runs correctly when executed directly on
> > the same Linux
> > > machine.
> > > strace shows:
> > >
> > > ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS,
> > 0xbfe20890) = -1 ENOTTY
> > > (Inappropriate ioctl for device)
> > It's hard to tell from that one line, but ENOTTY
> > often means the job
> > wants stdout/stderr and doesn't have it (it would if
> > you run it from
> > console). Adding ">/dev/null 2>&1" might fix it.
> > Dima