Page MenuHomeFreeBSD

mail: Don't trap signals we shouldn't.
ClosedPublic

Authored by des on Apr 24 2025, 10:03 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, May 21, 11:13 AM
Unknown Object (File)
Tue, May 20, 9:57 PM
Unknown Object (File)
Fri, May 16, 11:31 AM
Unknown Object (File)
Sun, May 11, 2:22 PM
Unknown Object (File)
Wed, May 7, 7:07 AM
Unknown Object (File)
Tue, May 6, 1:27 PM
Unknown Object (File)
May 5 2025, 9:54 AM
Unknown Object (File)
Apr 28 2025, 11:33 PM
Subscribers

Details

Summary

When in interactive mode, trap SIGINT, SIGHUP, and tty-related signals.
Otherwise, leave signals untouched as required by POSIX.

MFC after: 1 week
Sponsored by: Klara, Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

des requested review of this revision.Apr 24 2025, 10:03 PM
kevans added inline comments.
usr.bin/mail/collect.c
82–85

Looking at the standard, it's not clear to me that this is actually correct. ASYNCHRONOUS EVENTS explciitly spells out ignore handling only in the interactive case as something evaluated when a SIGINT rolls in, and otherwise has:

When mailx is in Send Mode and standard input is not a terminal, it shall take the standard action for all signals.

I think we should continue to leave SIGINT alone in the non-interactive case.

This revision is now accepted and ready to land.Apr 25 2025, 1:56 PM
This revision was automatically updated to reflect the committed changes.