Re: snd_ich and syntax error
JoaoBR wrote: On Tuesday 29 November 2005 11:53, Marco Calviani wrote: Hi list, i have a problem during the config(8) phase of a kernel configuration file. I would like to add in the kernel the device snd_ich with (as indicated in the handbook): device snd_ich However i've got a Syntax Error on that line when i try to config it. Put quotation marks around the driver name: device snd_ich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubles with apcupsd (basic setup)
Dan O'Connor wrote: My config file: UPSNAME APC_BACKUPS_650 UPSCABLE 940-0020B UPSTYPE dumb DEVICE /dev/cuaa0 LOCKFILE /var/spool/lock ONBATTERYDELAY 10 BATTERYLEVEL 20 MINUTES 5 TIMEOUT 600 Nope. Same thing. Well, first off, try setting UPSTYPE to apcsmart then just set UPSCABLE to smart... To the OP: Is it a BACKUPS __PRO__ 650 or just a BACKUPS 650? If it's the latter then the dumb UPSTYPE should be correct. I have two boxes running this model with apcupsd without issue. Incidentally, based on your original description it almost sounds like your battery is dead (or very low charge) which would explain why apcupsd wants to shutdown immediately. Try running the ups without load for a few hours to see. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MX freebsd
Glenn Dawson wrote: At 04:53 PM 11/25/2005, Beecher Rintoul wrote: On Friday 25 November 2005 03:43 pm, Francisco Reyes wrote: dick hoogendijk writes: Any idea how long it takes until the MX freebsd mailservers know that my mail relay has changed? It's three days ago now that I changed my MX records and still mail for nagual.st is routed to my old mx mailservers. dig nagual.st mx ;;; QUESTION SECTION: ;nagual.st. IN MX ;; ANSWER SECTION: nagual.st. 86400 IN MX 10 mx1.mailhop.org. nagual.st. 86400 IN MX 20 mx2.mailhop.org. bc 86400/3600 24 Should only take a day based on the results above. The command to see your XM settings is dig url mx Did you update the serial number when you changed the MX record? Servers downline will not see the changes otherwise. Actually, the serial number is only used by the slave servers for a particular zone to decide whether or not a zone transfer is needed. I don't think that's entirely true. The serial number is also used by named internally to determine whether to reload your zones, and hence, to make the actual change in memory. AFAIK if you don't update the serial number the change won't take effect. To confirm this I just ran `rndc reload` and then checked /var/log/messages on my closest available OBSD name server. Reloaded named.conf but NOT my zone files. Then I changed the serial on one of my primary zone files and ran `rndc reload` again. This time syslog records that both named.conf and that zone have been reloaded. Of course, the serial number change ALSO signals to slaves that they need to update their copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MX freebsd
Glenn Dawson wrote: At 09:58 AM 11/26/2005, Greg Maruszeczka wrote: Glenn Dawson wrote: At 04:53 PM 11/25/2005, Beecher Rintoul wrote: On Friday 25 November 2005 03:43 pm, Francisco Reyes wrote: dick hoogendijk writes: Any idea how long it takes until the MX freebsd mailservers know that my mail relay has changed? It's three days ago now that I changed my MX records and still mail for nagual.st is routed to my old mx mailservers. dig nagual.st mx ;;; QUESTION SECTION: ;nagual.st. IN MX ;; ANSWER SECTION: nagual.st. 86400 IN MX 10 mx1.mailhop.org. nagual.st. 86400 IN MX 20 mx2.mailhop.org. bc 86400/3600 24 Should only take a day based on the results above. The command to see your XM settings is dig url mx Did you update the serial number when you changed the MX record? Servers downline will not see the changes otherwise. Actually, the serial number is only used by the slave servers for a particular zone to decide whether or not a zone transfer is needed. I don't think that's entirely true. The serial number is also used by named internally to determine whether to reload your zones, and hence, to make the actual change in memory. AFAIK if you don't update the serial number the change won't take effect. To confirm this I just ran `rndc reload` and then checked /var/log/messages on my closest available OBSD name server. Reloaded named.conf but NOT my zone files. Then I changed the serial on one of my primary zone files and ran `rndc reload` again. This time syslog records that both named.conf and that zone have been reloaded. Did you actually make a change to one of the zone files? or did you just look at logs? If you make a change to one of the zone files without changing the serial number, and then do rndc reload, the changes will be reflected in queries sent to that named process. To quote the fourth edition of DNS and BIND page 432: When you reload the primary, it loads the updated zone file regardless of whether you've changed the serial number. I stand corrected. Thanks for the clarification and reference. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubles with apcupsd (basic setup)
Peter wrote: Hello. I have an APC BackUPS 650 and I want to have my FreeBSD 5.4 system shutdown on power failure. I received a cable with the unit but there are no identifying markings. When I run apcupsd it thinks there is a power failure and proceeds to shut me down. Can anyone help? My config file: UPSNAME APC_BACKUPS_650 UPSCABLE 940-0020B UPSTYPE dumb DEVICE /dev/cuaa0 LOCKFILE /var/spool/lock ONBATTERYDELAY 10 BATTERYLEVEL 20 MINUTES 5 TIMEOUT 600 Try this cable: 940-0020C hope that helps you, G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: MailScanner / SMTP Auth
Sasa Stupar wrote:
--On 14. november 2005 10:15 +0100 Martin Schweizer
[EMAIL PROTECTED] wrote:
Sorry, forgot to attache the sendmail.mc
Hello
Until now I run sendmail, mailscanner and cyrus-imapd without any
problems. Now I want to update sendmail with SMTP Auth. I updated my
sendmail.mc like described in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html.
But after this all new mails only delivered local to root (no more to
cyrus). Below attached is my sendmail.mc. Is there anybody how has the
same setup? Are there any pitfalls?
My system: FreeBSD 5.4, sendmail 8.13.3, cyrus IMAP4 2.2.12
Any hints are welcome.
divert(-1)
#
# Copyright (c) 1983 Eric P. Allman
# Copyright (c) 1988, 1993
#The Regents of the University of California. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
# 3. All advertising materials mentioning features or use of this
software
#must display the following acknowledgement:
#This product includes software developed by the University of
#California, Berkeley and its contributors.
# 4. Neither the name of the University nor the names of its contributors
#may be used to endorse or promote products derived from this
software
#without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
# THE POSSIBILITY OF SUCH DAMAGE.
#
#
# This is a generic configuration file for FreeBSD 5.X and later
systems.
# If you want to customize it, copy it to a name appropriate for your
# environment and do the modifications there.
#
# The best documentation for this .mc file is:
# /usr/share/sendmail/cf/README or
# /usr/src/contrib/sendmail/cf/README
#
divert(0)
VERSIONID(`$FreeBSD: src/etc/sendmail/freebsd.mc,v 1.29 2003/12/24
21:15:09 gshapiro Exp $') OSTYPE(freebsd5)
DOMAIN(generic)
FEATURE(access_db, `hash -o -TTMPF /etc/mail/access')
FEATURE(blacklist_recipients)
FEATURE(local_lmtp)
FEATURE(mailertable, `hash -o /etc/mail/mailertable')
FEATURE(virtusertable, `hash -o /etc/mail/virtusertable')
dnl Uncomment to allow relaying based on your MX records.
dnl NOTE: This can allow sites to use your server as a backup MX without
dnl your permission.
dnl FEATURE(relay_based_on_MX)
dnl DNS based black hole lists
dnl
dnl DNS based black hole lists come and go on a regular basis
dnl so this file will not serve as a database of the available servers.
dnl For that, visit
dnl
http://directory.google.com/Top/Computers/Internet/Abuse/Spam/Blacklists/
dnl Uncomment to activate Realtime Blackhole List
dnl information available at http://www.mail-abuse.com/
dnl NOTE: This is a subscription service as of July 31, 2001
dnl FEATURE(dnsbl)
dnl Alternatively, you can provide your own server and rejection message:
dnl FEATURE(dnsbl, `blackholes.mail-abuse.org', `550 Mail from
${client_addr} rejected, see http://mail-abuse.org/cgi-bin/lookup?;
${client_addr}') FEATURE(dnsbl, `relays.ordb.org', `550 Mail rejected -
see http://www.ordb.org/faq;') FEATURE(dnsbl, `sbl.spamhaus.org', `550
Mail rejected - see http://www.spamhaus.org/SBL;')
dnl Dialup users should uncomment and define this appropriately
define(`SMART_HOST', `[195.186.18.142]')
dnl Uncomment the first line to change the location of the default
dnl /etc/mail/local-host-names and comment out the second line.
dnl define(`confCW_FILE', `-o /etc/mail/sendmail.cw')
define(`confCW_FILE', `-o /etc/mail/local-host-names')
dnl Enable for both IPv4 and IPv6 (optional)
DAEMON_OPTIONS(`Name=IPv4, Family=inet')
DAEMON_OPTIONS(`Name=IPv6, Family=inet6, Modifiers=O')
dnl set SASL options
TRUST_AUTH_MECH(`GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl
define(`confAUTH_MECHANISMS', `GSSAPI DIGEST-MD5 CRAM-MD5
Re: ipw and 6.0-RELEASE
Luk van den Borne wrote: You should delete /var/db/ports/ipw-firmware/options and run make install clean again. This time, do not select the build with kernel modules option. (Or just set it to false in the options file and recompile). I had the same problem the other day and simply ended up fetching the package manually from the FBSD ftp archives and: pkg_add ipw_firmware.tgz Works just fine on my laptop. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What have you done
come on do you want me to go to red hat. Can't speak for anyone else here but... yes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Configuring default 6.0 install to send mail
Brooke Landers wrote: Hello list. I am learning FreeBSD and I'd like to know how to configure Sendmail to simply forward mail although it seems it's doing this by default. I can send mail, but it's being rejected since mylocalhost.mydomain.com doesn't resolve. I'm using internal hosts that will never have DNS entries. I'm looking for somewhere where I can specify that [EMAIL PROTECTED] can send mail as [EMAIL PROTECTED] I'm pretty sure that my mail would be accepted if I can do this. I don't want to set up a mail server, I'd just like to know how I can get my logs and admin mail forwarded to an external address. I apologize for not sending this to a sendmail list, but I figured there may be something simple and specific to FreeBSD that I have overlooked. Thank you for any help :) BL If that's all you want to do the simplest thing is this (as root): cd /etc/mail vi aliases Look for the entry for root: uncomment it and add whatever external address you want after the colon. After saving and exiting: newaliases Now all system mail should be sent to the external address you specified in /etc/mail/aliases. Test it by doing this: mail -s Test root ctrl-d G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Configuring default 6.0 install to send mail
Brooke Landers wrote: Hello list. I am learning FreeBSD and I'd like to know how to configure Sendmail to simply forward mail although it seems it's doing this by default. I can send mail, but it's being rejected since mylocalhost.mydomain.com doesn't resolve. I'm using internal hosts that will never have DNS entries. I'm looking for somewhere where I can specify that [EMAIL PROTECTED] can send mail as [EMAIL PROTECTED] I'm pretty sure that my mail would be accepted if I can do this. I don't want to set up a mail server, I'd just like to know how I can get my logs and admin mail forwarded to an external address. I apologize for not sending this to a sendmail list, but I figured there may be something simple and specific to FreeBSD that I have overlooked. Uh, sorry for the noise on that last reply, everybody. I should have read more carefully BEFORE hitting send... Brooke, can you post what's output to your /var/log/maillog after you try to send from that box? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendmail/postfix ports question
Matt Singerman wrote: Hello all, I have a server running FreeBSD 5.2.1 that provides (amongst other things) MTA services to our office via sendmail. For a variety of a reasons, I would like to move away from sendmail to postfix. However, the postfix package cannot, as I am sure you know, simply install with sendmail on the system, since they install files to the same places. I am assuming that I have to delete the sendmail package off the system before I can install postfix (someone please correct me if this assumption is wrong). My question is, is there a way to safely and accurately save my sendmail configuration in the event that postfix simply does not work out? I would really prefer not to have to face a situation where I am left high and dry with no MTA working :) The ports version of postfix by default installs all its configuration files under /usr/local/ports/postfix so it leaves your /etc/mail alone (with the exception of mailer.conf) so your sendmail config should be safe -- though it never hurts to tar it up and cp someplace else just in case. You DO NOT need to remove sendmail from the system, though, if you desire, you can exclude it from the `make world` process by adding NO_SENDMAIL=yes to /etc/make.conf. A couple of things to watch for: 1. You will have another aliases file under the new postfix directory so you'll want to remember this if you use the aliases file much. You can just ignore the new one and continue to use the one in /etc/mail or you can do what I did and instruct postfix through its main.cfg to take the postfix-directory version as gospel since this seemed convenient for me to keep the bulk of my config stuff in the postfix directory. 2. Like David said in his reply to you, make sure you read the post-install messages once you build/install postfix so that you can modify your mailer.conf appropriately to use postfix instead of the core sendmail. The /etc/mail/mailer.conf file is the key to the seamless transition here. Also, be careful with mergemaster when you do the next `make world` so that you don't inadvertently overwrite your postfix-modified one with the base sendmail one (done that myself once or twice :) ) Hope that helps, G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with compiling sendmail+sasl (QUIT FBSD)
Sasa Stupar wrote: After two three days of trying unsuccesfully to configure sendmail with sasl I have decided to quit on FreeBSD and go back to linux. Yes, go back to Fedora or whatever. When you can follow directions and the good advice given to you, come back and learn something. Anything you'd like to add to that, Ted? :) G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with compiling sendmail+sasl
Sasa Stupar wrote: Hi! I am new to FreeBSD just migrated from linux. I have installed version 5.4 and ports collection via cvsup. Then I have used ports for cyrus22 to build Cyrus and also sasl2. Now I am trying to build sendmail 8.13.5 but it doesn't build with sasl support. In my make.conf I have added: SENDMAIL_CFLAGS+= -I/usr/local/include -DSASL=2 SENDMAIL_LDFLAGS+= -L/usr/local/lib SENDMAIL_LDADD+= -lsasl2 And then run make and make install under /usr/ports/mail/sendmail. But when I check with : -- mig29# telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost.workgroup. Escape character is '^]'. 220 xmail.homelinux.net ESMTP Sendmail 8.13.3/8.13.5; Wed, 28 Sep 2005 14:15:32 +0200 (CEST) ehlo localhost 250-xmail.homelinux.net Hello localhost.workgroup [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE 10480760 250-DSN 250-DELIVERBY 250 HELP -- I don't have smtp auth. Moreover, I found out that it didn't built with SASL with: -- mig29# sendmail -bt -d0.1 Version 8.13.3 Compiled with: DNSMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS PIPELINING SCANF STARTTLS TCPWRAPPERS USERDB XDEBUG Warning: Option: AuthMechanisms requires SASL support (-DSASL) Warning: Option: AuthOptions requires SASL support (-DSASL) SYSTEM IDENTITY (after readcf) (short domain name) $w = mig29 (canonical domain name) $j = xmail.homelinux.net (subdomain name) $m = workgroup (node name) $k = mig29.workgroup ADDRESS TEST MODE (ruleset 3 NOT automatically invoked) -- What am I doing wrong here? I think you might be getting the BASE sendmail mixed up with the PORT sendmail. For max flexibility, there are TWO separate versions of sendmail available. Unless you know you need the version provided in the ports you should stick with the one provided in the base. Your sendmail-related make.conf syntax looks correct but what you need to do is rebuild the BASE sendmail with sasl support under /usr/src NOT /usr/ports. I suggest you remove/deinstall the sendmail version found under /usr/ports and do a full `make world` as recommended in the handbook. Others may be able to give you specific directions on rebuilding ONLY the base sendmail if a full make world is undesirable. cheers, G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with compiling sendmail+sasl
big snip But I have nothing under /usr/src. I have installed minimum of FreeBSD. But you originally said you cvsup'ed to get 5.4 which means you should have downloaded the source tree for the entire release as well as the ports. Unless you meant to say that you ONLY cvsup'd the ports tree. Can you show us the contents of your cvsupfile? (or at least the commandline args you used to cvsup if you're not reading from a config file for this purpose) For reference, I use a single global config file to get the source tree (userland + kernel) and ports tree (plus docs) in one pass. This is what my /etc/cvsupfile contains: *defaulthost=cvsup11.FreeBSD.org *defaultbase=/usr *defaultprefix=/usr *defaultrelease=cvs *defaulttag=RELENG_5_4 *defaultdelete use-rel-suffix src-all *defaulttag=. doc-all ports-all Then, I just type this at the shell (I use bash) before putting it into a cronjob once I know it works: cvsup -g -L 2 /etc/cvsupfile portsdb -uF As an alternative to my earlier suggestion regarding sendmail, I believe you could also disable the base sendmail and use the ports sendmail instead but that seems like more work to me. I don't offhand know what you'd additionally have to supply in /etc/make.conf and/or the make args for the ports build in order to do this properly. If you're set on doing it this way, maybe check the archives and/or post a new question specific to this (ie. replacing base sendmail with sendmail from ports) Otherwise, just check that you've got the right syntax for cvsup and get the source for the release you want. You'll likely need/want it later for doing updates anyway. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rm -rf ?
Ansar Mohammed wrote: Ok I am logged in as root, yet I cant delete /var/empty ( I get operation not permitted). Any suggestions? man chflags In particular, check for the immutable flag and how to change it. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Information on designing program
Bonny Fourie wrote: Good day I am running on FreeBSD 5.2 currently and I am looking for a designing program. I have Gimp but it doesn't include everything I want. What I want to do is design a few brochures, business cards and so on, I am also working with a scanner. I am looking for a few ideas. Thanks for your time Bonny Fourie Check out /usr/ports/print/scribus New version just out a couple of days ago. Enjoy! G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel PRO/100 VE Network Connection NIC undetected, FreeBSD 5.4
Andrew Robinson wrote: Dear list, I am using an Intel PRO/100 VE Network Connection with FreeBSD 5.4 Release. The card does not seem to be detected. The page at http://www.freebsd.org/releases/5.4R/hardware-i386.html#ETHERNET lists it among the cards that should be supported by fxp. My kernel shows that fxp is included: devicefxp # Intel EtherExpress PRO/100B (82557, 82558) The relevant output of dmesg is: pci5: network, ethernet at device 8.0 (no driver attached) ifconfig says: lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 The relevant output of pciconf -lv is: [EMAIL PROTECTED]:8:0:class=0x02 card=0x01a71028 chip=0x27dc8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class= network subclass = ethernet In WinXP the physical device is identified as Intel 82562 ET 100 Base-TX PHY Does anyone have any suggestions? By coincidence I just installed 5.4 REL on my Gateway notebook this afternoon, which has the Intel PRO 100 on-board. In my case it was detected immediately and coupled with the fxp driver enabled in GENERIC. FWIW the output of pciconf -lv on my notebook yields this: [EMAIL PROTECTED]:8:0 class=0x2 card=0x0200107b chip=0x103d8086 rev=0x81 hdr=0x00 vendor = 'Intel Corporation device = '82801DB (ICH4) PRO/100 VE Network Connection' class = network subclass = ethernet I don't know enough about these numbers to say for sure but obviously your output and mine are quite different, particularly WRT card and chip. Are you absolutely sure you have this particular adapter and not some variant? G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: chrooting SSH users into their home directories
Brian Kaczynski wrote: I was wondering how you could lock a user into their home with chroot when using SSH, similar to what the /etc/ftpchroot file does for FTP users. The ssh server is sshd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Check out 'scponly' -- it's in the ports collection. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[OT Re: SPAM Problem]
Aaron Siegel wrote: Hello This message is off topic but I was not sure were else I can go to get help with my problem. For the past week I have been receiving messages from various mail servers which have bounced messages I have not sent but have my email address as the originator of the bounced message. I believe there are some SPAMers using my email address on their SPAM. I would really like to avoid changing my domain name. Has anyone experienced this problem? Is there something I can do? It's probably blowback resulting from the activities of worm-infected windows hosts. Someone you correspond with got infected and the worm subsequently propagated itself by picking your name from their address book and inserting it into the from: header of the message carrying the worm. Then, badly configured MTAs send helpful NDRs to the sender informing them that they're messages couldn't be delivered Pretty routine, really. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Perl + apache problem
Jack Raats wrote: I've a little question. After upgrading perl to 5.8.7. I'm getting an error of Apache. It says Syntax error on line 239 of /usr/local/etc/apache/httpd.conf: Cannot load /usr/local/libexec/apache/libperl.so into server: Shared object libperl.so not found, required by libperl.so After the upgrade I ran the perl-after-upgrade script. Do you have any clues? How did you run the script? Did you use the -f option as specified on the manpage? Please provide output from `perl-after-upgrade`. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Remote server warnings
Jonathan Arnold wrote: I'm going to be moving my server to a remote site, where I'll only be able to ssh to it for any kind of service. It has been local, hooked up via a KVM switch, so it will be a new setup for me. What sorts of problems should I keep an eye out for? What kind of setup should I have? I've turned on ssh. What else should I do? How hard will it be to update my system remotely? Thanks in advance for any help you can provide. Use rsa/dsa keys and disable password auth in sshd_config. You can generally do port upgrades via ssh without issue. Obviously you have to be careful when performing major updates like `make world` where it's usually recommended that you drop to single-user mode before installing world. Some folks claim they do the whole make world dance by remote and just don't reboot or drop to single-user mode. Personally, I'd never do this on a production box but I recall some good discussion on this list a few months ago about this very topic. Check the archives if you're interested. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail keeps dieing on freebsd 5.4 with postfix
Matt Juszczak wrote: Hi all, We had a mail server running with FreeBSD 5.4, about 3,000 accounts, and postfix. Recently, I turned procmail on in postfix (mailbox_command=/usr/procmail) and the machine has been locking up weekly ever since. And when this machines crashes, it crashes hard ... and procmail is always on the screen as the error causer when it happens. Patient: Doctor, my arm hurts when I do this. Doctor: Then stop doing that. Seriously though, you need to provide some more detailed information if you want anyone here to be able to help you. Start with explaining why you decided to change MDAs in the first place since I'm sure I'm not the only one thinking you must be nuts to make such a major change on a production system with a potential 3000-user lynch mob waiting in the wings. What were you using for local delivery before this? Was there a problem with it or were you looking for new features, etc.? I know you all want messages, but I never seem to be here and my co workers reboot the box on me to fix it. Both times; however, we've had to run fsck from single user mode and also refresh the postfix queue. If you're not around to see the console messages how do you know procmail is always the error causer? Perhaps this is conveyed to you by your co-workers but if so, why don't they tell you the complete error message so you can convey it to us? Leaving that aside, however, what about the logs? Certainly /var/log/maillog should provide some clues if the problem is really your MDA (more on this below). Also we'd need to know something about your configuration (i.e. contents of main.cf and master.cf for starters) to help you with a MTA/MDA problem. Does anyone have any ideas why procmail could be causing my system to completely hard lock every other couple of days? I disabled procmail for now and I know (knock on wood) the machine should be fine like it used to be ... but all these hard locks could eventually drive the freebsd box mad, and I wouldn't want to do a reinstall. FWIW this doesn't sound like a software issue (except maybe a massive memory leak(??)) but then again, I'm saying this with very little useful information provided by you. Have you done any basic hardware checks (e.g. memtest, case and cpu cooling, power supply integrity, etc.)? You've stated that these lock-ups occur every week at the beginning of your post then you say later it's every couple of days. Which is it? Also, please try to precisely define locking up and crashes. It's unclear to me based on your description and the (possibly misleading) subject line what portions of the system are affected. Precision matters IMHO. Cheers, G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
