Bug 168233 - Option for a 'background' push
Summary: Option for a 'background' push
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora Infrastructure
Classification: Retired
Component: update system
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Luke Macken
QA Contact: Bill Nottingham
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-13 18:31 UTC by Bill Nottingham
Modified: 2016-09-20 02:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-12-08 03:25:35 UTC
Embargoed:


Attachments (Terms of Use)

Description Bill Nottingham 2005-09-13 18:31:29 UTC
As I understand it, for a push to succeed, the connection has to be open for the
entirety of the metadata generation, push, mail sending, etc.

Could there possibly be an option for a fire-and-forget background push that
sends mail when it succeeds (or if it doesn't)?

Comment 1 Luke Macken 2005-11-10 18:49:36 UTC
Bill, when you get a chance can you verify that closing your web browser kills
all pushing processes on porkchop ? 

I remember doing this a few times before, and the currently running process
wasn't killed when I closed my browser.. but I'm not sure if it will keep
executing the rest of the push script.

Comment 2 Bill Nottingham 2005-11-14 18:10:25 UTC
I've just verified; if i close the open tab, the currently running createrepo
processes finish, but the rest of the push process (push to wallace, close bugs,
etc.) doesn't happen.

Comment 3 Luke Macken 2005-12-08 03:25:35 UTC
With the createrepo cache speedup, this shouldn't be necessary (yet)


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