On Thu, Jul 21, 2011 at 06:06:38PM +0200, Lennart Poettering wrote:
> > still exist -- we just got go-ahead for a rather expensive one). There,
> > the network connectivity is pretty much a given and if the network
> > properties change it's either a big problem or else something we've
> > planned
On Thu, 21.07.11 11:28, Matthew Miller ([email protected]) wrote:
>
> On Wed, Jul 20, 2011 at 08:46:00PM +0200, Lennart Poettering wrote:
> > However, I don't think something like you suggest is feasible. In a
> > modern environment network connectivity is dynamic: it comes and goes
> > and comes
On Thu, Jul 21, 2011 at 09:30:27AM +, "Jóhann B. Guðmundsson" wrote:
> This sounds backwards to me why arent you doing the updates before shutdown
> instead so for example you would boot into a new kernel.
The pathological case is a system which has been shut off for the summer.
When it comes
On Wed, Jul 20, 2011 at 08:46:00PM +0200, Lennart Poettering wrote:
> However, I don't think something like you suggest is feasible. In a
> modern environment network connectivity is dynamic: it comes and goes
> and comes and goes, and its's properties change. A robust system should
That's definit
On 21/07/11 10:30, "Jóhann B. Guðmundsson" wrote:
On 07/20/2011 06:11 PM, Matthew Miller wrote:
In general, it's useful to have an on-boot update service make sure any
updates are applied before any daemons which might be updated are
started.
This sounds backwards to me why arent you doing the
On 07/20/2011 06:11 PM, Matthew Miller wrote:
In general, it's useful to have an on-boot update service make sure any
updates are applied before any daemons which might be updated are started.
This sounds backwards to me why arent you doing the updates before
shutdown instead so for example yo
On 20.07.2011 20:46, Lennart Poettering wrote:
> On Wed, 20.07.11 14:11, Matthew Miller ([email protected]) wrote:
>
>> In general, it's useful to have an on-boot update service make sure any
>> updates are applied before any daemons which might be updated are
>> started.
>
> If so it is possible
On Wed, 20.07.11 14:11, Matthew Miller ([email protected]) wrote:
> In general, it's useful to have an on-boot update service make sure any
> updates are applied before any daemons which might be updated are
> started.
If so it is possible to stick it between early boot and late
boot. Use "After=
On Wed, Jul 20, 2011 at 08:02:38PM +0200, Lennart Poettering wrote:
> In systemd we spawn services in parallel, and boot-up completes as soon
> as all services (including yours) have been started. That means that by
> definition the boot will finish only after your stuff was started.
>
> Now, what
On Wed, 20.07.11 18:49, Frank Murphy ([email protected]) wrote:
> I want yum-updateonboot to complete, before booting continues.
> Currently it is trying to login before completion.
In systemd we spawn services in parallel, and boot-up completes as soon
as all services (including yours) have be
On 20/07/11 18:45, Lennart Poettering wrote:
You can make any process you like a systemd service.
Example:
/etc/systemd/system/systemd-user-sessions.service
[Unit]
Description=Permit User Sessions
After=local-fs.target remote-fs.target yum-updateonboot.service
even with this, boot still con
On Wed, 20.07.11 09:45, Frank Murphy ([email protected]) wrote:
> I'm not a dev.
>
> Previously posted to:
> http://lists.baseurl.org/pipermail/yum/2011-July/023700.html
> This may be a more correct list?
>
>
> Using yum-updateonboot with systemd on Fedora 15\16(Rawhide).
>
> As yum-updateon
I'm not a dev.
Previously posted to:
http://lists.baseurl.org/pipermail/yum/2011-July/023700.html
This may be a more correct list?
Using yum-updateonboot with systemd on Fedora 15\16(Rawhide).
As yum-updateonboot is a service, (chkconfig)
it calls both yum and creatrepo (with yum-plugin-local)
13 matches
Mail list logo
