[Bug 1778860] Re: testparm does not detect bad vfs objects settings

2018-06-27 Thread Andreas Hasenack
Release notes updated: https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#Samba ** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1778860] Re: testparm does not detect bad vfs objects settings

2018-06-27 Thread Andreas Hasenack
Release notes updated: https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#Samba ** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu.

[Bug 1778860] Re: testparm does not detect bad vfs objects settings

2018-06-27 Thread Andreas Hasenack
** Bug watch added: Samba Bugzilla #13490 https://bugzilla.samba.org/show_bug.cgi?id=13490 ** Also affects: samba via https://bugzilla.samba.org/show_bug.cgi?id=13490 Importance: Unknown Status: Unknown ** Changed in: ubuntu-release-notes Assignee: (unassigned) => Andreas

[Bug 1778860] Re: testparm does not detect bad vfs objects settings

2018-06-27 Thread Andreas Hasenack
** Bug watch added: Samba Bugzilla #13490 https://bugzilla.samba.org/show_bug.cgi?id=13490 ** Also affects: samba via https://bugzilla.samba.org/show_bug.cgi?id=13490 Importance: Unknown Status: Unknown ** Changed in: ubuntu-release-notes Assignee: (unassigned) => Andreas

[Bug 1778860] Re: testparm does not detect bad vfs objects settings

2018-06-27 Thread Andreas Hasenack
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

[Bug 1778860] Re: testparm does not detect bad vfs objects settings

2018-06-27 Thread Andreas Hasenack
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