[Bug 1778860] Re: testparm does not detect bad vfs objects settings
Andreas Hasenack
andreas at canonical.com
Wed Jun 27 12:53:08 UTC 2018
The fact that the vfs_aio_linux module was dropped should go into the
release notes, so I added a bug task for that.
Invalid vfs objects are indeed annoying to debug, because not only is
testparm oblivious to such errors, smbd will also start up just fine
until the share is connected to.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu)
Status: New => Triaged
** Changed in: samba (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1778860
Title:
testparm does not detect bad vfs objects settings
Status in Release Notes for Ubuntu:
New
Status in samba package in Ubuntu:
Triaged
Bug description:
When I upgraded to bionic, samba broke. The failure was nonobvious
until I ran it in interactive mode.
testparm should be able to check I think?
anyhow, the config issue was that vfs_aio_linux had been removed, but
my config still said
vfs objects = aio_linux
and testparm did not detect that as broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1778860/+subscriptions
More information about the foundations-bugs
mailing list