303603 – Using emerge in a cron job causes warning messages.

Bug 303603 - Using emerge in a cron job causes warning messages.

Summary: Using emerge in a cron job causes warning messages.

Status:	RESOLVED DUPLICATE of bug 285341

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-02-05 18:01 UTC by Navid Zamani
Modified:	2010-02-05 18:21 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Navid Zamani 2010-02-05 18:01:03 UTC

I run eix-sync and “emerge -puDNtv world” in a weekly cron job.
My eix-sync.conf also contains a call to “emerge -q --sync”.
in both cases, I get a lot of the following messages:

“sandbox:main  signal SIGQUIT already had a handler ...

”

I think that the cron process somehow already defines a handler.

It would be better, if emerge would be able to handle this case anyway.

Reproducible: Always

Steps to Reproduce:

Comment 1 Paul Varner (RETIRED) gentoo-dev

2010-02-05 18:21:21 UTC

Even though the bug I'm duplicating this to references revdep-rebuild, it is the same issue.

*** This bug has been marked as a duplicate of bug 285341 ***