From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 279DB1F463 for ; Tue, 31 Dec 2019 16:54:16 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=uhZKG dute3pem6HhXTwdptOxnrPH62FvE+49fAdr3GLoPOx/WSXVIwgXoJIfupGh40xmK i0dbp/csodc2bsJJWzSUdH02oulFCsoEsrQZbefcvq/eg4urNMZlBHCNTKvyOc/2 A0h5COutT0GdpnMkITQoKf3PzmvO3JhYcSCrKk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=J7s8UuU2jyk 8DGIEuwY4NO62sjo=; b=hJj5LoMbncVcN3RaDgHjSp34fGUCPXXgO8nlVQCVkhe /SJrPi+FWWDLguCB5oUQir15ayZEO9CZj2iyvpGtBpJxUbzbFyAAzT7ESd/7DZZM CzdeYivxgLjgfRw1PBjKruG2/dz45aG7LcRCMIhpdQKtvofMbhEXL6mvPegYTfvY = Received: (qmail 8665 invoked by alias); 31 Dec 2019 16:54:08 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 8615 invoked by uid 89); 31 Dec 2019 16:54:08 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: albireo.enyo.de From: Florian Weimer To: Samuel Thibault Cc: libc-alpha@sourceware.org Subject: Re: posix_openpt vs getpt?? References: <20191230213550.icqt2er7dwnxcrrb@function> <87a778mxta.fsf@mid.deneb.enyo.de> <20191231163803.rbcctlhvyhwdrxqv@function> <20191231164525.ps7mpnh3p4huxlu3@function> Date: Tue, 31 Dec 2019 17:53:16 +0100 In-Reply-To: <20191231164525.ps7mpnh3p4huxlu3@function> (Samuel Thibault's message of "Tue, 31 Dec 2019 17:45:25 +0100") Message-ID: <87lfqsl9mr.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain * Samuel Thibault: > One thing I'm unsure of: the Linux manpage says > > It is equivalent to > > open("/dev/ptmx", O_RDWR | O_NOCTTY); > > But the Linux implementation is > > int fd = __posix_openpt (O_RDWR); > > > Is getpt supposed to set the controlling tty or not? Since the Linux > behavior has been not to set O_NOCTTY since its introduction in 1998, I > guess applications assumes !O_NOCTTY and it's the manpage which needs to > be fixed? I'm not sure if O_NOCTTY actually has an impact here. Does /dev/ptmx actually qualify as a terminal device? In any case, I agree that the manual page should be fixed. Would you submit a patch, please?