Hello,
I'm Norman Chan, Tak-Lam, S.B.S., J.P, Chief Executive, Hong Kong
Monetary Authority (HKMA). I have a Business worth $47.1M USD for you to
handle with me. Contact me on my email (chan_norman2...@qq.com) for more
details of the business,
La informacion contenida en este e-mail y sus anexos
Erwan David wrote:
> This I did not know, not finding migration documentation for sysvinit
users.
Erwan, googling for debian systemd led me to this migration guide:
https://wiki.debian.org/systemd
It also includes instructions on how to make boot messages visible (the
Debugging section).
K
Hi,
(as this thread has already attracted two "interesting replies", I'll try
again to convey the message which has not been heard yet... I don't have high
hopes this thread won't become a flamefest, but I want to at least try to kill
the flames before they explode...)
(And if you know systemd
Hi,
> Ralf Jung writes:
>> $ sudo hwclock -r ; date
>>
>>
>> Tue 22 Jul 2014 20:13:22 CEST -0.235161 secon
Hi Ralf,
Ralf Jung writes:
> $ sudo hwclock -r ; date
>
>
> Tue 22 Jul 2014 20:13:22 CEST -0.235161 second
Processing commands for cont...@bugs.debian.org:
> severity 746358 important
Bug #746358 [systemd] systemd: system boot hangs if /etc/fstab contains an NFS
mount
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
746358: ht
Hi Gerrit,
Gerrit Pape writes:
>> There is a reason, why we added the logic in a single place.
>
> With sysvinit I have the logic easily implemented in the maintainer
> scripts. With runit it's even more simple. I really don't want to
> depend on some complex logic and an additional package jus
Package: systemd-sysv
Version: 208-6
Severity: normal
When booting I get fiollowing logs :
1)
from journalctl :
Jul 21 09:04:49 nux28622 systemd[1]: Activating swap /dev/sda4...
Jul 21 09:04:49 nux28622 systemd[1]: Activating swap
/dev/disk/by-uuid/4d15936d-9e4f-4556-b141-98c32fdc9799...
Jul 2
This message contains a digitally signed email which can be read by opening
the attachment.
--
teamix GmbH
Südwestpark 43
90449 Nürnberg
fon: +49 911 30999 0
fax: +49 911 30999 99
mail: i...@teamix.de
web: http://www.teamix.de
blog: http://blog.teamix.de
Amtsgericht Nürnberg, HRB 18320
On Tue, Jul 22, 2014 at 03:03:02PM +0200, Michael Biebl wrote:
> Am 22.07.2014 14:34, schrieb Gerrit Pape:
> > Hi, I've now prepared this changeset. Do you have any comments on it?
> > diff --git a/debian/daemontools-run.postinst
> > b/debian/daemontools-run.postinst
> > index d51ac09..1d7aae1 1
Package: cups-daemon
Version: 1.7.4-1
Severity: normal
File: /lib/systemd/system/cups.path
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: systemd-units
Please hook up the cups.path in paths.target instead of
multi-user.target.
See man systemd.special
paths.target
Am 22.07.2014 14:34, schrieb Gerrit Pape:
> On Fri, Jul 18, 2014 at 12:03:41PM +, Gerrit Pape wrote:
> --- /dev/null
> +++ b/debian/systemd/daemontools.path
> @@ -0,0 +1,9 @@
> +[Unit]
> +Description=Daemontools service monitor
> +
> +[Path]
> +DirectoryNotEmpty=/etc/service/
> +Unit=daemontoo
Am 22.07.2014 14:34, schrieb Gerrit Pape:
> On Fri, Jul 18, 2014 at 12:03:41PM +, Gerrit Pape wrote:
>> I'm really not keen to add a dependency to daemontools-run, esp. not to
>> the runit package, just for (un)installing and starting/stopping a
>> service.
>
> Hi, I've now prepared this chang
On Fri, Jul 18, 2014 at 12:03:41PM +, Gerrit Pape wrote:
> I'm really not keen to add a dependency to daemontools-run, esp. not to
> the runit package, just for (un)installing and starting/stopping a
> service.
Hi, I've now prepared this changeset. Do you have any comments on it?
Author: Ge
Hi,
Quoting Michael Biebl (2014-07-22 13:54:48)
> Might also be the same as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751624#49
maybe. Except that for me, a prompt was never displayed.
cheers, josch
___
Pkg-systemd-maintainers mailing list
P
Am 22.07.2014 13:34, schrieb Johannes Schauer:
> Hi,
>
> Quoting Michael Biebl (2014-07-22 13:23:13)
>> Am 22.07.2014 09:45, schrieb Johannes Schauer:
>>> Secondly, it is not very helpful to have the emergency mode message
>>> spawn in an (seemingly) infinite loop. I should not have to boot with
>
Hi,
Quoting Michael Biebl (2014-07-22 13:23:13)
> Am 22.07.2014 09:45, schrieb Johannes Schauer:
> > Secondly, it is not very helpful to have the emergency mode message
> > spawn in an (seemingly) infinite loop. I should not have to boot with
> > init=/bin/bash. Instead, the emergency mode should
Am 22.07.2014 09:45, schrieb Johannes Schauer:
> Package: systemd
> Version: 208-6
> Severity: normal
>
> Hi,
>
> after I upgraded systemd today my system became unbootable. I removed
> the "quiet" option from the kernel boot options and after waiting a
> while I can see the following:
>
> [ TIM
Am 22.07.2014 09:45, schrieb Johannes Schauer:
> Secondly, it is not very helpful to have the emergency mode message
> spawn in an (seemingly) infinite loop. I should not have to boot with
> init=/bin/bash. Instead, the emergency mode should start and allow me to
> analyze the situation.
Samuel fi
Hi,
I managed to get some more info on this bug. It seems to indeed be a regression
in systemd. I tried the following:
wget
http://snapshot.debian.org/archive/debian/20140628T163326Z/pool/main/s/systemd/systemd_204-14_amd64.deb
wget
http://snapshot.debian.org/archive/debian/20140628T163326Z/poo
Package: systemd
Version: 208-6
Severity: normal
Hi,
after I upgraded systemd today my system became unbootable. I removed
the "quiet" option from the kernel boot options and after waiting a
while I can see the following:
[ TIME ] Timed out waiting for device dev-mapper-volumegroup/x2dhome.devic
21 matches
Mail list logo
