Re: Qmail install success on 1.4; possible package bug?
On Fri, Feb 10, 2006 at 09:56:24AM -0700, Tim Darby wrote: > [EMAIL PROTECTED] wrote: > >On Sat, Jan 14, 2006 at 09:22:27PM -0700, Tim Darby wrote: > >>Thanks for the suggestions! I installed qmail totally manually, since I > >>didn't see a DFly package for it. > > > >There is no binary package because it can't be build without patching > >and therefore the package is restricted. > > > >Joerg > > Joerg, > > I noticed there is a binary package for Qmail now. Thanks! I tried it, grmbl. that is a bug. It should definitely not be part of the upload set. You are most likely having different user ids and the permissions are therefore incorrect. Joerg
Re: Qmail install success on 1.4; possible package bug?
[EMAIL PROTECTED] wrote: On Sat, Jan 14, 2006 at 09:22:27PM -0700, Tim Darby wrote: Thanks for the suggestions! I installed qmail totally manually, since I didn't see a DFly package for it. There is no binary package because it can't be build without patching and therefore the package is restricted. Joerg Joerg, I noticed there is a binary package for Qmail now. Thanks! I tried it, but it seemed to only partially work. That is, it installed all the binaries, but qmail-send failed to start. Qmail-smtpd and Qmail-pop3d do start. When I looked into what was going on, I found that the installer had not created the file /var/qmail/queue/lock/sendmutex. Beyond that, it hadn't created any of the subdirectories or files under /var/qmail/queue. After manually creating sendmutex, I found that qmail-send still wouldn't start and that's when I noticed that lspawn and rspawn, which send depends on, weren't starting either. I haven't had time to figure out the problem with those and they don't give any errors when they fail. Thanks again for the package work, Tim
Re: Qmail install success on 1.4; possible package bug?
On Sat, Jan 14, 2006 at 09:22:27PM -0700, Tim Darby wrote: > Thanks for the suggestions! I installed qmail totally manually, since I > didn't see a DFly package for it. There is no binary package because it can't be build without patching and therefore the package is restricted. Joerg
Re: Qmail install success on 1.4; possible package bug?
Amitai Schlair wrote: > Tim Darby wrote: > >> Thanks, I got sidetracked with another project and just now getting >> back to Qmail on DFly. It appears that root, which is what this runs >> under, already has those directories in its path, so I don't think >> that's the issue. I'm not very up on RC scripts but I found that the >> following modification to the svscan.sh that came with the package >> worked: >> >> From: >> exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' >> >> exec env PATH=/usr/pkg/bin:$PATH /bin/csh -cf '/usr/pkg/bin/svscan >> /var/spool/service &' >> >> If this is not the best way to do fix this, I'd like to know, >> especially if there's a preferred DFly way of doing it. > > A pkgsrc developer brought your message to my attention. I maintain > the djbware in pkgsrc and would like to help. > > How are you installing qmail? There's a fairly good package (if I do > say so myself :-) in pkgsrc/mail/qmail that I've been happily using > for years. > > Does DragonFly have a NetBSD-derived /etc/rc.d subsystem? If so, I > highly recommend not using svscan and /service to run qmail. Instead, > try pkgsrc/mail/qmail-run, which makes qmail feel like an ordinary > BSD-style daemon, complete with rc.d scripts, knobs in /etc/rc.conf, > etc. Interesting a scheme though /service is, I can't imagine going > back to it. > > I'm not subscribed to this list; please Cc me on any replies. > > - Amitai > Thanks for the suggestions! I installed qmail totally manually, since I didn't see a DFly package for it. If the NetBSD qmail package can be used, I will by all means try it. I'm definitely not wedded to the djb daemontools. The only reason I use them is that qmail docs recommend that and so I've just always done it that way. I will definitely try out qmail-run and see how it goes. Thanks, Tim
Re: Qmail install success on 1.4; possible package bug?
Tim Darby wrote: Thanks, I got sidetracked with another project and just now getting back to Qmail on DFly. It appears that root, which is what this runs under, already has those directories in its path, so I don't think that's the issue. I'm not very up on RC scripts but I found that the following modification to the svscan.sh that came with the package worked: From: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' exec env PATH=/usr/pkg/bin:$PATH /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' If this is not the best way to do fix this, I'd like to know, especially if there's a preferred DFly way of doing it. A pkgsrc developer brought your message to my attention. I maintain the djbware in pkgsrc and would like to help. How are you installing qmail? There's a fairly good package (if I do say so myself :-) in pkgsrc/mail/qmail that I've been happily using for years. Does DragonFly have a NetBSD-derived /etc/rc.d subsystem? If so, I highly recommend not using svscan and /service to run qmail. Instead, try pkgsrc/mail/qmail-run, which makes qmail feel like an ordinary BSD-style daemon, complete with rc.d scripts, knobs in /etc/rc.conf, etc. Interesting a scheme though /service is, I can't imagine going back to it. I'm not subscribed to this list; please Cc me on any replies. - Amitai
Re: Qmail install success on 1.4; possible package bug?
On Sun, Jan 08, 2006 at 09:12:38PM -0700, Tim Darby wrote: > Anyway, I think I've either found a package bug or it's just me being > clueless, probably the latter. As part of the Qmail install, I installed > the package daemontools-0.76. After I setup the service folders and > rebooted, I got boot errors from svscan telling me that it couldn't > start the 'supervise' processes. After some poking around, I think the > problem is that the supervise program is installed by the package in > /usr/pkg/bin, however that folder is not in the path of the shell > command that the included /usr/local/etc/rc.d/svscan.sh script runs. > When I copied supervise to /usr/sbin and rebooted, it worked fine. > Here's the only command that the svscan.sh script runs: Please fill a NetBSD/pkgsrc PR against either daemontools or qmail, whatever is more appropiate. RC scripts and related things MUST NOT depend on PATH. Joerg
Re: Qmail install success on 1.4; possible package bug?
Justin C. Sherrill wrote: Tim Darby wrote: I got Qmail up and running today on 1.4 and it looks good. Coming from OpenBSD and having never done anything with FreeBSD or DragonFly before, it took me quite a while to figure out where everything was, but I did it. I have to give a hearty thanks to the people who put the DragonFly handbook together; I'd have been really stuck without it. From the OpenBSD perspective, I do miss having lynx and sudo as part of the base install. Anyway, I think I've either found a package bug or it's just me being clueless, probably the latter. As part of the Qmail install, I installed the package daemontools-0.76. After I setup the service folders and rebooted, I got boot errors from svscan telling me that it couldn't start the 'supervise' processes. After some poking around, I think the problem is that the supervise program is installed by the package in /usr/pkg/bin, however that folder is not in the path of the shell command that the included /usr/local/etc/rc.d/svscan.sh script runs. When I copied supervise to /usr/sbin and rebooted, it worked fine. Here's the only command that the svscan.sh script runs: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' Good work on 1.4 btw! Tim You'll want to put /usr/pkg/bin and /usr/pkg/sbin in your path; that'll get them found. Add it to all your existing users and /usr/share/skel, I think it is, so that new users on the system get it too. There's probably other places I'm not thinking of - /etc/login.conf, .profile, etc. I thought the $PATH was changed by default; maybe I'm wrong. Thanks, I got sidetracked with another project and just now getting back to Qmail on DFly. It appears that root, which is what this runs under, already has those directories in its path, so I don't think that's the issue. I'm not very up on RC scripts but I found that the following modification to the svscan.sh that came with the package worked: From: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' To: exec env PATH=/usr/pkg/bin:$PATH /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' If this is not the best way to do fix this, I'd like to know, especially if there's a preferred DFly way of doing it. Tim
Re: Qmail install success on 1.4; possible package bug?
Tim Darby wrote: I got Qmail up and running today on 1.4 and it looks good. Coming from OpenBSD and having never done anything with FreeBSD or DragonFly before, it took me quite a while to figure out where everything was, but I did it. I have to give a hearty thanks to the people who put the DragonFly handbook together; I'd have been really stuck without it. From the OpenBSD perspective, I do miss having lynx and sudo as part of the base install. Anyway, I think I've either found a package bug or it's just me being clueless, probably the latter. As part of the Qmail install, I installed the package daemontools-0.76. After I setup the service folders and rebooted, I got boot errors from svscan telling me that it couldn't start the 'supervise' processes. After some poking around, I think the problem is that the supervise program is installed by the package in /usr/pkg/bin, however that folder is not in the path of the shell command that the included /usr/local/etc/rc.d/svscan.sh script runs. When I copied supervise to /usr/sbin and rebooted, it worked fine. Here's the only command that the svscan.sh script runs: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' Good work on 1.4 btw! Tim You'll want to put /usr/pkg/bin and /usr/pkg/sbin in your path; that'll get them found. Add it to all your existing users and /usr/share/skel, I think it is, so that new users on the system get it too. There's probably other places I'm not thinking of - /etc/login.conf, .profile, etc. I thought the $PATH was changed by default; maybe I'm wrong.
Qmail install success on 1.4; possible package bug?
I got Qmail up and running today on 1.4 and it looks good. Coming from OpenBSD and having never done anything with FreeBSD or DragonFly before, it took me quite a while to figure out where everything was, but I did it. I have to give a hearty thanks to the people who put the DragonFly handbook together; I'd have been really stuck without it. From the OpenBSD perspective, I do miss having lynx and sudo as part of the base install. Anyway, I think I've either found a package bug or it's just me being clueless, probably the latter. As part of the Qmail install, I installed the package daemontools-0.76. After I setup the service folders and rebooted, I got boot errors from svscan telling me that it couldn't start the 'supervise' processes. After some poking around, I think the problem is that the supervise program is installed by the package in /usr/pkg/bin, however that folder is not in the path of the shell command that the included /usr/local/etc/rc.d/svscan.sh script runs. When I copied supervise to /usr/sbin and rebooted, it worked fine. Here's the only command that the svscan.sh script runs: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' Good work on 1.4 btw! Tim
