Re: [Dovecot] Upgrade to 2.0 - Not so smooth
> On 2010-08-16 07:16:46 -0700, Marc Perkel wrote: >> Maybe dovecot could use the "nobody" user if dovenull doesn't exist? > > you could just read the warning message, create the user and stop > worrying? > > and no ... it shouldnt fallback to nobody. a broken set up is a broken > setup and needs to be fixed. > Wow. Well said. -- Dennis Clarke dcla...@opensolaris.ca <- Email related to the open source Solaris dcla...@blastwave.org <- Email related to open source for Solaris
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-16 07:16:46 -0700, Marc Perkel wrote: > Maybe dovecot could use the "nobody" user if dovenull doesn't exist? you could just read the warning message, create the user and stop worrying? and no ... it shouldnt fallback to nobody. a broken set up is a broken setup and needs to be fixed. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On Mon, 2010-08-16 at 07:16 -0700, Marc Perkel wrote: > Maybe dovecot could use the "nobody" user if dovenull doesn't exist? The entire point of dovenull user is that it's not used by anything else. The only things I'm going to change here is to make the error message somewhat better for v2.0.1 and add a note about this user to NEWS file / release announcement.
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/16/2010 2:45 AM, William Blunn wrote: On 15/08/2010 22:49, Marc Perkel wrote: On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named "dovenull" to work. Please create user "dovenull" and try again. No. The first sentence of your proposed message is FALSE. On 15/08/2010 17:10, Timo Sirainen wrote: - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. Dovecot does NOT need a user named "dovenull" to work. The second sentence is predicated on the first and as such also falls down. Dovecot needs a user named by the default_login_user setting in order to work. Whilst this defaults to "dovenull", there is nothing to stop you setting it to something else (e.g. "flibble"). The point is that the answer is more of a commentary and the right solution depends on the situation. Rather than try to squeeze solution summaries into every error message, I would suggest having a link (perhaps into the Dovecot wiki) in the error message, e.g. Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see http://wiki2.dovecot.org/Errors/NoDefaultLoginUser) (Note that the above URL is hypothetical.) Then have a commentary and suggested solutions in the wiki. Alternatively, the link could rooted at a notional documentation root like: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see documentation "Errors/NoDefaultLoginUser") so that users could refer to a local copy of the documentation rather than encouraging load on the Dovecot wiki server(s). Bill Maybe dovecot could use the "nobody" user if dovenull doesn't exist?
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On Aug 15, 2010, at 9:04 PM, Jim wrote: On Aug 15, 2010, at 4:01 PM, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. Or in the case of OS X, dscl... Documenting this is good, but perhaps the configure script could check if the user exists, and instruct the user to create this manually before going any further? And some may be building binaries packages for distribution so forcing user creation on a build server would be extra unhelpful work. On thing I was considering was if patching to allow configure to set -- default_login_user=_dovenull and --default_internal_user=_dovecot. I don't think this is a big deal but it would allow package builders to build packages with default names that match their distributions. BTW, things are fine the way they are. The fewer options that meet the needs the better. Regards, Bradley Giesbrecht
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-15 12:03 PM, Marc Perkel wrote: > Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't > exist: dovenull > > Just some real time feedback. I don't know what dovenull user is or > why it is necessary. It would be a lot smoother (and this probably applies to all other software you use) if you would spend at least 5 SECONDS doing a little research before wasting everyone's (especially Timo's) time with questions that you can easily answer yourself: http://www.lmgtfy.com/?q=dovenull For dovecot stuff, I've found that simply adding the word 'wiki' after the other search term will almost always provide the link to the wiki page describing whatever it is: http://www.lmgtfy.com/?q=dovenull+wiki Yes, this is a pet peeve of mine... -- Best regards, Charles
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 15/08/2010 22:49, Marc Perkel wrote: On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named "dovenull" to work. Please create user "dovenull" and try again. No. The first sentence of your proposed message is FALSE. On 15/08/2010 17:10, Timo Sirainen wrote: - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. Dovecot does NOT need a user named "dovenull" to work. The second sentence is predicated on the first and as such also falls down. Dovecot needs a user named by the default_login_user setting in order to work. Whilst this defaults to "dovenull", there is nothing to stop you setting it to something else (e.g. "flibble"). The point is that the answer is more of a commentary and the right solution depends on the situation. Rather than try to squeeze solution summaries into every error message, I would suggest having a link (perhaps into the Dovecot wiki) in the error message, e.g. Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see http://wiki2.dovecot.org/Errors/NoDefaultLoginUser) (Note that the above URL is hypothetical.) Then have a commentary and suggested solutions in the wiki. Alternatively, the link could rooted at a notional documentation root like: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull (see documentation "Errors/NoDefaultLoginUser") so that users could refer to a local copy of the documentation rather than encouraging load on the Dovecot wiki server(s). Bill
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On Aug 15, 2010, at 4:01 PM, Marc Perkel wrote: > Seems to me that it wouldn't take a lot of code to at lease find if they have > adduser or useradd. Or in the case of OS X, dscl... Documenting this is good, but perhaps the configure script could check if the user exists, and instruct the user to create this manually before going any further?
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 5:49 PM, Marc Perkel wrote: On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named "dovenull" to work. Please create user "dovenull" and try again. I agree its not as simple as people would think but, if dovecot would log everything relevant, dovecot could use its own logs to know what environment it is within. Jerrale G. SC Senior Admin
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named "dovenull" to work. Please create user "dovenull" and try again.
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: > Seems to me that it wouldn't take a lot of code to at lease find if > they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 9:58 AM, Marcus Rueckert wrote: On 2010-08-15 09:44:49 -0700, Marc Perkel wrote: might want to automatically add dovenull to the install script if possible. Perhaps a better error message than the one above that indicates the solution is to create the dovenull user. I dont think you can know all the different tools distros use to create users. (adduser vs useradd e.g.) so documenting this is the better approach. darix Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd.
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-15 09:44:49 -0700, Marc Perkel wrote: > might want to automatically add dovenull to the install script if > possible. Perhaps a better error message than the one above that > indicates the solution is to create the dovenull user. I dont think you can know all the different tools distros use to create users. (adduser vs useradd e.g.) so documenting this is the better approach. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 9:10 AM, Timo Sirainen wrote: On 15.8.2010, at 17.03, Marc Perkel wrote: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary. I added now to http://wiki2.dovecot.org/Upgrading/2.0 : - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. might want to automatically add dovenull to the install script if possible. Perhaps a better error message than the one above that indicates the solution is to create the dovenull user. Everything seems to be working. Is there a "what's new" feature list anywhere? Anything cool I might want to try?
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 15/08/2010 17:14, Dennis Clarke wrote: On 15.8.2010, at 17.03, Marc Perkel wrote: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary. I added now to http://wiki2.dovecot.org/Upgrading/2.0 : - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. Dovecot 2.x seems to be very close to release grade. Could you provide a guess as to when it will be released so that I can plan downtime for the upgrade on my production servers? See Timo's comment of Friday 13/08/2010 19:29: http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz.sig I expect this to be the last release candidate. Unless release critical bugs are reported, I'll update the version number to v2.0.0 on Monday morning without any other changes. Since rc5 there have been mainly some small fixes and some error message improvements. The only (somewhat) important fixes are: - dict quota didn't always decrease quota when messages were expunged - Shared INBOX wasn't always listed with FS layout "I'll update the version number to v2.0.0 on Monday morning" Bill
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
> On 15.8.2010, at 17.03, Marc Perkel wrote: > >> Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: >> dovenull >> >> Just some real time feedback. I don't know what dovenull user is or why >> it is necessary. > > I added now to http://wiki2.dovecot.org/Upgrading/2.0 : > > - Dovecot uses two internal users now by default: dovenull and dovecot. > You need to create the dovenull user or change default_login_user > setting. > Dovecot 2.x seems to be very close to release grade. Could you provide a guess as to when it will be released so that I can plan downtime for the upgrade on my production servers? -- Dennis Clarke dcla...@opensolaris.ca <- Email related to the open source Solaris dcla...@blastwave.org <- Email related to open source for Solaris
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 15.8.2010, at 17.03, Marc Perkel wrote: > Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull > > Just some real time feedback. I don't know what dovenull user is or why it is > necessary. I added now to http://wiki2.dovecot.org/Upgrading/2.0 : - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting.