Processing commands for cont...@bugs.debian.org:
> reassign 766429 systemd-sysv
Bug #766429 [sysstat] sysstat service will not start on machines with systemd
Bug reassigned from package 'sysstat' to 'systemd-sysv'.
No longer marked as found in versions sysstat/11.0.1-1.
Ignoring request to alter f
On Thu, Oct 23, 2014 at 09:02:01AM +0300, Niko Tyni wrote:
> On Wed, Oct 22, 2014 at 04:58:03PM +0200, intrigeri wrote:
> > Holger Levsen wrote (22 Oct 2014 14:06:05 GMT) :
> > > BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line
> > > 85.
> >
> > ... which is shipped by the
> (I'm using vixie's crontab) you cannot really assume the crontab is
> syntactically ok.
There is the posix standard, but there are also extra features that
are not in the standard like the "value/step"
http://pubs.opengroup.org/onlinepubs/009696699/utilities/crontab.html ;
anyway crontab(5) wou
Am Donnerstag, 23. Oktober 2014, 00:15:48 schrieb Marcelo Laia:
> On 22/10/14 at 07:15pm, Michael Biebl wrote:
> > Am 22.10.2014 um 19:08 schrieb Michael Biebl:
> > > If you even had more files in /tmp and maybe you have an HDD, it's very
> > > well possible, that systemd-tmpfiles will need several
On Wed, 22 Oct 2014 20:17:19 -0500 Preston Maness
wrote:
> Package: sysstat
> Version: 11.0.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> It is currently not possible to start sysstat on a systemd enabled
> system:
>
> # service sysstat start
> Fai
Am 23.10.2014 um 13:54 schrieb Martin Steigerwald:
> Am Donnerstag, 23. Oktober 2014, 00:15:48 schrieb Marcelo Laia:
>> On 22/10/14 at 07:15pm, Michael Biebl wrote:
>>> Am 22.10.2014 um 19:08 schrieb Michael Biebl:
If you even had more files in /tmp and maybe you have an HDD, it's very
we
On 23/10/14 at 01:54pm, Martin Steigerwald wrote:
> I have tried:
> >
> > # rm -rf *
Sorry. There are a mistake here. I run the command:
# rm -rf /tmp/*
I write the command wrong, but I run the right one.
--
Laia, ML
http://ppgcf.ufvjm.edu.br/~ppgcf/marcelolaia
_
Processing commands for cont...@bugs.debian.org:
> retitle 766092 systemd: blocks during boot at: Create Volatile files and
> directories
Bug #766092 [systemd] systemd: Boot hangs indefinitely
Changed Bug title to 'systemd: blocks during boot at: Create Volatile files and
directories' from 'syst
I mounted the drive on my Debian stable system and deleted the '/tmp'
directory.
The boot sequence and time is back to normal now, thanks very much for the
help!
--
Regards
Marc
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.al
Processing commands for cont...@bugs.debian.org:
> forcemerge 766092 765957 765784
Bug #766092 [systemd] systemd: blocks during boot at: Create Volatile files and
directories
Bug #765957 [systemd] systemd: Create Volatile Files and Directories... taking
5 minutes
Severity set to 'critical' from
Processing commands for cont...@bugs.debian.org:
> severity 766429 normal
Bug #766429 [systemd-sysv] sysstat service will not start on machines with
systemd
Severity set to 'normal' from 'grave'
> retitle 766429 sysstat service fails to start after installation without
> daemon-reload
Bug #76642
Processing commands for cont...@bugs.debian.org:
> tags 765784 - moreinfo
Bug #765784 [systemd] systemd: Very slow boot time (4 Minutes).
Bug #765957 [systemd] systemd: Create Volatile Files and Directories... taking
5 minutes
Bug #766092 [systemd] systemd: blocks during boot at: Create Volatile
I can confirm this behavior on a fresh install and it does get fixed with a
systemctl daemon-reload:
# /etc/init.d/sysstat start
Starting sysstat (via systemctl): sysstat.serviceFailed to start
sysstat.service: Unit sysstat.service failed to load: No such file or
directory.
failed!
# systemctl d
systemd-cron_1.3.1+ds1-2_amd64.changes uploaded successfully to localhost
along with the files:
systemd-cron_1.3.1+ds1-2_all.deb
systemd-cron_1.3.1+ds1-2.dsc
systemd-cron_1.3.1+ds1-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
_
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 14 Oct 2014 09:40:12 +0200
Source: systemd-cron
Binary: systemd-cron
Architecture: source all
Version: 1.3.1+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Systemd Maintainers
Changed-By: Michael
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Greetings,
Thanks for updating the bug package. I'm guessing systemd-sysv handles
sysvinit-style init scripts when systemd service files aren't available?
In any case, I was unable to test the suggested fix prior to shutting
down this machine. Upon
Am 24.10.2014 um 04:14 schrieb Preston Maness:
> Greetings,
>
> Thanks for updating the bug package. I'm guessing systemd-sysv handles
> sysvinit-style init scripts when systemd service files aren't available?
>
> In any case, I was unable to test the suggested fix prior to shutting
> down this m
Processing commands for cont...@bugs.debian.org:
> found 766345 1.3.1+ds1-2
Bug #766345 [systemd-cron] Does not mail user in case of crontab errors
Marked as found in versions systemd-cron/1.3.1+ds1-2.
> found 766348 1.3.1+ds1-2
Bug #766348 [systemd-cron] Does not parse ranges correctly
Ignoring r
Processing commands for cont...@bugs.debian.org:
> found 766348 1.3.1+ds1-2
Bug #766348 [systemd-cron] Does not parse ranges correctly
Marked as found in versions systemd-cron/1.3.1+ds1-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
766348: http://bugs.debian.
19 matches
Mail list logo
