Re: sendmail problem in 4.6-RELEASE - solution
On Wed, 19 Jun 2002, Mario Pranjic wrote: 2. Have one and only one smmsp account. 3. Have one and only one smmsp group. 4. The gid of the smmsp account matches the gid of the smmsp group. 5. /var/spool/clientmqueue is mode 0770, owned by smmsp:smmsp. 6. /usr/libexec/sendmail/sendmail is mode 2755, owned by root:smmsp. I don't have this account/group. This is something new in sendmail? It's interesting though: drwxrwx--- 2 25 25 512 Jun 11 06:17 clientmqueue Seems that the upgrade procedure didn't make the smmsp user/group. On another FreeBSD box I have smmsp account/group. It is probably because that box was ugraded only once: from 4.5 to 4.6. A box that had this sendmail problem was originally FreeBSD 4.3-RELEASE and since it was upgraded to 4.5 and now to 4.6 (always RELEASE). I manually added that smmsp user/group and now sendmail works just fine. Thanks for your help! Mario Pranjic, dipl.ing. sistem administrator Knjiznica, Institut Rudjer Boskovic - e-mail: [EMAIL PROTECTED] ICQ: 72059629 tel: +385 1 45 60 954 (interni: 1293) - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sendmail problem in 4.6-RELEASE
On Wed, 19 Jun 2002, Mario Pranjic wrote: 9. Have installed a proper /etc/mail/submit.cf (not the same as sendmail.cf). Don't have this file in /etc/mail. Have some examples though: /etc/upgrade/mail/freebsd.submit.cf /etc/upgrade/mail/submit.cf /usr/share/sendmail/cf/cf/submit.cf /usr/src/contrib/sendmail/cf/cf/submit.cf Yes, ofcourse, I had to copy /etc/upgrade/mail/freebsd.submit.cf in /etc/mail submit.cf in order to be able to send mail. Mario Pranjic, dipl.ing. sistem administrator Knjiznica, Institut Rudjer Boskovic - e-mail: [EMAIL PROTECTED] ICQ: 72059629 tel: +385 1 45 60 954 (interni: 1293) - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
mod_php4 won't compile for Apache 2.0.39
I just cvsuped and updated apache2 to 2.0.39 when I cd /usr/ports/www/mod_php4/ make -DWITH_APACHE2I get the following errors:-I/usr/ports/www/mod_php4/work/php-4.2.1/TSRM -I/usr/local/include/pth -O -pipe -I/usr/local/include -pthread -DZTS -prefer-pic -c php_functions.cphp_functions.c:93: syntax error*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1/sapi/apache2filter.*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1/sapi/apache2filter.*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1/sapi.*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1.*** Error code 1 Stop in /usr/ports/www/mod_php4.*** Error code 1 Stop in /usr/ports/www/mod_php4.
mod_php4 won't compile for Apache2 2.0.39
I just cvsuped and updated apache2 to 2.0.39 when I cd /usr/ports/www/mod_php4/ make -DWITH_APACHE2I get the following errors:-I/usr/ports/www/mod_php4/work/php-4.2.1/TSRM -I/usr/local/include/pth -O -pipe -I/usr/local/include -pthread -DZTS -prefer-pic -c php_functions.cphp_functions.c:93: syntax error*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1/sapi/apache2filter.*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1/sapi/apache2filter.*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1/sapi.*** Error code 1 Stop in /usr/ports/www/mod_php4/work/php-4.2.1.*** Error code 1 Stop in /usr/ports/www/mod_php4.*** Error code 1 Stop in /usr/ports/www/mod_php4.
Re: IPFW rules on tunX devices
On Wed, Jun 19, 2002 at 04:57:21PM +1000, Peter Jeremy wrote: I have a situation where I want to have some ipfw rules permanently associated with tun0. In 4.5-RELEASE, I just included lines like the following in the rules file specified as firewall_type in rc.conf: add 11010 allow tcp from 10.2.3.4 to 10.2.3.5 keep-state in recv tun0 setup In 4.6-RELEASE, the tun devices are created on demand and so tun0 doesn't exist don't exist when the firewall rules are added. Other than starting ppp(8), how do I create tun0? I thought ifconfig tun0 create would work, but that returns: ifconfig: SIOCIFCREATE: Invalid argument Any suggestions? I was able to hack around this for someone by placing an entry in /etc/rc.early to open the tun0 device so the interface would be created. The disgusting hack I used was a staticly linked binary which opened /dev/tun0. On current the following signficantly less gross shell works: echo /dev/tun0 I don't know if this works on stable though. I'm sure there's a better solution, but I've never claimed to be a shell hacker. :-) IMO, the long term solution it to fix the tun(4) driver to use interface cloning like gif(4) so you can do ifconfig tun0 create as necessicary. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg46533/pgp0.pgp Description: PGP signature
Re: make buildworld for 4_6_0_RELEASE failed
Ulrich Drolshagen wrote: Hello fbsd-stable, my make buildworld of 4_6_0_RELEASE failed with pendig error message. Its my first try updating (from 4.4 release) this way so I don't know exactly what happend. I did a fresh install for the src- and the ports-tree from Distribution-CD and cvsuped to RELENG_4_6_0_RELEASE. You'll find my /etc/cvsupfile in the bottom, just in case I missed something important. cvsup returned successfully so far. You aren't running a full set of source and the build is bombing because of it. You are missing the following # These are the individual collections that make up FreeBSD's crypto # collection. They are no longer export-restricted and are a part of # src-all #src-crypto #src-eBones #src-secure #src-sys-crypto The important one is src-sys-crypto and if you are not using src-all, you have to include it. Kent I don't know where the log.h is searched for. A find showed me three diffent ones /usr/src/contrib/ntp/libntp/log.h /usr/src/contrib/nvi/common/log.h /usr/src/usr.sbin/ppp/log.h I think there must something fundamental be missing due to the great gap between 4.4 and 4.6 Release. Can anybody give me a hint what to do? Thanks for help Ulrich 8-- === libpam/modules/pam_ssh rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:69: log.h: No such file or directory In file included from /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:70: /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.h:31: warning: `SSH_CLIENT_IDENTITY' redefined /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/ssh.h:105: warning: this is the location of the previous definition /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.h:32: warning: `SSH_CLIENT_ID_DSA' redefined /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/ssh.h:106: warning: this is the location of the previous definition mkdep: compile failed *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_ssh. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 8-- *default host=cvsup.de.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_4_6_0_RELEASE *default delete use-rel-suffix src-base src-bin src-contrib src-etc src-games src-gnu src-include src-kerberosIV src-kerberos5 src-lib src-libexec src-release src-sbin src-share src-sys src-tools src-usrbin src-usrsbin *default tag=. ports-all doc-all -- Ulrich Drolshagen [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message . -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
ATA tags bug fix committed to -releng4
I've just committed a fix for the tags problem, so please those that had this problem, test it out and let me know... This fix might also help the ATAPI READ_BIG timeout problem, so again please let me know... (I'm not on this list so please CC [EMAIL PROTECTED] on replies) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
