On Wed, May 14, 2014 at 11:50:39 -0400, Vivek Goyal wrote:
On Wed, May 14, 2014 at 03:16:39PM +0200, Martin Milata wrote:
[..]
> > I am not a big fan of this idea. Why not leave it as follows.
> >
> > ------------------------------------------------------------------
> > Path: /var/crash
> > Local file system: Partition:
> > core will be in /var/crash/%DATE/
> > -----------------------------------------------------------------
> >
> > Reason being.
> >
> > - First of all now system-config-kdump will have to implement the logic to
> > map which disk /var/crash is mounted on and then do the relative path
> > calculation on that disk.
> >
> > - More importantly, this is not kdump API. If kdump changes behavior down
> > the line, system-config-kdump will be out of sync again.
> >
> > So to me let us not try to be too intelligent. Once we say core will be
> > saved in /var/crash/%DATE, I think it is clear. Who cares what's the disk
> > and what's the filesystem. Admin has plenty of ways to figure out
what's
> > the disk backing /var/crash/.
>
> Oops, I didn't catch this email yesterday and went ahead implementing
> it. Scratch builds if you want to try it:
>
> F20:
http://koji.fedoraproject.org/koji/taskinfo?taskID=6848717
> rawhide:
http://koji.fedoraproject.org/koji/taskinfo?taskID=6848763
Hi Martin,
If you have already done the changes, I guess there is no need to
revert it.
So after your changes, how do all three fields look like for the case
where /var/crash is mounted on some other disk, say /dev/foo.
If /dev/foo (ext4) is mounted on /var/crash then it looks like this:
------------------------------------------------------------------
Path: /var/crash
Local file system: Partition: Unspecified
core will be in /%DATE on ext4 /dev/foo
------------------------------------------------------------------
Martin