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
--
To UNSUBSCRIBE, email to
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
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 22/10/14 at 07:08pm, Michael Biebl wrote:
> You might be affected by [1].
Same problem!
# ls -l /etc/cups/ppd
total 896
-rw-r- 1 root lp24950 Out 15 15:29 Brother-HL-5370DW-series.ppd
-rw-r- 1 root lp 9838 Out 15 13:20
Brother-HL-5370DW-series.ppd.O
-rw-r--r-- 1 root root 338
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 minutes.
> > That's why I wanted to know, how long you let the systemd-
On 22/10/14 at 07:08pm, Michael Biebl wrote:
> Control: tags -1 moreinfo
>
> On Tue, 21 Oct 2014 04:46:45 +0200 Michael Biebl wrote:
> > Am 21.10.2014 um 02:19 schrieb Marcelo Laia:
> > > On 21/10/14 at 01:07am, Michael Biebl wrote:
> > >> How long did you wait?
> > >
> > > no limit! Indefinitel
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 minutes.
> That's why I wanted to know, how long you let the systemd-tmpfiles job run.
Case in point: A user at [1] repo
Processing control commands:
> tags -1 moreinfo
Bug #766092 [systemd] systemd: Boot hangs indefinitely
Added tag(s) moreinfo.
--
766092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to de
Control: tags -1 moreinfo
On Tue, 21 Oct 2014 04:46:45 +0200 Michael Biebl wrote:
> Am 21.10.2014 um 02:19 schrieb Marcelo Laia:
> > On 21/10/14 at 01:07am, Michael Biebl wrote:
> >> How long did you wait?
> >
> > no limit! Indefinitely
> >
>
> Could you check your /tmp (and /var/tmp) director
Am 21.10.2014 um 02:19 schrieb Marcelo Laia:
> On 21/10/14 at 01:07am, Michael Biebl wrote:
>> How long did you wait?
>
> no limit! Indefinitely
>
Could you check your /tmp (and /var/tmp) directory if it contains a
large amount of symlinks (created by cups) or files. IIRC there is a bug
report t
On 21/10/14 at 02:29am, Michael Biebl wrote:
Hi,
> Btw, is there anything special about your setup, e.g. how does your
> partition layout look like?
:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 111,8G 0 disk
├─sda1 8:10 23,3G 0 part /
├─sda2 8:20 1K
On 21/10/14 at 02:27am, Michael Biebl wrote:
> Can you tar those files and send attach them to the bug report, please.
>
Here you are!
--
Laia, ML
http://ppgcf.ufvjm.edu.br/~ppgcf/marcelolaia
output.tar
Description: Unix tar archive
Am 21.10.2014 um 02:27 schrieb Michael Biebl:
> Hi,
>
> Am 21.10.2014 um 02:19 schrieb Marcelo Laia:
>> # ls -l /usr/lib/tmpfiles.d.old/
>> total 48
>> -rw-r--r-- 1 root root 480 Set 28 16:05 debian.conf
>> -rw-r--r-- 1 root root 595 Set 22 14:43 gvfsd-fuse-tmpfiles.conf
>> -rw-r--r-- 1 root roo
Hi,
Am 21.10.2014 um 02:19 schrieb Marcelo Laia:
> # ls -l /usr/lib/tmpfiles.d.old/
> total 48
> -rw-r--r-- 1 root root 480 Set 28 16:05 debian.conf
> -rw-r--r-- 1 root root 595 Set 22 14:43 gvfsd-fuse-tmpfiles.conf
> -rw-r--r-- 1 root root 1181 Set 28 16:05 legacy.conf
> -rw-r--r-- 1 root root
On 21/10/14 at 01:07am, Michael Biebl wrote:
> How long did you wait?
no limit! Indefinitely
> Which kernel version is it exactly?
:~$ uname -a
Linux marcelo 3.16-2-686-pae #1 SMP Debian 3.16.3-2 (2014-09-20) i686
GNU/Linux
:~$
I found a workaround [1] and can boot after I did it:
# mv /usr/l
Am 20.10.2014 um 23:55 schrieb Marcelo Laia:
> The same here! Breaks the whole system! Isn't possible to boot! O hit
> Ctrl+Alt+Del and system reboot and hang again! The message is:
>
> "a start job is running for Create Volatile files and directories (xx
> minutes / no limit)"
>
> My kernels are
The same here! Breaks the whole system! Isn't possible to boot! O hit
Ctrl+Alt+Del and system reboot and hang again! The message is:
"a start job is running for Create Volatile files and directories (xx
minutes / no limit)"
My kernels are the Debian default linux-images. I don't compile it.
--
On Lu, 20 oct 14, 22:22:28, Thomas Zoschke wrote:
>
> I just installed my first systemd, previously had sysv-initcore, well-working.
> The boot after the installation hung forever after a timed out job for the
> boot drive.
> I would have expected the system to boot.
> I cannot even get to a sulog
Package: systemd
Version: 215-5+b1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
I just installed my first systemd, previously had sysv-initcore, well-working.
The boot after the installation hung forever after a timed out job for the
boot drive.
I would have expected
19 matches
Mail list logo
