Bug 3434

Summary:	vnstat blocks shutdown
Product:	Mageia	Reporter:	Dave Hodgins <davidwhodgins>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	dmorganec, ennael1, marja11
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	vnstat-1.10-2.mga1.src.rpm	CVE:
Status comment:

Description Dave Hodgins 2011-11-24 02:41:57 CET

In Bug 3074 the line
service vnstat force-reload
was removed from /etc/sysconfig/network-scripts/ifdown.d/vnstat_ip-down
to prevent a shutdown hang.

After an upgrade from mga 1 to the pre-release alpha, I've found it's
back.

If present, the line must not be executed on a shutdown or reboot.

Comment 1 Manuel Hiebel 2011-11-24 18:20:05 CET

Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

CC: (none) => dmorganec, ennael1

Comment 2 Marja Van Waes 2012-01-20 16:00:54 CET

still no maintainer

I do not understand, because I think version 1.0-3.mga2 was in Mga2a1 (oct 27 was almost 2 weeks before the freeze)


Thu Oct 27 2011 dmorgan <dmorgan> 1.10-3.mga2

+ Revision: 158874
- Do not reload vnstat service ( mga #3074)

CC: (none) => marja11

Comment 3 Dave Hodgins 2012-01-20 19:57:57 CET

Either for some reason the update did not get picked up by that
pre-release, in which case this bug can be closed as fixed,
since it's ok now, or there's a problem after an upgrade from
mga 1, where that file isn't getting updated (which I doubt).

I'll check with an upgrade using alpha 3 later today.

Comment 4 Marja Van Waes 2012-02-27 21:32:47 CET

(In reply to comment #3)
> Either for some reason the update did not get picked up by that
> pre-release, in which case this bug can be closed as fixed,
> since it's ok now, or there's a problem after an upgrade from
> mga 1, where that file isn't getting updated (which I doubt).
> 
> I'll check with an upgrade using alpha 3 later today.

@ Dave

What did you find?

Keywords: (none) => NEEDINFO

Comment 5 Dave Hodgins 2012-02-27 22:50:02 CET

Looks like it's ok.  It was something else blocking the shutdown, that's
now been fixed. Closing as invalid.

Status: NEW => RESOLVED
Resolution: (none) => INVALID