ffmpeg Bus error: 10 (core dumped)
Hi all, I just installed ffmpeg from ports (after a portsnap update). Running ffmpeg results in a core dump: # /usr/local/bin/ffmpeg -i myfile.flv output.flv FFmpeg version 0.6, Copyright (c) 2000-2010 the FFmpeg developers built on Aug 10 2010 14:46:32 with gcc 3.4.6 [FreeBSD] 20060305 configuration: --prefix=/usr/local --mandir=/usr/local/man --enable-shared --enable-gpl --enable-postproc --enable-avfilter --enable-avfilter-lavf --enable-pthreads --enable-x11grab --enable-memalign-hack --cc=cc --extra-cflags=-I/usr/local/include/vorbis -I/usr/local/include --extra-ldflags=-L/usr/local/lib --extra-libs=-pthread --disable-debug --disable-sse --disable-mmx --enable-libopencore-amrnb --enable-version3 --enable-libopencore-amrwb --enable-version3 --disable-libdirac --disable-libfaac --enable-libfaad --enable-libfaadbin --enable-libgsm --enable-libmp3lame --disable-libopenjpeg --disable-libschroedinger --disable-ffplay --disable-libspeex --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid libavutil 50.15. 1 / 50.15. 1 libavcodec52.72. 2 / 52.72. 2 libavformat 52.64. 2 / 52.64. 2 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter1.19. 0 / 1.19. 0 libswscale 0.11. 0 / 0.11. 0 libpostproc 51. 2. 0 / 51. 2. 0 Bus error: 10 (core dumped) Here's the backtrace: # gdb `which ffmpeg` ffmpeg.core [...etc, etc] This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `ffmpeg'. Program terminated with signal 10, Bus error. Reading symbols from /usr/local/lib/libavdevice.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libavdevice.so.1 [...etc, etc] Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2812ea67 in ff_av_dup_packet () from /usr/local/lib/libavformat.so.1 [New LWP 100870] (gdb) bt #0 0x2812ea67 in ff_av_dup_packet () from /usr/local/lib/libavformat.so.1 Cannot access memory at address 0xbf94 Running FreeBSD 6.3-RELEASE. Any thoughts / suggestions? 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: http://www.freebsd.org site unreachable
New York is down ICMP and telnet 80 are OK -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Bertrand Sent: Friday, September 14, 2007 4:03 PM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: http://www.freebsd.org site unreachable [EMAIL PROTECTED] wrote: I am unable to get to freebsd.org is this on my end only ? Failing from Southern Ontario, Canada as well. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Root access loggin
You can patch bash to log commands to syslog/remote/etc: http://64.233.169.104/search?q=cache:y0SGTs8EoTYJ:www.linux.it/~carlo/somehacks/bup/bash-2.05b-syslog_udp01.patch+bash+perassihl=engl=usstrip=1 I set this up on a few machines and it's not too hard. You can also run a cron job to see when/who is logged in (w + netstat, for instance) and then send an email/text message, so he can't login and get rid of the logger without you knowing it. Or for the more elaborate setup: http://www.honeynet.org/tools/sebek On 7/24/07, Ian Lord [EMAIL PROTECTED] wrote: Hi, A Zend technician asked me to have a root access on one of my box to troubleshoot something wrong in Zend Platform installation that doesn't work on Freebsd. He will need root access naturally to install and debug remotely. Is there a way to log all the commands he will type and send them in a logfile ? Or is there a better solution than granting him root access from ssh ? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Root access loggin
I may be misunderstanding this, but wouldn't allowing only certain commands with sudo assume that the user actually knows what commands are needed by the user? In this situation it seems like the whole reason to grant access to the server was because the user _doesn't_ know what needs to be done. On 7/24/07, Tom Grove [EMAIL PROTECTED] wrote: Lowell Gilbert wrote: Tom Grove [EMAIL PROTECTED] writes: You could even go so far as to limit what he can use sudo on. $man sudo Giving him full root access is probably not a good idea. In practice, this approach *is* effectively giving him full root access. Once you have to give the tech the ability to edit root-owned files, you have to trust his honesty. Once any kind of local access is given to a user trust becomes an issue; regardless of root access or not. By only allowing a certain set of commands there would still need to be a great deal of cracking to gain more access. If one just gives out root access no more would need to be done. This is where sudo is unlike root access. There are some important advantages to doing it through sudo, though: one is that it makes it easy for the user to keep track of just the root-privileged commands, and another is that it's easier for the user to avoid shooting himself in the foot. Other advantages to sudo are not having to give out the root password. A possible solution may be using sudo and watch together. To watch everything done by the remote-connected tech, the most complete approach is probably watch(8), which is a much simpler way of getting everything typed on a particular tty. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] While I agree that any kind of raised privilege may not be the best idea, if it is necessary, sudo adds a layer of protection you do not get with straight root. -Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: connecting user root with ssh
In /etc/ssh/sshd_config uncomment Port 22 and change it. On 7/24/07, Hakan K [EMAIL PROTECTED] wrote: How can I change the ssh port? Thanks Troy http://dominor.com On 7/24/07, Pollywog [EMAIL PROTECTED] wrote: On Tuesday 24 July 2007 11:33:26 Norberto Meijome wrote: On Wed, 30 May 2007 02:06:38 -0700 [EMAIL PROTECTED] wrote: * If root cannot log in remotely, a cracker has to guess three guess or brute force - so quite long random passwords (or ssh keys) are extremely recommendable. things to obtain root access, instead of just one: + A valid username which is in the wheel group; + That user's password; + The root password. that is assuming, of course, that the user your just logged in with belongs to wheel. If one must allow root logins via ssh, I recommend in sshd_config: PermitRootLogin without-password This will force the use of a passphrase and disallow root login with just a password. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ipnat + mysql replication
Hi, I have 4 FreeBSD servers in one location. A firewall/nat load balances between two web servers which hits a database server for content (also behind firewall/nat). The database server replicates from a remote location (outgoing connection), where the admin interface resides (different facility). The problem I'm having is that it's a fairly well-trafficked site. The ipnat entries table fills up quickly (30,000 I think is the max), and so I have to ipnat -F fairly often (every 5 minutes or so). The problem with this is that it kills any outgoing connections (like my mysql replication). Is there a way I can set the expiration for ipnat table entries, or setup mysql replication rules in ipnat.conf that will be ignored when ipnat -F is issued? Thanks, JJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
