sendmail && SMTP AUTH: question about /etc/mail/auth/client-info file
Matthias Apitz writes: > Hello, > > Because I was forced by my ISP to do so, I have configured successfully > as described in the FBSD docs the sendmail with SMTP AUTH; > > one question remains: the required file /etc/mail/auth/client-info has > the line: > > AuthInfo:smtp.1blu.de "U:root" "I:Y" "P:X" > > where the I: value is the userID given by the ISP and P: its password; > what does the U: value is good for exactly? thanks in advance Hi Matthias, U = user for details see http://www.sendmail.org/~ca/email/auth.html atb Glyn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Any delivery block to freebsd-questions list?
El día Friday, January 08, 2010 a las 06:57:04AM +0100, Matthias Apitz escribió: > > Sounds like that's just graylisting. The delay will depend on how long > > it takes your MTA (or the smarthost you use) to retry the message. > > In my case it seems not to be graylisting, but blacklisting; i.e. the > mail is not delivered at all :-( Now, with the above reply, the mail of yesterday showed up in the list as well... what is this? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
sendmail && SMTP AUTH: question about /etc/mail/auth/client-info file
Hello, Because I was forced by my ISP to do so, I have configured successfully as described in the FBSD docs the sendmail with SMTP AUTH; one question remains: the required file /etc/mail/auth/client-info has the line: AuthInfo:smtp.1blu.de "U:root" "I:Y" "P:X" where the I: value is the userID given by the ISP and P: its password; what does the U: value is good for exactly? thanks in advance matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Any delivery block to freebsd-questions list?
El día Thursday, January 07, 2010 a las 03:58:08PM -0500, Lowell Gilbert escribió: > > On 1/7/2010 2:18 PM, Matthias Apitz wrote: > >> > >> Hello, > >> > >> I have sent some hours ago a mail to freebsd-questions > >> which went out fine to the MX of my ISP (as I can see in > >> /var/log/maillog) but does not show up in the list and not > >> in the Archives. The Subject: was about sendmail and SMTP AUTH. > >> > >> I have changed the ISP today morning for outbound mail and it > >> may happen that this could be the cause, even if mails to > >> other recipients are working fine... > >> > >> Is there some kind of anti-SPAM protection for freebsd-questions > >> based on the IP of the SMTP origin? To whom I could contact? > >> > >> Thanks in advance > >> > >> matthias > > ... > > Sounds like that's just graylisting. The delay will depend on how long > it takes your MTA (or the smarthost you use) to retry the message. In my case it seems not to be graylisting, but blacklisting; i.e. the mail is not delivered at all :-( matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Failed to Load Kernel
On 1/7/2010 7:26 PM, Kevin Kinsey wrote: > Hmm, having two optical drives might rise up and bite one's tushy; > It could be that you're booting from a drive in BIOS that gets > reassigned by the kernel to be "number two", and the kernel's > attempting to find it one "number one". NO idea for certain, but > such things have happened in the past, I think. > > You might trying disconnecting one optical drive and trying > again. > > Kevin Kinsey > Did so, same exact error. -- PIT signature.asc Description: OpenPGP digital signature
Re: Failed to Load Kernel
Programmer In Training wrote: On 1/6/2010 5:07 PM, Programmer In Training wrote: After testing out the boot disk on my mom's laptop, I have determined there is an error somewhere with my computer. I don't know what it is or where to even begin to look to fix it, but my computer is toast. BIOS: Phoenix - AwardBIOS Attached Hardware: Sound Blaster Live! Generic USB expansion PCI Card Pentium IV 2.4GHz 2GB RAM HP DVD Writer 1040r NEC CD-RW NR-9100A 6GB WD WD64AA ATI Radeon 9200 (AGP) ZoneNet 10/100 Wireless NIC LinkSys 10/100 wired NIC Monitor: CTX LCD No floppy disk drive (none hooked up anyway) ZIP100 internal drive (not hooked up to anything) None of the attached hardware I saw specifically listed as being compatible, but none of it listed as incompatible, either. The two optical drives are known to work (obviously if I can get so far as attempting to load the kernel). The only thing I can think of is the hard drive (unknown previous working condition, although claimed to be in good order). Just to test, though, I'm going to swap out the CD-RW for a 52x CD-ROM. I have no other hard drives to test with (my 32GB drive, known to work, is MIA). Hmm, having two optical drives might rise up and bite one's tushy; It could be that you're booting from a drive in BIOS that gets reassigned by the kernel to be "number two", and the kernel's attempting to find it one "number one". NO idea for certain, but such things have happened in the past, I think. You might trying disconnecting one optical drive and trying again. Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
How to get NIC status?
Assuming I have the name of an interface, what's the easiest way programmatically to get the status of the interface? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Setup FTP service on FreeBSD 2.0.5?
On 7/01/2010 2:35 AM, Jerry McAllister wrote: On Wed, Jan 06, 2010 at 06:20:53PM +0800, Paul Shi wrote: Hi Everyone, I am trying to find a way to setup a wireless network with a FreeBSD server machine running FTP service. The release of FreeBSD I intend to use is 2.0.5 but I could not find anything on how to setup FTP service on FreeBSD 2.0.5 in handbook. There are only howto on PPP and SLIP. Does anyone have a handbook on how to enable FTP service on FreeBSD 2.0.5? Millions thanks! I haven't followed your whole thread, but is there a good reason you want to use such an old version of FreeBSD? You would be very seriously better off installing the latest version -- especially if you plan to use the system on the internet. There have been many many security fixes since 2.0.5 was around. It should not be difficult to have access to the latest version in Hong Kong. There may even be a mirror site there. I definitely second this - unless there's an old application that doesn't work any more, it would certainly be easier and more secure to use the 7.2 or 8.0 releases of FreeBSD. After all, Internet or Intranet, it only takes one loathsome, dispicable, contemptible miscreant to find a security hole, and your entire server is toast. There appears to be a mirror site for FreeBSD in Hong Kong at ftp://ftp.hk.freebsd.org/pub/FreeBSD/ Dave. -- David Rawling PD Consulting And Security Mob: +61 412 135 513 Email: d...@pdconsec.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Possible mysql.sock problem | ERROR 2002 (HY000)
jaymax wrote: > > Thanks !!! > Got it resolved after adding > mysql_socket="/usr/tmp/mysql.sock" to the rc.conf file > Removing the /etc/my.cnf file as the aetting were redundant with those > used in the compilation > deinstalling and reinstalling both the server and the client > [snip] The "new" default location for my.cnf as installed by the ports system is now /usr/local/etc, although MySQL will still find it if it is in mysql_dbdir. MySQL startup will skip it if it has world write permissions on it, more specific info is in the docs. I just chmod mine 444 when I'm done with it as it is something I don't change once configured. But if you have two of them the permissions thingy can be the cause of why it skips over and ignores the one you think it should be using. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Can't figure out recursion problem in bash/freebsd
On 8/01/2010 8:47 AM, Bernard T. Higonnet wrote: echo starting in `pwd` for hoo in * do echo $hoo if [ -d "$hoo" ] then echo pushing $hoo; cd $hoo $0 else echo processing $hoo fi; echo going to next item done cd .. I have tried various minor variations , all to no avail. I have no doubt I'm doing something very dumb, but I'm too locked into my vision to see it... All help appreciated Bernard Higonnet I am probably the last person you'd want debugging your scripts, but I can at least reproduce the problem. My test folder and file structure: /tmp/test dir0 dir00 file00 file0 dir1 dir11 file11 file1 Luckily, I think I have also derived the solution. The problem appears to be the directory stack. Specifically, the output of my revised version shows that it's not working in the right folders all the time. #! /bin/sh echo Starting in `pwd` for hoo in *; do echo $hoo if [ -d "$hoo" ]; then echo Pushing $hoo; cd $hoo ($0) else echo Processing file $hoo fi echo Going to next item done cd .. echo Finishing in `pwd` By moving the cd command into the if statement, we change back into the correct folder at the right time (otherwise the siblings to the first directory cannot be found in the for loop, perhaps because the current directory has changed mid-execution): test01# cat /root/recurse.sh #! /bin/sh echo Starting in `pwd` for hoo in *; do echo Found item $hoo if [ -d "$hoo" ]; then echo Pushing $hoo cd $hoo $0 cd .. else echo Processing file $hoo fi echo Going to next item done echo Finishing in `pwd` test01# I think it works - someone brighter than me can tell us both why :). Most of the changes you see there are stylistic (eg the placement of then/else and do/done) or were for my own clarity in figuring out what was being printed where. Dave. -- David Rawling Principal Consultant PD Consulting And Security 7 Virginia Ave Baulkham Hills, NSW 2153 Australia Mob: +61 412 135 513 Email: d...@pdconsec.net Please note that whilst we take all care, neither PD Consulting and Security nor the sender accepts any responsibility for viruses and it is your responsibility to scan for viruses. The contents are intended only for use by the addressee and may contain confidential and/or privileged material and any use by other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: pf headaches: why won' t it let me fetch from ftp servers?
I'm not all that familiar with pf syntax, but you know ftp uses ports above
1023 right? Is pf "stateful" by default so it can allow the ports above 1023?
Also, make sure you're using passive (PASV) ftp.
G
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Dino Vliet
Sent: Thursday, January 07, 2010 3:39 PM
To: freebsd-questions@freebsd.org
Subject: pf headaches: why won' t it let me fetch from ftp servers?
Dear freebsd list,
I have the following pf.conf file:
tcp_services = "{ ftp, ssh, domain, www, auth, https }"
udp_services = "{ ftp, domain, ntp }"
icmp_types = "echoreq"
block all
pass inet proto icmp all icmp-type $icmp_types keep state
#pass in proto tcp to any port 22 keep state
pass out proto tcp to any port $tcp_services keep state
#pass out proto tcp to any port 25 keep state
#pass out proto tcp to any port 465 keep state
#pass out proto tcp to any port 587 keep state
pass out proto tcp to any port 5999 keep state
#pass out all keep state
#pass out proto tcp to any keep state
pass out proto udp to any port $udp_services
However,if I try to fetch a file from a ftp server as in the followining
example:fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/bash/FAQ
I get the result: Operation not permitted
My first question is: What is causing this? If I stop pf, then I' m able to
fetch it.
My second question is:Is my ruleset looking fine, as i want to block everything
and only let some specific services go out. Or need t be tightened more?
BrgdsDino
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
"This email is intended to be reviewed by only the intended recipient
and may contain information that is privileged and/or confidential.
If you are not the intended recipient, you are hereby notified that
any review, use, dissemination, disclosure or copying of this email
and its attachments, if any, is strictly prohibited. If you have
received this email in error, please immediately notify the sender by
return email and delete this email from your system."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pf headaches: why won' t it let me fetch from ftp servers?
On Thu, Jan 7, 2010 at 2:38 PM, Dino Vliet wrote:
> Dear freebsd list,
> I have the following pf.conf file:
> tcp_services = "{ ftp, ssh, domain, www, auth, https }"
> udp_services = "{ ftp, domain, ntp }"
> icmp_types = "echoreq"
> block all
> pass inet proto icmp all icmp-type $icmp_types keep state
> #pass in proto tcp to any port 22 keep state
> pass out proto tcp to any port $tcp_services keep state
> #pass out proto tcp to any port 25 keep state
> #pass out proto tcp to any port 465 keep state
> #pass out proto tcp to any port 587 keep state
> pass out proto tcp to any port 5999 keep state
> #pass out all keep state
> #pass out proto tcp to any keep state
> pass out proto udp to any port $udp_services
>
> However,if I try to fetch a file from a ftp server as in the followining
> example:fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/bash/FAQ
> I get the result: Operation not permitted
> My first question is: What is causing this? If I stop pf, then I' m able to
> fetch it.
> My second question is:Is my ruleset looking fine, as i want to block
> everything and only let some specific services go out. Or need t be tightened
> more?
> BrgdsDino
Dino-
Default behavior for FTP is that you open connection to server on port
20 and then server opens a connection back to you on another port,
basically. This means that when you have the firewall active your
blocking this inbound connection on the alternate port. The easiest
way to work around this and to get the security of having a firewall
running is to use "PASSIVE" mode in your FTP client, which basically
indicates that the client will open a second connection to the server:
$ fetch -p ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/bash/FAQ
There's also an environment variable (FTP_PASSIVE_MODE) that you can
set to default to passive FTP. See fetch(3), but basically set it to
anything besides "no" to set the default.
Cheers,
Ben
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Can't figure out recursion problem in bash/freebsd
Dear freebsd list, There must be something simple I'm getting wrong in attempting a simple recursive bash script. I want to do something on every file in a tree, so I have a script which recurses when it finds a directory and processes the file when it is not a directory. My testbed is a directory with 3 subdirectories and a few files. My script correctly recognizes the first directory encountered, recurses to process that sub-directory, but when it comes back it no longer recognizes the next item as a directory, though it is indeed a directory. In the script given below, the processing of an actual file is represented by "echo processing $hoo". If I eliminate the recursion but enter and then exit the sub-directory (i.e. I replace line "$0" with "cd ..") the sub-directories are correctly recognized. echo starting in `pwd` for hoo in * do echo $hoo if [ -d "$hoo" ] then echo pushing $hoo; cd $hoo $0 else echo processing $hoo fi; echo going to next item done cd .. I have tried various minor variations , all to no avail. I have no doubt I'm doing something very dumb, but I'm too locked into my vision to see it... All help appreciated Bernard Higonnet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
pf headaches: why won' t it let me fetch from ftp servers?
Dear freebsd list,
I have the following pf.conf file:
tcp_services = "{ ftp, ssh, domain, www, auth, https }"
udp_services = "{ ftp, domain, ntp }"
icmp_types = "echoreq"
block all
pass inet proto icmp all icmp-type $icmp_types keep state
#pass in proto tcp to any port 22 keep state
pass out proto tcp to any port $tcp_services keep state
#pass out proto tcp to any port 25 keep state
#pass out proto tcp to any port 465 keep state
#pass out proto tcp to any port 587 keep state
pass out proto tcp to any port 5999 keep state
#pass out all keep state
#pass out proto tcp to any keep state
pass out proto udp to any port $udp_services
However,if I try to fetch a file from a ftp server as in the followining
example:fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/bash/FAQ
I get the result: Operation not permitted
My first question is: What is causing this? If I stop pf, then I' m able to
fetch it.
My second question is:Is my ruleset looking fine, as i want to block everything
and only let some specific services go out. Or need t be tightened more?
BrgdsDino
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Security Hardening: Removing Permissions; Suggestions
APseudoUtopia writes: > Hey list, > > I'm working on a shell script that basically removes the group and the > other permissions from certain files to harden my system. Right now, > the only files I'm doing this on is the GCC compiler collection. I'm > asking for suggestions on other files that these permissions can be > removed from in order to help further secure the system (a headless db > and web server). > > $CHMOD o=,g= /usr/bin/cc > $CHMOD o=,g= /usr/bin/cpp > $CHMOD o=,g= /usr/bin/gcov > $CHMOD o=,g= /usr/bin/ld > $CHMOD o=,g= /usr/bin/gdb > $CHMOD o=,g= /usr/bin/c++ This kind of approach hardly ever makes sense any more. Unless you've got a really good reason, putting the daemons and untrusted users into jails (not even necessarily the same jails) is almost certainly going to give you all the advantages you could get out of blocking off applications one at a time. The jails don't need compilers in the first place. Disabling the compiler is pretty much useless if the web server's users are going to be allowed to copy their own files onto the machine anyway. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Some point out rc.local as a fix, i find it ok to but it has some ups'n'downs indeed in a reboot situation rc.local having the route add command would be ok but in a short network restart it wouldn't count (as i particularly value my uptime)... the ipv6 defaultroute it's not a big issue for me, as i do not depend on it so much, but i find it somewhat important to FreeBSD ... dunno i like to know that a distro is stable in any case (not that i'm complaining FreeBSD) reference: http://www.tunnelbroker.net/forums/index.php?topic=734.0 2010/1/7 Steve Bertrand > Bogdan Webb wrote: > > I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my > > FreeBSD 7.2-RELEASE-p6 > > It`s a particular issue on the ipv6_defaultrouter config, it jost does > not > > work... > > Upon network and routing restart ipv6 is enabled the gif interface are > given > > ip's and everything but the defaultrouter does not. > > Researching a bit i found some say that gif1 sould work and tried both > > ipv6_defaultrouter="-interface gif1" > > and > > ipv6_defaultrouter="2001:0470:1f0a:d40::1" > > This issue is not limited to gif interfaces... > > I've had this exact same problem on ALL of my FreeBSD hosts for, well, > since ever. > > No matter what I've tried, if a box reboots, I must manually enter in > the default IPv6 router. > > Even on IPv6-only hosts, the default gateway does not take upon reboot. > > I'm up for figuring this issue out today, if nobody else has a solution > for you. > > Let me know. If you're interested, I'll fire up a couple of hosts that > we can use and just continuously reboot if necessary :) > > Steve > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Any delivery block to freebsd-questions list?
Programmer In Training writes: > On 1/7/2010 2:18 PM, Matthias Apitz wrote: >> >> Hello, >> >> I have sent some hours ago a mail to freebsd-questions >> which went out fine to the MX of my ISP (as I can see in >> /var/log/maillog) but does not show up in the list and not >> in the Archives. The Subject: was about sendmail and SMTP AUTH. >> >> I have changed the ISP today morning for outbound mail and it >> may happen that this could be the cause, even if mails to >> other recipients are working fine... >> >> Is there some kind of anti-SPAM protection for freebsd-questions >> based on the IP of the SMTP origin? To whom I could contact? >> >> Thanks in advance >> >> matthias > > I too have a similar problem with my emails. They take about 30-45 > minutes to be posted to the list. According to Thunderbird the mail is > sent (at least to my mail server @ Bluehost), and the time-stamp on the > message reads as the time I sent it. Didn't think anyone else was having > this problem. Sounds like that's just graylisting. The delay will depend on how long it takes your MTA (or the smarthost you use) to retry the message. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Any delivery block to freebsd-questions list?
On 1/7/2010 2:36 PM, Programmer In Training wrote: > I too have a similar problem with my emails. They take about 30-45 > minutes to be posted to the list. According to Thunderbird the mail is > sent (at least to my mail server @ Bluehost), and the time-stamp on the > message reads as the time I sent it. Didn't think anyone else was having > this problem. > I should note this only happens when I'm posting a new message to the list. Replies go straight through. -- PIT signature.asc Description: OpenPGP digital signature
Re: Any delivery block to freebsd-questions list?
On 1/7/2010 2:18 PM, Matthias Apitz wrote: > > Hello, > > I have sent some hours ago a mail to freebsd-questions > which went out fine to the MX of my ISP (as I can see in > /var/log/maillog) but does not show up in the list and not > in the Archives. The Subject: was about sendmail and SMTP AUTH. > > I have changed the ISP today morning for outbound mail and it > may happen that this could be the cause, even if mails to > other recipients are working fine... > > Is there some kind of anti-SPAM protection for freebsd-questions > based on the IP of the SMTP origin? To whom I could contact? > > Thanks in advance > > matthias I too have a similar problem with my emails. They take about 30-45 minutes to be posted to the list. According to Thunderbird the mail is sent (at least to my mail server @ Bluehost), and the time-stamp on the message reads as the time I sent it. Didn't think anyone else was having this problem. -- PIT signature.asc Description: OpenPGP digital signature
Any delivery block to freebsd-questions list?
Hello, I have sent some hours ago a mail to freebsd-questions which went out fine to the MX of my ISP (as I can see in /var/log/maillog) but does not show up in the list and not in the Archives. The Subject: was about sendmail and SMTP AUTH. I have changed the ISP today morning for outbound mail and it may happen that this could be the cause, even if mails to other recipients are working fine... Is there some kind of anti-SPAM protection for freebsd-questions based on the IP of the SMTP origin? To whom I could contact? Thanks in advance matthias -- Matthias Apitz - http://www.UnixArea.de/ - http://gurucubano.blogspot.com/ «...una sola vez, que es cuanto basta si se trata de verdades definitivas.» «...only once, which is enough if it has todo with definite truth.» José Saramago, Historia del Cerco de Lisboa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Possible mysql.sock problem | ERROR 2002 (HY000)
Thanks !!!
Got it resolved after adding
mysql_socket="/usr/tmp/mysql.sock" to the rc.conf file
Removing the /etc/my.cnf file as the aetting were redundant with those used
in the compilation
deinstalling and reinstalling both the server and the client
Matthew Seaman-2 wrote:
>
> jaymax wrote:
>
>> Direct start from script /usr/local/etc/rc.d/mysql-server start fails
>> also
>>
>> And running /usr/local/bin/mysql ==>
>> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
>> '/usr/tmp/mysql.sock' (2)
>>
>
> There's a $mysql_socket rc.conf variable you need to set as well.
>
>> Settings in rc.conf
>> mysql_enable="YES"
>> mysql_limits="YES"
>> mysql_dbdir="/disk02/db/mysql/DATA"
>> mysql_args=""
> mysql_socket="/usr/tmp/mysql.sock"
>
> (Although if /usr/tmp is set to mode 1777, what's the benefit of using
> that
> location rather than the default /tmp/mysql.sock ?)
>
> Initially they were on their own file systems both ran into problems of
> restricted sizes and overflow condition.
>
>
> Judging by the complaints about 'update log no longer supported' I'm
> guessing that there is somewhere a my.cnf or a .my.cnf file filled with
> configuration settings appropriate to a much earlier version of MySQL.
> A good strategy is to grab one of the sample .cnf files from
> /usr/local/share/mysql (according to the capabilities of your server)
> copy that into ${mysql_dbdir}/my.cnf and edit to make any local
> customizations.
>
> Aparently ignored after
>
--
View this message in context:
http://old.nabble.com/Possible-mysql.sock-problem-%7C-ERROR-2002-%28HY000%29-tp27001411p27066296.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Security Hardening: Removing Permissions; Suggestions
Hey list, I'm working on a shell script that basically removes the group and the other permissions from certain files to harden my system. Right now, the only files I'm doing this on is the GCC compiler collection. I'm asking for suggestions on other files that these permissions can be removed from in order to help further secure the system (a headless db and web server). $CHMOD o=,g= /usr/bin/cc $CHMOD o=,g= /usr/bin/cpp $CHMOD o=,g= /usr/bin/gcov $CHMOD o=,g= /usr/bin/ld $CHMOD o=,g= /usr/bin/gdb $CHMOD o=,g= /usr/bin/c++ Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ports/devel/protobuf: Segmentation fault in mmap in some applications
On Thursday 07 January 2010 10:02:36 O. Hartmann wrote:
> On 01/07/10 01:41, Pieter de Goeje wrote:
> > On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
> >> Dear Sirs,
> >> We use a software package for scientific imagery processing from USGS,
> >> ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
> >> 3.1.21 and since this version, the software intensively uses
> >> libprotobuf.so.
> >>
> >> While we can use ISIS 3.1.20 very well under FreeBSD 8.0/amd64, it is
> >> impossible to use the software with version no. 3.1.21, which seems to
> >> have some issues wih libprotobuf.so. Every client out of this ISIS3
> >> package crashes with a segmentation fault and as far as I can judge the
> >> situation, there is a problem with libprotobuf.so, against which all
> >> clients out of ISIS 3.1.21 are linked.
> >
> > Perhaps the ISIS package was developed using a different (older?) version
> > of Google's protocol buffers. Compiling protobuf from source is quite
> > easy on FreeBSD. You can find the source here:
> > http://code.google.com/p/protobuf/downloads/list
> > I would start by trying version 2.1.0 and 2.2.0a.
> >
> >> I searched for help on the ISIS3-support forum and realised that some
> >> Apple OS X guys have had similar problems, but those threads where
> >> closed immediately or got relative senseless response.
> >>
> >> In our case, we compile every necessary library and prerequisite
> >> software package (mostly Qt4 libs) from ports. This works great with
> >> some tweaks for FreeBSD in make/config.freebsd (which I derived from
> >> some linux and/or OS X config files).
> >>
> >> Now I'm floating like a dead man i the water. Below I provide q gdb
> >> output of the qview-client (the same is with all other clients, like
> >> photrim etc. for those familiar with the software package).
> >
> > A backtrace ('bt' at the gdb prompt) might contain more useful
> > information.
> >
> >> Additionaly, I provide a truss-output, that stops at mmap issues.
> >>
> >> Well, if someone could provide me with some advance debugging hints I
> >> would appreaciate them. I'm pretty sure he problem is located within the
> >> libprotobuf library or the way it is treated, but this is a guess of a
> >> non-developer.
> >>
> >> Thanks very much in advance.
> >> Please reply also to this email address, since I'm not subscriber of the
> >> list I post to.
> >>
> >> Oliver
> >
> > - Pieter
>
> Hello Pieter,
>
> ISIS3 utilises the very same revision of libprotobuf as FreeBSD has in
> the ports repositorium (libprotobuf.so.4.0.0, aka protobuf-2.2.0). The
> backtrace follows, it is a little bit lengthy ...
Ok, I can reproduce this locally. The cause is incorrect compiler flags.
Basically one must use `pkg-config --cflags protobuf` to get the correct
CFLAGS and `pkg-config --libs protobuf` for the correct libraries.
Most likely one or both of the following were missing during the
compilation/linking of ISIS: -D_THREAD_SAFE -pthread
Regards,
Pieter
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Intel PRO/Wireless 2100 ipw WPA
On Thu, Jan 7, 2010 at 11:44 AM, Andreas Rudisch <"cyb."@gmx.net> wrote: > On Sun, 3 Jan 2010 15:27:55 -0700 (MST) > Warren Block wrote: > > > Finishing a complete new install of 8-stable on a Thinkpad T42. This > > model came with the Intel PRO/wireless 2100. > > > > So far, it has almost but not quite been able to connect using WPA on > > FreeBSD. > > Same here when trying to set up wireless LAN on a T41 with an Intel > PRO/wireless 2100. > > > rc.conf: > > wlans_ipw0="wlan0" > > ifconfig_wlan0="WPA DHCP" > > > > loader.conf: > > legal.intel_ipw.license_ack=1 > > if_ipw_load="YES" > > That's what I did too. No joy. > > > ifconfig wlan0 scan sees all the nearby access points, including mine. > > Here too. > > > wpa_supplicant can't quite attach, but doesn't give up trying. > > > /var/log/messages: > > Jan 3 14:49:40 paddy wpa_supplicant[392]: CTRL-EVENT-SCAN-RESULTS > > Jan 3 14:49:40 paddy wpa_supplicant[392]: Trying to associate with > 00:14:bf:cd:a2:0b (SSID='myssid' freq=2412 MHz) > > Jan 3 14:49:50 paddy wpa_supplicant[392]: Authentication with > 00:14:bf:cd:a2:0b timed out. > > Appart from that I got the following in /var/log/messages: > kernel: ipw0: need multicast update callback > > Since the same setup worked fine on FreeBSD 7.2, maybe this infomation > regarding ipw is correct after all: > > http://wiki.freebsd.org/8.0TODO#head-637d4dd09847005583f360ebb430cf32b64a4d8b > Yeah I think it was mentioned in one of the beta announcements, but can't seem to find it now. Anyways, my laptop is stuck on 7-STABLE due to this. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Intel PRO/Wireless 2100 ipw WPA
On Sun, 3 Jan 2010 15:27:55 -0700 (MST) Warren Block wrote: > Finishing a complete new install of 8-stable on a Thinkpad T42. This > model came with the Intel PRO/wireless 2100. > > So far, it has almost but not quite been able to connect using WPA on > FreeBSD. Same here when trying to set up wireless LAN on a T41 with an Intel PRO/wireless 2100. > rc.conf: > wlans_ipw0="wlan0" > ifconfig_wlan0="WPA DHCP" > > loader.conf: > legal.intel_ipw.license_ack=1 > if_ipw_load="YES" That's what I did too. No joy. > ifconfig wlan0 scan sees all the nearby access points, including mine. Here too. > wpa_supplicant can't quite attach, but doesn't give up trying. > /var/log/messages: > Jan 3 14:49:40 paddy wpa_supplicant[392]: CTRL-EVENT-SCAN-RESULTS > Jan 3 14:49:40 paddy wpa_supplicant[392]: Trying to associate with > 00:14:bf:cd:a2:0b (SSID='myssid' freq=2412 MHz) > Jan 3 14:49:50 paddy wpa_supplicant[392]: Authentication with > 00:14:bf:cd:a2:0b timed out. Appart from that I got the following in /var/log/messages: kernel: ipw0: need multicast update callback Since the same setup worked fine on FreeBSD 7.2, maybe this infomation regarding ipw is correct after all: http://wiki.freebsd.org/8.0TODO#head-637d4dd09847005583f360ebb430cf32b64a4d8b Andreas -- GnuPG key : 0x2A573565|http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 pgpF3TNzlhYSz.pgp Description: PGP signature
Re: Failed to Load Kernel
On 1/6/2010 5:07 PM, Programmer In Training wrote: > > > After testing out the boot disk on my mom's laptop, I have determined > there is an error somewhere with my computer. I don't know what it is or > where to even begin to look to fix it, but my computer is toast. > BIOS: Phoenix - AwardBIOS Attached Hardware: Sound Blaster Live! Generic USB expansion PCI Card Pentium IV 2.4GHz 2GB RAM HP DVD Writer 1040r NEC CD-RW NR-9100A 6GB WD WD64AA ATI Radeon 9200 (AGP) ZoneNet 10/100 Wireless NIC LinkSys 10/100 wired NIC Monitor: CTX LCD No floppy disk drive (none hooked up anyway) ZIP100 internal drive (not hooked up to anything) None of the attached hardware I saw specifically listed as being compatible, but none of it listed as incompatible, either. The two optical drives are known to work (obviously if I can get so far as attempting to load the kernel). The only thing I can think of is the hard drive (unknown previous working condition, although claimed to be in good order). Just to test, though, I'm going to swap out the CD-RW for a 52x CD-ROM. I have no other hard drives to test with (my 32GB drive, known to work, is MIA). -- PIT signature.asc Description: OpenPGP digital signature
Re: FreeBSD ipv6 rc.conf settings issue
Matthew Seaman wrote: > Steve Bertrand wrote: > >> Hmmm. This config does not work: >> >> ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" >> ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" >> ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" >> ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" > > Yep. Try it like this: > > ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" > ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" > ipv6_ifconfig_re0="2607:f118::b6 prefixlen 64" > ipv6_ifconfig_re0_alias0="2607:f118::b7 prefixlen 64" The above works. > or, even better, like this: > > ipv4_addrs_re0="208.70.104.210/26 208.70.104.211/26" > ipv6_addrs_re0="2607:f118::b6/64 2607:f118::b7/64" Unfortunately, that one does not. I do not get any IPv6 addresses configured. I didn't re-try my original configuration, but I will at another time. Both of your recommendations failed until I entered ipv6_enable="YES" in /etc/rc.conf. I did not have this line prior, yet the addresses were successfully applied, just no default gateway. Either way, thanks much :) I will try out your second recommendation again in the future. For now, problem resolved. Cheers! Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
required apache22 modules
I'm installing Apache22 on a new server and for once, I'd like to install just the modules I need, instead of the default mess. I've been googling for this answer, but can't seem to find it: Are any apache modules *required*? Or can I just disable them all and then add them in as I need them? -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Matthew Seaman wrote: > Steve Bertrand wrote: > >> Hmmm. This config does not work: >> >> ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" >> ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" >> ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" >> ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" > > Yep. Try it like this: > > ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" > ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" > ipv6_ifconfig_re0="2607:f118::b6 prefixlen 64" > ipv6_ifconfig_re0_alias0="2607:f118::b7 prefixlen 64" > > or, even better, like this: > > ipv4_addrs_re0="208.70.104.210/26 208.70.104.211/26" > ipv6_addrs_re0="2607:f118::b6/64 2607:f118::b7/64" > > You can make the 2nd address in each case a /32 or /128 if you want, > but the requirement for having 2nd and subsequent addresses from a > netblock have a different netmask than the initial address on that NIC > has gone away. I thought I read that some time ago... This particular box is my MTA that I use for all of my personal email, so I'll get on the console, input the new settings reboot and let you know how it wor... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Steve Bertrand wrote: Hmmm. This config does not work: ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" Yep. Try it like this: ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" ipv6_ifconfig_re0="2607:f118::b6 prefixlen 64" ipv6_ifconfig_re0_alias0="2607:f118::b7 prefixlen 64" or, even better, like this: ipv4_addrs_re0="208.70.104.210/26 208.70.104.211/26" ipv6_addrs_re0="2607:f118::b6/64 2607:f118::b7/64" You can make the 2nd address in each case a /32 or /128 if you want, but the requirement for having 2nd and subsequent addresses from a netblock have a different netmask than the initial address on that NIC has gone away. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
zpool status hangs zfs command, possibly related to spindown
Greetings,
uname -a (64bit)
8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009
I have a raidz setup with 4x 2TB drives, plus a UFS CF on the IDE
channel I use to boot off of. I have an 1TB ZFS (non-raid) drive in
an attached docking station that I use for nightly backups. Since the
drive in the docking station has no fan on it, and is only used for
about 2 minutes per day, I have a spindown script added to rc.d:
#!/bin/sh
DEV=ad12
case "$1" in
start)
echo "Spindown SATA disk $DEV after idle for 15 minutes."
atacontrol spindown $DEV 900 && dd if=/dev/$DEV of=/dev/null
count=1 2> /dev/null &
;;
stop)
echo "Spindown of SATA disk $DEV disabled."
atacontrol spindown $DEV 0 && dd if=/dev/$DEV of=/dev/null
count=1 2> /dev/null
;;
status)
atacontrol spindown $DEV
;;
*)
echo "Usage: `basename $0` {start|stop|status}" >&2
exit 64
;;
esac
However after running a spindown stop twice within a couple minutes, I
see this in /var/log/messages:
Jan 7 07:36:54 frodo kernel: ad12: request while spun down, starting.
Jan 7 07:36:55 frodo kernel: ad12: timeout waiting to issue command
Jan 7 07:36:55 frodo kernel: ad12: error issuing READ_DMA command
Jan 7 07:38:40 frodo kernel: ad12: timeout waiting to issue command
Jan 7 07:38:40 frodo kernel: ad12: error issuing READ_DMA command
If I issue a 'zpool status storage' command (main raidz) it returns
normally. If I issue 'zpool status' or 'zpool status backup' (backup
is the drive in the docking station), the command hangs. 'zfs list'
also does not return nor do zfs mounting commands associated with the
backup drive.
When I was using 7.x (without ZFS), I was able to use spindown and the
drive would spin up when being used, then shut down after the
requisite inactivity time. Is this no longer recommended, or have I
hit a bug/regression in the ata controller?
I am remote to the machine right now, so I am hesitant to reboot it to
get the spundown drive back up and running. Does anyone know of a way
to kick start a spundown drive so it is mountable (as a short term
fix) and the proper way to spin up/down the drive for 8.x (for a long
term fix).
TIA,
Derrick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Matthew Seaman wrote: > Steve Bertrand wrote: > Funny. My IPv6 config works like a charm, on both 7.2-STABLE and > 8.0-STABLE. Related config settings look like this: > > gif_interfaces="gif0" > gifconfig_gif0="81.187.76.162 81.187.81.6" > > ipv6_ifconfig_gif0="2001:08b0:0151:0001::1/64" > ipv6_prefix_de0="2001:08b0:0151:0001" > > ipv6_enable="YES" > ipv6_defaultrouter="-interface gif0" > ipv6_default_interface="gif0" > ipv6_gateway_enable="YES" > > rtadvd_enable="YES" > rtadvd_interfaces="de0" > > This causes my machine to autoconfigure an IPv6 address on the ethernet > i/f, plus provide rtadvd service to anything else wanting IPv6 connectivity > on my home LAN. IPv6 traffic from the home LAN is routed via the tunnel to > the IPv6 tunnel handler provided by my ISP, but the only reason I need > to do > that is because IPv6 aware consumer broadband routers are kind of hard to > obtain. Hmmm. This config does not work: ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" defaultrouter="208.70.104.193" ipv6_defaultrouter="2607:f118::1" I've got native v6. The above particular box is one of only a couple that have more than a single IP per protocol. The rest are generic, one v4 and one v6 address. Admittedly, I haven't spent much time at all on the issue, as my solution is simply to not let the boxes go down :) % uptime 10:52AM up 727 days, 3:11, 6 users, load averages: 0.19, 0.19, 0.24 %uptime 10:54AM up 549 days, 8:38, 1 user, load averages: 0.12, 0.16, 0.26 ...seriously, all of my other FreeBSD boxes receive proper updates etc, and the only time they are rebooted is when someone is at the console (or right nearby) and can manually enter in the default route. My FreeBSD routers running Quagga don't have this issue, presumably because they're in the DFZ, and acquire all routing info dynamically. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Steve Bertrand wrote: Bogdan Webb wrote: I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my FreeBSD 7.2-RELEASE-p6 It`s a particular issue on the ipv6_defaultrouter config, it jost does not work... Upon network and routing restart ipv6 is enabled the gif interface are given ip's and everything but the defaultrouter does not. Researching a bit i found some say that gif1 sould work and tried both ipv6_defaultrouter="-interface gif1" and ipv6_defaultrouter="2001:0470:1f0a:d40::1" This issue is not limited to gif interfaces... I've had this exact same problem on ALL of my FreeBSD hosts for, well, since ever. No matter what I've tried, if a box reboots, I must manually enter in the default IPv6 router. Even on IPv6-only hosts, the default gateway does not take upon reboot. I'm up for figuring this issue out today, if nobody else has a solution for you. Let me know. If you're interested, I'll fire up a couple of hosts that we can use and just continuously reboot if necessary :) Funny. My IPv6 config works like a charm, on both 7.2-STABLE and 8.0-STABLE. Related config settings look like this: gif_interfaces="gif0" gifconfig_gif0="81.187.76.162 81.187.81.6" ipv6_ifconfig_gif0="2001:08b0:0151:0001::1/64" ipv6_prefix_de0="2001:08b0:0151:0001" ipv6_enable="YES" ipv6_defaultrouter="-interface gif0" ipv6_default_interface="gif0" ipv6_gateway_enable="YES" rtadvd_enable="YES" rtadvd_interfaces="de0" This causes my machine to autoconfigure an IPv6 address on the ethernet i/f, plus provide rtadvd service to anything else wanting IPv6 connectivity on my home LAN. IPv6 traffic from the home LAN is routed via the tunnel to the IPv6 tunnel handler provided by my ISP, but the only reason I need to do that is because IPv6 aware consumer broadband routers are kind of hard to obtain. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD ipv6 rc.conf settings issue
Bogdan Webb wrote: > I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my > FreeBSD 7.2-RELEASE-p6 > It`s a particular issue on the ipv6_defaultrouter config, it jost does not > work... > Upon network and routing restart ipv6 is enabled the gif interface are given > ip's and everything but the defaultrouter does not. > Researching a bit i found some say that gif1 sould work and tried both > ipv6_defaultrouter="-interface gif1" > and > ipv6_defaultrouter="2001:0470:1f0a:d40::1" This issue is not limited to gif interfaces... I've had this exact same problem on ALL of my FreeBSD hosts for, well, since ever. No matter what I've tried, if a box reboots, I must manually enter in the default IPv6 router. Even on IPv6-only hosts, the default gateway does not take upon reboot. I'm up for figuring this issue out today, if nobody else has a solution for you. Let me know. If you're interested, I'll fire up a couple of hosts that we can use and just continuously reboot if necessary :) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ports/devel/protobuf: Segmentation fault in mmap in some applications
On 01/07/10 01:41, Pieter de Goeje wrote:
On Wednesday 06 January 2010 14:14:28 O. Hartmann wrote:
Dear Sirs,
We use a software package for scientific imagery processing from USGS,
ISIS3 (http://isis.astrogeology.usgs.gov/). The most recent version is
3.1.21 and since this version, the software intensively uses
libprotobuf.so.
While we can use ISIS 3.1.20 very well under FreeBSD 8.0/amd64, it is
impossible to use the software with version no. 3.1.21, which seems to
have some issues wih libprotobuf.so. Every client out of this ISIS3
package crashes with a segmentation fault and as far as I can judge the
situation, there is a problem with libprotobuf.so, against which all
clients out of ISIS 3.1.21 are linked.
Perhaps the ISIS package was developed using a different (older?) version of
Google's protocol buffers. Compiling protobuf from source is quite easy on
FreeBSD. You can find the source here:
http://code.google.com/p/protobuf/downloads/list
I would start by trying version 2.1.0 and 2.2.0a.
I searched for help on the ISIS3-support forum and realised that some
Apple OS X guys have had similar problems, but those threads where
closed immediately or got relative senseless response.
In our case, we compile every necessary library and prerequisite
software package (mostly Qt4 libs) from ports. This works great with
some tweaks for FreeBSD in make/config.freebsd (which I derived from
some linux and/or OS X config files).
Now I'm floating like a dead man i the water. Below I provide q gdb
output of the qview-client (the same is with all other clients, like
photrim etc. for those familiar with the software package).
A backtrace ('bt' at the gdb prompt) might contain more useful information.
Additionaly, I provide a truss-output, that stops at mmap issues.
Well, if someone could provide me with some advance debugging hints I
would appreaciate them. I'm pretty sure he problem is located within the
libprotobuf library or the way it is treated, but this is a guess of a
non-developer.
Thanks very much in advance.
Please reply also to this email address, since I'm not subscriber of the
list I post to.
Oliver
- Pieter
Hello Pieter,
ISIS3 utilises the very same revision of libprotobuf as FreeBSD has in
the ports repositorium (libprotobuf.so.4.0.0, aka protobuf-2.2.0). The
backtrace follows, it is a little bit lengthy ...
(gdb) bt
#0 0x000805a2f2c8 in std::_Rb_treestd::pair >,
std::_Select1st
> >, std::less, std::allocatorconst, std::pair > >::_M_insert_unique () from
/usr/local/lib/libprotobuf.so.4
#1 0x000805a326c6 in
google::protobuf::InsertIfNotPresentstd::pair, std::less, std::a
locator > > >,
std::string, std::pair > ()
from /usr/local/lib/libprotobuf.so.4
#2 0x000805a32d4f in
google::protobuf::SimpleDescriptorDatabase::DescriptorIndexconst*, int> >::AddFile ()
from /usr/local/lib/libprotobuf.so.4
#3 0x000805a2df86 in
google::protobuf::EncodedDescriptorDatabase::Add () from
/usr/local/lib/libprotobuf.so.4
#4 0x0008059ed8fd in
google::protobuf::DescriptorPool::InternalAddGeneratedFile () from
/usr/local/lib/libprotobuf.so.4
#5 0x000805a16218 in
google::protobuf::protobuf_AddDesc_google_2fprotobuf_2fdescriptor_2eproto ()
from /usr/local/lib/libprotobuf.so.4
#6 0x000805a168a5 in __static_initialization_and_destruction_0 ()
from /usr/local/lib/libprotobuf.so.4
#7 0x000805a64aab in __do_global_ctors_aux () from
/usr/local/lib/libprotobuf.so.4
#8 0x0008059d00f6 in _init () from /usr/local/lib/libprotobuf.so.4
#9 0x00080064bc70 in ?? () from /libexec/ld-elf.so.1
#10 0x00080052582b in dlsym () from /libexec/ld-elf.so.1
#11 0x000800526b85 in dlopen () from /libexec/ld-elf.so.1
#12 0x0008005217a9 in ?? () from /libexec/ld-elf.so.1
#13 0x in ?? ()
#14 0x in ?? ()
#15 0x in ?? ()
#16 0x in ?? ()
#17 0x0001 in ?? ()
#18 0x7fffe800 in ?? ()
#19 0x in ?? ()
#20 0x7fffe806 in ?? ()
#21 0x7fffe822 in ?? ()
#22 0x7fffe847 in ?? ()
#23 0x7fffe852 in ?? ()
#24 0x7fffe86c in ?? ()
#25 0x7fffe879 in ?? ()
#26 0x7fffe899 in ?? ()
#27 0x7fffe8c7 in ?? ()
#28 0x7fffe8d9 in ?? ()
#29 0x7fffe8f0 in ?? ()
#30 0x7fffe907 in ?? ()
#31 0x7fffe927 in ?? ()
#32 0x7fffe936 in ?? ()
#33 0x7fffe943 in ?? ()
#34 0x7fffe95d in ?? ()
#35 0x7fffec8e in ?? ()
#36 0x7fffecb1 in ?? ()
#37 0x7fffecbc in ?? ()
#38 0x7fffecd1 in ?? ()
#39 0x7fffed99 in ?? ()
#40 0x7fffedb2 in ?? ()
#41 0x7fffedce in ?? ()
#42 0x7fffedda in ?? ()
#43 0x7fffedee in ?? ()
---Type to continue, or q to quit---
#44 0x7fffee02 in ?? ()
#45 0x7fffee0c in ?? ()
#46 0x7fffee1d in ?? ()
#47 0x7fffee2d in ?? ()
#48 0x7fffee3a in ?? ()
#49 0x
FreeBSD ipv6 rc.conf settings issue
I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my FreeBSD 7.2-RELEASE-p6 It`s a particular issue on the ipv6_defaultrouter config, it jost does not work... Upon network and routing restart ipv6 is enabled the gif interface are given ip's and everything but the defaultrouter does not. Researching a bit i found some say that gif1 sould work and tried both ipv6_defaultrouter="-interface gif1" and ipv6_defaultrouter="2001:0470:1f0a:d40::1" but no joy... here is the basic comand line config from tunnelbroker.net http://pastebin.ca/1736599 here's the rc.conf defaultrouter="86.122.121.129" gateway_enable="YES" hostname="pgn.ro" ifconfig_nfe0="inet ." [...] ipv6_enable="YES" ipv6_network_interfaces="lo0 gif1" ipv6_gateway_enable="YES" gif_interfaces="gif1" gifconfig_gif1="86.122.121.171 216.66.80.30" ipv6_ifconfig_gif1="2001:0470:1f0a:d40::2/64" ipv6_defaultrouter="-interface gif1" [...] after that i do a quick network restart http://pastebin.ca/1736601 as ipv6 does not work i use route to add the gateaway : http://pastebin.ca/1736604 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
