Re: [Dovecot] Dovecot vs Ports
Odhiambo WASHINGTON schreef (08-10-06 9:16):
You could have as well explained the problem, if it was that serious.
After the latest portupgrade I rebooted my system and for some reason it stopped booting after loadin acpi.ko Investigated the OS with Fixit (from the first install disc booting and choosing this option from the sysinstall menu). After fsck we could mount the HD and investigate the problem.
Main problem was an error in the /etc/rc.conf.. The dovecot_enable was missing the quotes... I think this is due to the portmanager (the person that has made the port for BSD) instead of Dovecot itself...
I am running this version on 30+ FreeBSD 5.5-STABLE boxes and they all seem fine though. Perhaps I should thank God I still don't run 6.2-PRE?
I think it is a combination of OS version and the person that makes the (accurate) port for that version. Anyway we're all humans after all, so this is allways possible. Just a little bit stressing on a normal Saturdaynight :-)
regards, Jos Chrispijn
* On 08/10/06 13:17 +0200, Jos Chrispijn wrote: | | Odhiambo WASHINGTON schreef (08-10-06 9:16): | >You could have as well explained the problem, if it was that serious. | > | After the latest portupgrade I rebooted my system and for some reason it | stopped booting after loadin acpi.ko | Investigated the OS with Fixit (from the first install disc booting and | choosing this option from the sysinstall menu). | After fsck we could mount the HD and investigate the problem. | | Main problem was an error in the /etc/rc.conf.. The dovecot_enable was | missing the quotes... | I think this is due to the portmanager (the person that has made the | port for BSD) instead of Dovecot itself... | >I am running this version on 30+ FreeBSD 5.5-STABLE boxes and they all | >seem fine though. Perhaps I should thank God I still don't run 6.2-PRE? | > | I think it is a combination of OS version and the person that makes the | (accurate) port for that version. | Anyway we're all humans after all, so this is allways possible. Just a | little bit stressing on a normal Saturdaynight :-) Are you sure portmanager adds entries into /etc/rc.conf? I'd say it's pure madness if it does, because it is not supposed to "decide" for me "how" I want to run an installed port, or even just the fact that I installed a port does not mean I want to run it. I suspect you added the entry and missed the closing quotes ;) I use portupgrade (not portmanager) and it has never added entries to /etc/rc.conf for me. Rather, it tells me to do it. Thanks for clarifying this though, even though it turns out that the tone of your initial post was almost alarmist:) -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash@wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ Waste not, get your budget cut next year.
Odhiambo WASHINGTON schreef (08-10-06 16:23):
- On 08/10/06 13:17 +0200, Jos Chrispijn wrote: | | Odhiambo WASHINGTON schreef (08-10-06 9:16): | >You could have as well explained the problem, if it was that serious. | >
| After the latest portupgrade I rebooted my system and for some reason it | stopped booting after loadin acpi.ko | Investigated the OS with Fixit (from the first install disc booting and | choosing this option from the sysinstall menu). | After fsck we could mount the HD and investigate the problem. | | Main problem was an error in the /etc/rc.conf.. The dovecot_enable was | missing the quotes... | I think this is due to the portmanager (the person that has made the | port for BSD) instead of Dovecot itself... | >I am running this version on 30+ FreeBSD 5.5-STABLE boxes and they all | >seem fine though. Perhaps I should thank God I still don't run 6.2-PRE? | >
| I think it is a combination of OS version and the person that makes the | (accurate) port for that version. | Anyway we're all humans after all, so this is allways possible. Just a | little bit stressing on a normal Saturdaynight :-)Are you sure portmanager adds entries into /etc/rc.conf? I'd say it's pure madness if it does, because it is not supposed to "decide" for me "how" I want to run an installed port, or even just the fact that I installed a port does not mean I want to run it. I suspect you added the entry and missed the closing quotes ;)
Don't think so... It is very unusual that at inspection of rc.conf after upgrading Dovecot, it is appended with a line containing:
dovecot_enable=YES instead of dovecot_enable="YES"
I just wanted to tell, without offensive behaviour towards any portsmanager at all (as I wrote, we are humans after all). Jos
Jos Chrispijn wrote:
[...]
Don't think so... It is very unusual that at inspection of rc.conf after upgrading Dovecot, it is appended with a line containing:
dovecot_enable=YES instead of dovecot_enable="YES"
I just wanted to tell, without offensive behaviour towards any portsmanager at all (as I wrote, we are humans after all). Jos
I have used 'portmanager' for quite some time now. In fact, I started using it when it was still beta.
Portmanager does not add anything to the /etc/rc.conf file unless it is part of the ports 'Makefile'. To find out exactly what transpired, I would suggest that you contact the port maintainer:
robin@isometry.net
and inquire as to the behavior of the dovecot port.
-- Gerard Seibert gerard@seibercom.net
Gerard Seibert wrote:
Jos Chrispijn wrote:
[...]
Don't think so... It is very unusual that at inspection of rc.conf after upgrading Dovecot, it is appended with a line containing:
dovecot_enable=YES instead of dovecot_enable="YES"
I just wanted to tell, without offensive behaviour towards any portsmanager at all (as I wrote, we are humans after all). Jos
I have used 'portmanager' for quite some time now. In fact, I started using it when it was still beta.
Portmanager does not add anything to the /etc/rc.conf file unless it is part of the ports 'Makefile'. To find out exactly what transpired, I would suggest that you contact the port maintainer:
robin@isometry.net
and inquire as to the behavior of the dovecot port.
not related to the post in question here, but i find portmaster to be far superior to portmanager and portupgrade. Check it out
i have never, ever seen port-anything add an entry to rc.conf. at best pkg-install will have a note to do so, at worst it will not and you have to check out the file installed to rc.d to see the proper entry to add.
participants (4)
-
Eric
-
Gerard Seibert
-
Jos Chrispijn
-
Odhiambo WASHINGTON