/usr/local leak in /etc/default/zfs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Native ZFS for Linux |
Fix Released
|
Unknown
|
|||
zfs-linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
While updating my focal server this morning, I got a dpkg prompt about /etc/default/zfs. Inspecting the diff showed some paths changed from /etc to /usr/local/etc:
...
Setting up zfsutils-linux (0.8.3-1ubuntu2) ...
Installing new version of config file /etc/cron.
Configuration file '/etc/default/zfs'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** zfs (Y/I/N/O/D/Z) [default=N] ? d
# Full path to the ZFS cache file?
# See "cachefile" in zpool(8).
-# The default is "/etc/zfs/
-#ZPOOL_
+# The default is "/usr/local/
+#ZPOOL_
#
# Setting ZPOOL_CACHE to an empty string ('') AND setting ZPOOL_IMPORT_OPTS to
-# "-c /etc/zfs/
+# "-c /usr/local/
# This is needed in some cases (extreme amounts of VDEVs, multipath etc).
# Generally, the use of a cache file is usually not recommended on Linux
# because it sometimes is more trouble than it's worth (laptops with external
# devices or when/if device nodes changes names).
-#ZPOOL_
+#ZPOOL_
#ZPOOL_CACHE=""
Changed in zfs: | |
status: | Unknown → New |
Changed in zfs: | |
status: | New → Fix Released |