[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #ORI-704946]: setpgid not working under linux in pipe_open

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #ORI-704946]: setpgid not working under linux in pipe_open
  • Date: Thu, 04 Sep 2008 14:01:27 -0600
Harry,

> P.S.  I checked this on Solaris 10.  It does the same thing.  I'm
> wondering if this is a requirement of POSIX, or if it is a case of great
> minds thinking alike.

I think the code that handles signal blocking is executed before teh
code that determines if the signal's being ignored, which is
executed in the kernel on behalf of the relevant process.

The only thing I don't like about having the LDM ignore SIGCONT is
that this would mean that EXECed programs would be in a non-standard
execution environment.  If such a program received a SIGSTOP, for
whatever reason, it would never be able to restart and would have
to be abnormally terminated.

If the problem is primarily with the dcgrib2(1) decoder, then it
might suffice to make decoders their own process-group leaders.
This can easily be done by replacing the "setpgid(0, getppid())"
with a "setpgid(0, 0)".

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ORI-704946
Department: Support LDM
Priority: Normal
Status: Closed