Re: Nut and RAID on FreeBSD 7.0
At 06:51 PM 1/9/2008, Derrick Ryalls wrote: Greetings, I have a RAID fileserver plugged into a UPS and nut is able to communicate with it successfully. With the winds making the lights flicker, I started looking into having the computer shut down when power goes out for more than say 5 minutes or so. Looking at the documentation, I found that the 'true' solution is more like the system goes into a safe state when the battery gets low, then the ups eventually dies. When power is restored, the UPS and computer are supposed to both come back to life. This would be a great system to have in place, but it does sound a bit risky and so may not be worth doing just to save my home fileserver. The instructions and the conf file have the shutdown command of 'shutdown -h +0' which will halt the system. The man page for halt says the the disk cache will be flushed, but doesn't mention anything about going to read-only or anything. I suppose my first question is whether or not flushing the cache is sufficient to save the RAID (5) array, or if I need to find a way to get the file systems into read only mode? The second question has to do with a rc.d script that nut recommends creating. The script does a 'upsdrvctl shutdown' and then a sleep 120, basically waiting for the machine to die while in the script. Won't this block the other rc.d scripts? Also, is this the magic part that enables the machine to auto power up when power is restored? Changing the shutdown command in nut to 'shutdown -p +0' looks like the sure fire way to get the system down clean before the power is lost, but if my concerns are not valid, then I could be missing out on some nice functionality for no reason. Does anyone have experience with this? I have my servers all using nut to safely shutdown. My configuration is the servers are set up with one as master for nut, that master connected to the UPS. The other servers are slaves and get their nut information from the master. My setup has the servers wait until the UPS is on low battery, then they all shutdown. As a separate part of the setup, the servers are set in their BIOS to power on, after a power failure. This is in the BIOS power setup. So if there is a minor power problem, the servers run from battery. In a larger power outage, they are shutdown cleanly once the battery level is low, and power up automatically once power is restored. In my upsmon.conf file I have this: SHUTDOWNCMD /sbin/shutdown -h +0 If you want more specifics, I can look through the configuration files and email you relevant settings. As far as my experiences using nut with RAID and different setups if the shutdown command works from a command line, it will work the same from nut. I would also suggest you test your setup. Pull the plug on your UPS and watch what happens. Also you should employ other monitoring systems and scripts, should a system not reboot correctly, you do want to know that quickly. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail from: field question
Lowell Gilbert wrote: The answer will probably depend on the MTA you're using (which you didn't mention, so it's probably sendmail) You've guessed it. Its out-of-the-box sendmail. Run the script from the command line and in particular just call mail the way the script does. If I run the script (or just send a mail) on the command line using sudo, then it's sent as me and not root. Same happens if I su to root first. The only way I can get it to be sent from root is if I explicitly login as root. Make sure the results are the same (if they're not, the MTA isn't the problem). So it looks like it isn't. What can be the cause of this then? Thanks for your help. JimBow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apache portupgrade conflicts with apr-db43
Tankko пишет: Does anyone know the answer to this? I am stuck as to how to proceed? Rebuild subversion with apache support. That way you would not need separate apr package. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail from: field question
[ apologies to Jim Bow who gets this twice due to my fingers typing faster than my brain. ] On Thu, Jan 10, 2008 at 10:46:30AM +, Jim Bow wrote: If I run the script (or just send a mail) on the command line using sudo, then it's sent as me and not root. Same happens if I su to root first. use 'su -'. It means you get a login shell (which sets up the enviroment in the same way that login does). I expect you can do the same thing with sudo with something like 'sudo bash -login' or similar. The only way I can get it to be sent from root is if I explicitly login as root. Make sure the results are the same (if they're not, the MTA isn't the problem). So it looks like it isn't. What can be the cause of this then? The extra things the shell does when running as a login shell; in particular clearing the enviroment and setting things like LOGNAME and USER (which I expect /usr/bin/mail and others pay attention to). -- Shenanigans! Shenanigans!Best of 3! -- Flash ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to run GUI under root in FreeBSD?
Hi all I want to run ddd debugger under root. I ran following before become root: xhost localhost Under root: echo $DISPLAY :0.0 When I run ddd: Xlib: connection to :0.0 refused by server Xlib: No protocol specified Error: Can't open display: :0.0 What else I should do in FreeBSD? I'm running 7.0-PRERELEASE on i386 with KDE 3.5.8. Appreciate very much a reply. Best Regards Unga Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
goffice fails to install
Hello list, I had gnumeric installed, and wanted to upgrade. portupgrade gnumeric failed because it wanted a newer version of goffice. I deinstalled the old goffice and did make install. It fails here: ... -- Installing ./html/right.png -- Installing ./html/style.css -- Installing ./html/up.png -- Installing ./html/index.sgml gmake[3]: *** [install-data-local] Error 1 gmake[3]: Leaving directory `/usr/ports/devel/goffice/work/goffice-0.6.1/docs/reference' gmake[2]: *** [install-am] Error 2 gmake[2]: Leaving directory `/usr/ports/devel/goffice/work/goffice-0.6.1/docs/reference' gmake[1]: *** [install-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/goffice/work/goffice-0.6.1/docs' gmake: *** [install-recursive] Error 1 *** Error code 2 Stop in /usr/ports/devel/goffice. Using 6.2-RELEASE-p9 i386, ports tree is up to date. Any suggestions? Thanks. -- Regards, Ghirai. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to run GUI under root in FreeBSD?
On Thursday 10 January 2008 06:52:38 am Unga wrote: Hi all I want to run ddd debugger under root. I ran following before become root: xhost localhost Under root: echo $DISPLAY :0.0 When I run ddd: Xlib: connection to :0.0 refused by server Xlib: No protocol specified Error: Can't open display: :0.0 What else I should do in FreeBSD? I'm running 7.0-PRERELEASE on i386 with KDE 3.5.8. Appreciate very much a reply. Best Regards Unga im not sure if its the best or correct way, but i was able to run an app (not ddd, i dont have that on my system) as root by doing this: (as my user) xhost + (then su - up to root) xcalc -display :0 nothing else to it. also, you might take a look at the man for xhost to see how to narrow down the access, because the '+' only gives you a nice little you are now wide open for connections message. cheers, -- Jonathan Horne http://dfwlpiki.dfwlp.org freebsd08 [EMAIL PROTECTED] dfwlp.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail from: field question
Mike Bristow wrote: On Thu, Jan 10, 2008 at 10:46:30AM +, Jim Bow wrote: If I run the script (or just send a mail) on the command line using sudo, then it's sent as me and not root. Same happens if I su to root first. use 'su -'. It means you get a login shell (which sets up the enviroment in the same way that login does). That makes perfect sense, but doesn't seem to work. Here's the output of my terminal session: host% whoami jim host% sudo su - (tried doing su - also, with same results) Password: host# whoami root host# env USER=root HOME=/root SHELL=/bin/csh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin MAIL=/var/mail/root BLOCKSIZE=K FTP_PASSIVE_MODE=YES TERM=screen HOSTTYPE=FreeBSD VENDOR=intel OSTYPE=FreeBSD MACHTYPE=i386 SHLVL=1 PWD=/root LOGNAME=root GROUP=wheel HOST=host.example.com EDITOR=vi PAGER=more host# cat /etc/motd | mail -s hello [EMAIL PROTECTED] This results in the mail from: header of [EMAIL PROTECTED] I've tried this on two different hosts with the same result. The actual thing Im trying to do is to email something from a script that runs as root from devd, but I run into the same problem of the email arriving from somebody other than root, hence trying this manually on the command line. There is definitely something that I am overlooking, but what is it? I'm extremely curious to work-out why I'm seeing such behavior as its defeating all my expectations so far. Thanks for reading. JimBow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to run GUI under root in FreeBSD?
--- Jonathan Horne [EMAIL PROTECTED] wrote: On Thursday 10 January 2008 06:52:38 am Unga wrote: Hi all I want to run ddd debugger under root. I ran following before become root: xhost localhost Under root: echo $DISPLAY :0.0 When I run ddd: Xlib: connection to :0.0 refused by server Xlib: No protocol specified Error: Can't open display: :0.0 What else I should do in FreeBSD? I'm running 7.0-PRERELEASE on i386 with KDE 3.5.8. Appreciate very much a reply. Best Regards Unga im not sure if its the best or correct way, but i was able to run an app (not ddd, i dont have that on my system) as root by doing this: (as my user) xhost + (then su - up to root) xcalc -display :0 nothing else to it. also, you might take a look at the man for xhost to see how to narrow down the access, because the '+' only gives you a nice little you are now wide open for connections message. Thanks, yep, after the access control disabled I can run ddd as root. Anyway, I'll read the xhost man page and lets see what others got to say too. Take care. Regards Unga Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsd Soekris
Good morning, I have a question. I am installing freebsd on soekris net4801. I have set console speed on soekris at 9600 an I have wrote console=comconsole on /boot/loader.conf (this path in into my tftp server) When i write: boot f0 start but it stop on: Starting the BTX loader suggestion? Thanks! -- Denis Beltramo [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: Boot Loader Broken?
Schiz0 [EMAIL PROTECTED] writes: I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE. I had some problem with the ports, but I got that taken care of. Now I'm having another very odd problem. I originally noticed something odd when I tried to shutdown from multiuser mode into single user mode. I ran shutdown now as root in multiuser. It said it was shutting down, etc. But then, it gave me the normal multiuser login prompt. So then I tried rebooting completely, and that's where the big error came up: Note that rebooting completely *is* the normal procedure, so that you know your kernel boots before you overwrite anything that depends on it. - FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jan 8 14:22:21 EST 2008) \ \: unknown command - /boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814 syms=[0x4+0x34c10+0x4+0x43ef1] Hit [Enter] to boot immediately, or any other key for a command prompt. Booting [/boot/kernel/kernel] in 4 seconds ... - Why it trying to run the command \ ? Right before I did this, I rebuilt world, including the kernel. I installed the new kernel, and was moving down to single user to install world. Is my bootloader corrupt somehow? I would suspect something more like some extra text in loader.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Python threading - some ports depend on it, others break with it
I'm having so much trouble with this. I'm hosting a trac based project which is implemented in python and uses an sqlite db backend along with its python bindings. Now it turns out that pysqlite breaks badly (compiles and installs fine but chokes on import, see http://lists.initd.org/pipermail/pysqlite/2006-May/000553.html) if python itself is compiled *without threading* support. However, on the same box I run a postgresql development and testing database and we have some triggers and other functions implemented in pl/python. Guess what? The compile of postgresql-plpython chokes upon configure if python is built *with threading* support. Running it seems to work fine, but there's a reason upstream put this check into configure because supposedly this is known to break things. ... I need both of these ports on one box and I'm not sure what to do to sort out this mess properly. Any ideas? What's up with Python's threading support on FreeBSD in any case, why is is broken? I would suggest framing either some of the programs/libraries with a few counts of 1st degree murder, and sending it to jail for life, where it can run for life in a nice little cell with it's own pet python. Would that work? It's probably a bit more work than a desirable solution, but if you don't need them running in the same space, it should work. Or have I completely missed the point (very likely given me). -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail from: field question
--On Thursday, January 10, 2008 13:22:47 + Jim Bow [EMAIL PROTECTED] wrote: Mike Bristow wrote: On Thu, Jan 10, 2008 at 10:46:30AM +, Jim Bow wrote: If I run the script (or just send a mail) on the command line using sudo, then it's sent as me and not root. Same happens if I su to root first. use 'su -'. It means you get a login shell (which sets up the enviroment in the same way that login does). That makes perfect sense, but doesn't seem to work. Here's the output of my terminal session: host% whoami jim host% sudo su - (tried doing su - also, with same results) Password: host# whoami root host# env USER=root HOME=/root SHELL=/bin/csh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin: /usr/X11R6/bin:/root/bin MAIL=/var/mail/root BLOCKSIZE=K FTP_PASSIVE_MODE=YES TERM=screen HOSTTYPE=FreeBSD VENDOR=intel OSTYPE=FreeBSD MACHTYPE=i386 SHLVL=1 PWD=/root LOGNAME=root GROUP=wheel HOST=host.example.com EDITOR=vi PAGER=more host# cat /etc/motd | mail -s hello [EMAIL PROTECTED] This results in the mail from: header of [EMAIL PROTECTED] I've tried this on two different hosts with the same result. The actual thing Im trying to do is to email something from a script that runs as root from devd, but I run into the same problem of the email arriving from somebody other than root, hence trying this manually on the command line. There is definitely something that I am overlooking, but what is it? I'm extremely curious to work-out why I'm seeing such behavior as its defeating all my expectations so far. Thanks for reading. I'm not sure what, but something is wrong. I did the exact same thing you did, but the results are completely different. [EMAIL PROTECTED] env HOST=utd59514.utdallas.edu TERM=xterm SHELL=/bin/csh GROUP=wheel USER=root HOSTTYPE=FreeBSD PAGER=more FTP_PASSIVE_MODE=YES MAIL=/var/mail/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin BLOCKSIZE=K PWD=/usr/ports/dns/noip EDITOR=vi [EMAIL PROTECTED] SHLVL=2 HOME=/root OSTYPE=FreeBSD VENDOR=intel LOGNAME=root MACHTYPE=i386 _=/usr/bin/env OLDPWD=/usr/ports [EMAIL PROTECTED] cat /etc/motd | mail -s hello [EMAIL PROTECTED] [EMAIL PROTECTED] tail /var/log/maillog Jan 10 03:44:29 utd59514 postfix/qmgr[816]: 6EDD1261839: from=[EMAIL PROTECTED], size=13491, nrcpt=1 (queue active) Jan 10 03:44:29 utd59514 postfix/smtp[37291]: 6D39E261838: to=[EMAIL PROTECTED], orig_to=root, relay=smtp.utdallas.edu[129.110.10.33]:25, delay=0.16, delays=0.01/0.06/0.05/0.04, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 855C65AEAC) Jan 10 03:44:29 utd59514 postfix/qmgr[816]: 6D39E261838: removed Jan 10 03:44:29 utd59514 postfix/smtp[37292]: 6EDD1261839: to=[EMAIL PROTECTED], orig_to=root, relay=smtp.utdallas.edu[129.110.10.33]:25, delay=0.17, delays=0/0.06/0.05/0.06, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 853C95AEA9) Jan 10 03:44:29 utd59514 postfix/qmgr[816]: 6EDD1261839: removed Jan 10 09:28:00 utd59514 postfix/pickup[37968]: 3A037261834: uid=0 from=root Jan 10 09:28:00 utd59514 postfix/cleanup[38056]: 3A037261834: message-id=[EMAIL PROTECTED] Jan 10 09:28:00 utd59514 postfix/qmgr[816]: 3A037261834: from=[EMAIL PROTECTED], size=641, nrcpt=1 (queue active) Jan 10 09:28:00 utd59514 postfix/smtp[38058]: 3A037261834: to=[EMAIL PROTECTED], relay=smtp.utdallas.edu[129.110.10.33]:25, delay=0.07, delays=0.02/0.01/0.01/0.04, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3E1575ADDD) Jan 10 09:28:00 utd59514 postfix/qmgr[816]: 3A037261834: removed [EMAIL PROTECTED] whoami root And the message received was sent by root. Received: from smtp2.utdallas.edu ([129.110.10.33]) by UTDEVS08.campus.ad.utdallas.edu with Microsoft SMTPSVC(6.0.3790.3959); Thu, 10 Jan 2008 09:29:03 -0600 Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp2.utdallas.edu (Postfix) with ESMTP id 3E1575ADDD for [EMAIL PROTECTED]; Thu, 10 Jan 2008 09:28:00 -0600 (CST) Received: by utd59514.utdallas.edu (Postfix, from userid 0) id 3A037261834; Thu, 10 Jan 2008 09:28:00 -0600 (CST) To: [EMAIL PROTECTED] Subject: hello Message-Id: [EMAIL PROTECTED] Date: Thu, 10 Jan 2008 09:28:00 -0600 (CST) From: [EMAIL PROTECTED] (Charlie Root) Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 10 Jan 2008 15:29:03.0486 (UTC) FILETIME=[87E371E0:01C8539D] FreeBSD 6.2-RELEASE-p9 (GENERIC) #2: Wed Dec 5 16:16:36 CST 2007 (1) Unauthorized use is prohibited; (2) Usage may be subject to security testing and monitoring; (3) Misuse is subject to criminal prosecution; and (4) No expectation of privacy except as otherwise provided by applicable privacy laws. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list
RE: How to run GUI under root in FreeBSD?
I would suggest using I ran following before become root: xhost localhost Under root: echo $DISPLAY :0.0 When I run ddd: Xlib: connection to :0.0 refused by server Xlib: No protocol specified Error: Can't open display: :0.0 why not sudo ddd instead? That should work just as well if there isn't a lot of cli redirecting that needs raised privs (I'm afraid I'm not familiar with ddd enough to know if it does or not). It could be tedious, but you could always make this script: xddd.sh: #!/bin/sh sudo ddd $* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network monitoring program.
Greetings, I need to monitor the network traffic from specific IP addresses. I need to be able to deduce the applications that are running that are generating the traffic. What software in the ports collection will allow me to do this ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network monitoring program.
tcpdump and pump that through ethereal? On Jan 10, 2008, at 9:14 AM, Darryl Hoar wrote: Greetings, I need to monitor the network traffic from specific IP addresses. I need to be able to deduce the applications that are running that are generating the traffic. What software in the ports collection will allow me to do this ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Eric F Crist Secure Computing Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
system programming
Good day all. I am a computer science student taking the operating systems course. All of our assignments are supposed run on Linux and I don't have a Linux machine. I was wondering mostly if FreeBSD uses the same functions for process / thread handling, whether the header files (e.g. unistd.h, stdlib.h, etc) are in the same locations and whether the pthread library is present by default. Haven't almost done any programming on FreeBSD (except Java). Thanks in advance, Michael Michael Sherman http://msherman77.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail from: field question
Paul Schmehl wrote: I'm not sure what, but something is wrong. I did the exact same thing you did, but the results are completely different. The only difference I can spot is that you are using Postfix, while the hosts I'm using all run standard Sendmail. Could this be the problem? I might give it a quick test to find out for sure. Thanks, Jim Bow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
On Jan 10, 2008 10:23 AM, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE. I had some problem with the ports, but I got that taken care of. Now I'm having another very odd problem. I originally noticed something odd when I tried to shutdown from multiuser mode into single user mode. I ran shutdown now as root in multiuser. It said it was shutting down, etc. But then, it gave me the normal multiuser login prompt. So then I tried rebooting completely, and that's where the big error came up: Note that rebooting completely *is* the normal procedure, so that you know your kernel boots before you overwrite anything that depends on it. - FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jan 8 14:22:21 EST 2008) \ \: unknown command - /boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814 syms=[0x4+0x34c10+0x4+0x43ef1] Hit [Enter] to boot immediately, or any other key for a command prompt. Booting [/boot/kernel/kernel] in 4 seconds ... - Why it trying to run the command \ ? Right before I did this, I rebuilt world, including the kernel. I installed the new kernel, and was moving down to single user to install world. Is my bootloader corrupt somehow? I would suspect something more like some extra text in loader.conf. My /etc/loader.rc: --- \ Loader.rc \ $FreeBSD: src/sys/boot/i386/loader/loader.rc,v 1.4.2.1 2005/10/30 14:37:02 scottl Exp $ \ \ Includes additional commands include /boot/loader.4th \ Reads and processes loader.conf variables start \ Tests for password -- executes autoboot first if a password was defined check-password \ Load in the boot menu include /boot/beastie.4th \ Start the boot menu beastie-start --- My /etc/loader.conf: --- # --- Generated by sysinstall --- hint.acpi.0.disabled=1 --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: system programming
Am Donnerstag, 10. Januar 2008 16:38:47 schrieb Michael S: I am a computer science student taking the operating systems course. All of our assignments are supposed run on Linux and I don't have a Linux machine. I was wondering mostly if FreeBSD uses the same functions for process / thread handling, whether the header files (e.g. unistd.h, stdlib.h, etc) are in the same locations and whether the pthread library is present by default. Whereas both systems could be termed mostly POSIX compliant (and thus you should be able to recompile program sources freely on each of the two without modifications to the source and get equal behaviour), FreeBSD's libc and kernel is (in my experience) more and the glibc (i.e., the most commonly used libc on Linux) and the Linux kernel generally somewhat less close/compliant to the specification in border- or seldom used cases. This includes (for example) the (still, IIRC) default pthreads implementation on Linux (called LinuxThreads, even though a new/better threads implementation has been available for quite some time, called NPTL), which doesn't properly support thread cancellation (or rather doesn't support them at all), and only implements a subset of the POSIX.1c (i.e., POSIX Threads) specification. FreeBSDs pthreads library is fully POSIX.1c compliant, IIRC. Some other things which I've hit when recompiling programs I implemented on FreeBSD for Linux generally concern more esoteric differences, like glibc missing a sys/endian.h (which is a heavens gift), but sys/endian.h isn't part of the POSIX standard anyway. What's not so esoteric though: socket behaviour isn't specified in the POSIX standard either; if you implement networking programs, you'll soon find that for example the error return values differ slightly between the two operating systems, making proper error recovery all the harder. Preprocessor macros are your friend, even in C++. For the rest, the compiler/linker-toolchain you'll use under Linux is (most probably) the exact same as under FreeBSD (i.e., gcc + GNU binutils), and as such you'll not have to expect any problems here. Concerning make: if you stick to writing GNU make Makefiles under FreeBSD, you'll also be on the safe side there, because I've yet to find a properly functioning BSD make implementation for Linux. Finally: stay away from the autotools if you can. They make your brain cringe. And, to finish up: generally you'll not feel the differences. And if you do, you've (most probably) hit operating system specific (i.e., non POSIX-specified) behaviour, anyway, and were on your own from the start. -- Heiko Wundram Product Application Development ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network monitoring program.
trafshow ... bye Norman Am Donnerstag, den 10.01.2008, 09:47 -0600 schrieb Eric Crist: tcpdump and pump that through ethereal? On Jan 10, 2008, at 9:14 AM, Darryl Hoar wrote: Greetings, I need to monitor the network traffic from specific IP addresses. I need to be able to deduce the applications that are running that are generating the traffic. What software in the ports collection will allow me to do this ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Eric F Crist Secure Computing Networks ___ 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 :Network monitoring program.
if any of your network devices have NetFlow capability you could try IPFlow ( http://www.ipflow.utc.fr/index.php/Main_Page ) as a collector. There are binaries for FreeBSD and as a flow collector goes it is quite straightforward. It can also be hooked up with RRDTool. Phil ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA DVD Drive Install Problem
I've been able to get 6.3-R3 and 7.0-RC1 to install from SATA DVD, but not any previous versions. On Jan 9, 2008 6:50 PM, Derrick Ryalls [EMAIL PROTECTED] wrote: On Jan 9, 2008 3:08 PM, Sean Murphy [EMAIL PROTECTED] wrote: Is anyone successful in installing FreeBSD from a SATA DVD Drive? Did it last month with a machine that has only SATA (DVD and SATA-RAID), so it is possible at least on 7.0. I am having trouble as it boots from the CD of 6.3 RC2 but at the beginning of the install it fails. The CD I then tried in another computer and it installs fine. I was wondering if it was the SATA DVD drive or the motherboard. 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] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dell Power Edge 2950
On Wed, 9 Jan 2008, Dennis Glatting wrote: As stupid as this is going to sound, I solved my dump problem on one of my 2950s running amd64 7.0 with two dual core processors. The problem was when I did a level 0 dump, regardless of partition. At random times the dump would halt, never to resume. Restarting the dump Did you disable the randomly schedule a RAID parity check of random sectors feature in the PERC5 BIOS? ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix with Cyrus SASL
Michal F. Hanula wrote: Your postfix is trying to use saslauthd, which usually listens on /var/run/saslauthd/mux. The right way to fix this depends on whether you want to use saslauthd and the place you store your e-mail user data. I want authentication against /etc/passwd (ultimately), not using sasldb2.db. There is no /var/run/saslauthd/mux, and saslauthd doesn't appear installed -- I'm getting the impression that selecting Cyrus-SASL in the make config dialog box for the Postfix port doesn't completely install cyrus-sasl components. I'm guessing the solution is to completely install the cyrus-sasl2 port to enable the use of saslauthd. Yes? Or am I way off? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nut and RAID on FreeBSD 7.0
Greetings, I have a RAID fileserver plugged into a UPS and nut is able to communicate with it successfully. With the winds making the lights flicker, I started looking into having the computer shut down when power goes out for more than say 5 minutes or so. Looking at the documentation, I found that the 'true' solution is more like the system goes into a safe state when the battery gets low, then the ups eventually dies. When power is restored, the UPS and computer are supposed to both come back to life. This would be a great system to have in place, but it does sound a bit risky and so may not be worth doing just to save my home fileserver. The instructions and the conf file have the shutdown command of 'shutdown -h +0' which will halt the system. The man page for halt says the the disk cache will be flushed, but doesn't mention anything about going to read-only or anything. I suppose my first question is whether or not flushing the cache is sufficient to save the RAID (5) array, or if I need to find a way to get the file systems into read only mode? The second question has to do with a rc.d script that nut recommends creating. The script does a 'upsdrvctl shutdown' and then a sleep 120, basically waiting for the machine to die while in the script. Won't this block the other rc.d scripts? Also, is this the magic part that enables the machine to auto power up when power is restored? Changing the shutdown command in nut to 'shutdown -p +0' looks like the sure fire way to get the system down clean before the power is lost, but if my concerns are not valid, then I could be missing out on some nice functionality for no reason. Does anyone have experience with this? I have my servers all using nut to safely shutdown. My configuration is the servers are set up with one as master for nut, that master connected to the UPS. The other servers are slaves and get their nut information from the master. My setup has the servers wait until the UPS is on low battery, then they all shutdown. As a separate part of the setup, the servers are set in their BIOS to power on, after a power failure. This is in the BIOS power setup. So if there is a minor power problem, the servers run from battery. In a larger power outage, they are shutdown cleanly once the battery level is low, and power up automatically once power is restored. In my upsmon.conf file I have this: SHUTDOWNCMD /sbin/shutdown -h +0 If you want more specifics, I can look through the configuration files and email you relevant settings. After doing more reading, I am confident that a shutdown -h would be sufficient, but am a bit concern on the order of operations. The nut documentation has a recommendation to add a kill script as such: #!/bin/sh if [ $1 == stop ] then if [ -f /etc/killpower ] then echo Killing the power, bye! /usr/local/libexec/nut/upsdrvctl shutdown sleep 120 fi fi /copy Even if I name this zz_killpower.sh to make it run last, depending on how long it takes FreeBSD to flush the cash after all rc.d scripts are run, I could end up doing a dirty power down, right? Without this, if the power does come back while before the battery finally dies, the system won't restart since the power was never fully interrupted at the computer side? As far as my experiences using nut with RAID and different setups if the shutdown command works from a command line, it will work the same from nut. I would also suggest you test your setup. Pull the plug on your UPS and watch what happens. I absolutely will do a full test as such before I put full faith in the setup, but I want to first minimize the chance of me destroying the file system during the test. Also you should employ other monitoring systems and scripts, should a system not reboot correctly, you do want to know that quickly. -Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix with Cyrus SASL
--On Thursday, January 10, 2008 13:44:23 -0600 Shawn Barnhart
[EMAIL PROTECTED] wrote:
Michal F. Hanula wrote:
Your postfix is trying to use saslauthd, which usually listens on
/var/run/saslauthd/mux. The right way to fix this depends on whether
you want to use saslauthd and the place you store your e-mail user data.
I want authentication against /etc/passwd (ultimately), not using sasldb2.db.
There is no /var/run/saslauthd/mux, and saslauthd doesn't appear installed --
I'm getting the impression that selecting Cyrus-SASL in the make config
dialog box for the Postfix port doesn't completely install cyrus-sasl
components.
It should, because it calls this:
.if defined(WITH_SASL2)
LIB_DEPENDS+= sasl2.2:${PORTSDIR}/security/cyrus-sasl2
POSTFIX_CCARGS+=-DUSE_SASL_AUTH -DUSE_CYRUS_SASL -I${LOCALBASE}/include
-I${LOCALBASE}/include/sasl
POSTFIX_AUXLIBS+= -L${LOCALBASE}/lib -lsasl2 -lpam -lcrypt
.endif
I'm guessing the solution is to completely install the cyrus-sasl2 port to
enable the use of saslauthd. Yes? Or am I way off?
Yes, you need to install saslauthd, however, if you checked the OPTION when you
installed Postfix, it's most likely already installed. You *also* need to
enable saslauthd in /etc/rc.conf:
[EMAIL PROTECTED] /usr/ports/mail/postfix]# grep sasl /etc/rc.conf
saslauthd_enable=YES
saslauthd_flags= -a pam -n 2
(This uses /etc/passwd through pam, btw.)
Look at /usr/local/etc/rc.d/saslauthd.sh for the options and flags available or
read man (8) saslauthd.
--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD's problems as seen by the BSDForen.de community
Sorry to cold-CC you on this, yongari--please ignore if this doesn't interest you. On Thu, Jan 10, 2008 at 09:40:50PM +0100, Kris Kennaway wrote: Erik Osterholm wrote: On Thu, Jan 10, 2008 at 11:56:15PM +0900, Adrian Chadd wrote: On 10/01/2008, Dominic Fandrey [EMAIL PROTECTED] wrote: This is the thing though. Its working for the developers, its not working for the users, so how do you think it'll get fixed? The second big problem is the handling of regressions. PRs remain unanswered or the reporters are told that the regressions they report do not exist. Some of our members have even suffered the experience that they developed a patch, but it simply was ignored or turned down for the reason that it was a Linux solution. Especially frustrating for those among us who have never looked at Linux code. Whats the PR number? I'm coming in in the middle of this thread, but here's one from July 2006: kern/100839 No one from the FreeBSD community ever responded on it. I thought that I'd even suggested removing the driver entirely, due to this showstopping bug, and removing its listing as compatible, but now I can't find an archived reference, so maybe it was in my head. I love FreeBSD, and I used it on a daily basis, but there's an example, if you're genuinely interested. Erik Yeah, that's a pretty good example of hardware with no real maintainer in the FreeBSD community. Actually it does look like yongari@ worked on it a couple of months ago, so you might want to bring it to his attention. Kris I can do that, though it looks like the changes made were quite generic to interfaces in general, and not specific to the TXP. While I was trying to get this to work, it looked pretty likely that the problem was in how the kernel was talking to the device itself--the device would get confused when it was brought down and back up. My recollection is that the Linux driver just stops I/O to the card, but leaves it in its online state, effectively disconnecting it from the TCP/IP stack, in order to bring it down. FreeBSD tries to actually disable the interface, but doesn't re-initialize it correctly when bringing it back up. If someone doesn't want to take accountability for the bug, I'd really like to see it removed from the compatibility list. I could probably find some hardware to donate to the cause of fixing it, if someone was committed to fixing it, though. Erik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd6 authenticating against openldap 2.4?
Hi Dave If you don't mind I'm going to reply on-list in case anyone else has comments. I might also teach you to suck eggs, a bit, because, not knowing your setup or experience level, I'm going to start a bit further back than your initial question, and mention a few things that I either think are important, or found useful to have in place. This is a long message, but I think it covers most of the things that tripped me up. You're going to be installing a number of ports/packages on all your machines to get LDAP authentication working. When I took over my current post, every server had its own source tree, its own ports tree, and just in terms of base OS we were running everything from 4.7-RELEASE to 5.3-RELEASE, including a couple of boxes running STABLE snapshots. Every box was configured differently and ports trees had been installed/updated more or less at random. I now have a fast box with a ports tree and source tree, both initially created with cvsup/csup (otherwise you can run into trouble with cvsup not deleting files because it didn't create them). It builds every kernel configuration I need, and the source, object and ports trees are NFS-mountable on all my other servers. All machines are configured to look for packages on my build server only, and whenever I build a port for the first time, I build a package from it which is written back to the build server. I also have a standard ``base'' server buildout which includes portupgrade, lynx, bash, sudo, and the LDAP stuff, among others. If you've got something like this in place, you can start planning your LDAP migration. The first thing is to decide what else you're going to use LDAP for so you can plan your directory. The painful mistake to avoid is to do with the class of the objects in your directory. There are two types of objectClass, structural and auxiliary, and although an object can belong to several auxiliary classes, it can only be in one structural class: if you pick the wrong one it's a pain to recover. My user accounts have a structural objectClass of inetOrgPerson, and auxiliaries of posixAccount and extensibleObject (the last is to allow me to use the host: attribute, of which more later). I'm currently able to run shell accounts on different boxes on a per-user basis, SMTP AUTH with sendmail, and user authentication for Cyrus IMAP and squirrelmail, among other things, from the user account information, and I'm working on using LDAP for maps in sendmail. The other thing you need to watch out for, both before the migration and on an ongoing basis afterwards, is user account numbers. There are two problems. First of all, you have to make sure that each user is able to have the same uid number on every machine. The second and in some ways more difficult problem is what I call NPCs - accounts which don't correspond to a human user because they were created by ports. Some of these have reserved numbers but most simply use pw useradd to create a new user. If you haven't planned for this you can find that the same uid number represents one user on one host, a different user on another host, and an NPC account such as dhcpd on a third. I renumbered all my accounts, both user and NPC, so that real users start at 1100 for my primary site, 1200, 1300 and so on on my other sites, and NPC accounts are 1000-1099. To make sure this stays the case, I create /etc/pw.conf on every machine, containing: reuseuids yes reusegids yes to use the lowest currently-unused uid number. Otherwise each time you install a port, it picks a uid number one higher than the highest currently in use, which screws up your numbering again. It's seriously worth getting all this right before you start implementing LDAP - once you've done so, LDAP itself is relatively straightforward. You need OpenLDAP itself - I'm not sure what the differences are between 2.3 and 2.4 but 2.3 works for me - plus nss_ldap and pam_ldap, both of which are in the ports tree. Create your user accounts, configure pam_ldap and nss_ldap, and make a few changes in /etc/pam.d and /etc/nsswitch.conf. These are the easy bits! Some last considerations: you can use the host: attribute in user accounts to limit which hosts each user can log in to, and you can install an additional port, pam_mkhomedir, which will create the home directory on login on each host, if you want local homedirs rather than an NFS mount. You will also find that users can't change their LDAP password through the normal channels. Although passwd(1) was rewritten a few years ago to be able to use PAM, the necessary code is diked out. Another issue which has come up on the list a few times: your LDAP server(s) is/are going to need some tweaking because there is a chicken-and-egg problem during booting. Before the system can use an account, it has to enumerate every group that account belongs to to make sure the right privileges are available. If you're starting the LDAP server as user ldap, the system tries to
Re: Postfix with Cyrus SASL
Paul Schmehl wrote:
It should, because it calls this:
.if defined(WITH_SASL2)
LIB_DEPENDS+= sasl2.2:${PORTSDIR}/security/cyrus-sasl2
POSTFIX_CCARGS+=-DUSE_SASL_AUTH -DUSE_CYRUS_SASL
-I${LOCALBASE}/include -I${LOCALBASE}/include/sasl
POSTFIX_AUXLIBS+= -L${LOCALBASE}/lib -lsasl2 -lpam -lcrypt
.endif
Yes, you need to install saslauthd, however, if you checked the OPTION
when you installed Postfix, it's most likely already installed. You
*also* need to enable saslauthd in /etc/rc.conf:
[EMAIL PROTECTED] /usr/ports/mail/postfix]# grep sasl /etc/rc.conf
saslauthd_enable=YES
saslauthd_flags= -a pam -n 2
(This uses /etc/passwd through pam, btw.)
Look at /usr/local/etc/rc.d/saslauthd.sh for the options and flags
available or read man (8) saslauthd.
Either I'm totally fubar, or the ports snapshot I have is braindead as I
did select the SASL option when I built postfix and I have sasl libs in
/usr/local/lib and /usr/local/lib/sasl2 but none of the other sasl
components are installed. No saslauthd in /usr/local/etc/rc.d, no
manpage, just libraries mentioned above, and my postfix smtpd does
appear to have a sasl library run-time dependency per ldd.
Is the better fix to manually re-install the same Cyrus sasl port or
deinstall both it and postfix and rebuild postfix with the sasl option
and hope I get a complete build?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
How to add proxy modules to Apache22 on FreeBSD 6.3
I have just spent the whole day trying to figure out how to enable mod_proxy, mod_proxy_http, and mod_proxy_balancer in Apache22 on FreeBSD 6.3. As I was writing up the question, I figured it out (isn't that so often the case?) It was stupidly simple, so perhaps this email will save someone else from a wasted day... This has always worked in the past for me, but didn't work on my new 6.3 machine (despite the instructions in the Makefiles): cd /usr/ports/www/apache22 make clean make WITH_CUSTOM_PROXY=proxy proxy_http proxy_balancer make deinstall make reinstall I tried every make variation possible. I tried putting my options in make.conf. I changed the Makefile.options. But nothing worked... no matter what I tried, Apache always complied without the new proxy modules. Oh, and I wore out Google searching for help. Every example showed something like the above, with an occasional sentence like 'with FreeBSD you don't run ./configure'. Well, actually, you do... sort of... Here's the answer you've been googling for. Do this: cd /usr/ports/www/apache22 make configure A nice menu will pop up, with all the current options selected. Just scroll down and click the modules you want, save, then continue as above. Of course, you still need to add the modules to httpd.conf: LoadModule proxy_module libexec/apache22/mod_proxy.so LoadModule proxy_http_module libexec/apache22/mod_proxy_http.so LoadModule proxy_balancer_module libexec/apache22/mod_proxy_balancer.so Restart apache and you are ready to go! Wow! I wish I'd found this email sooner! -- John Websites for On-line Collectible Dealers Identry, LLC John Almberg [EMAIL PROTECTED] www.identry.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nut and RAID on FreeBSD 7.0
At 01:40 PM 1/10/2008, Derrick Ryalls wrote: Greetings, I have a RAID fileserver plugged into a UPS and nut is able to communicate with it successfully. With the winds making the lights flicker, I started looking into having the computer shut down when power goes out for more than say 5 minutes or so. Looking at the documentation, I found that the 'true' solution is more like the system goes into a safe state when the battery gets low, then the ups eventually dies. When power is restored, the UPS and computer are supposed to both come back to life. This would be a great system to have in place, but it does sound a bit risky and so may not be worth doing just to save my home fileserver. The instructions and the conf file have the shutdown command of 'shutdown -h +0' which will halt the system. The man page for halt says the the disk cache will be flushed, but doesn't mention anything about going to read-only or anything. I suppose my first question is whether or not flushing the cache is sufficient to save the RAID (5) array, or if I need to find a way to get the file systems into read only mode? The second question has to do with a rc.d script that nut recommends creating. The script does a 'upsdrvctl shutdown' and then a sleep 120, basically waiting for the machine to die while in the script. Won't this block the other rc.d scripts? Also, is this the magic part that enables the machine to auto power up when power is restored? Changing the shutdown command in nut to 'shutdown -p +0' looks like the sure fire way to get the system down clean before the power is lost, but if my concerns are not valid, then I could be missing out on some nice functionality for no reason. Does anyone have experience with this? I have my servers all using nut to safely shutdown. My configuration is the servers are set up with one as master for nut, that master connected to the UPS. The other servers are slaves and get their nut information from the master. My setup has the servers wait until the UPS is on low battery, then they all shutdown. As a separate part of the setup, the servers are set in their BIOS to power on, after a power failure. This is in the BIOS power setup. So if there is a minor power problem, the servers run from battery. In a larger power outage, they are shutdown cleanly once the battery level is low, and power up automatically once power is restored. In my upsmon.conf file I have this: SHUTDOWNCMD /sbin/shutdown -h +0 If you want more specifics, I can look through the configuration files and email you relevant settings. After doing more reading, I am confident that a shutdown -h would be sufficient, but am a bit concern on the order of operations. The nut documentation has a recommendation to add a kill script as such: #!/bin/sh if [ $1 == stop ] then if [ -f /etc/killpower ] then echo Killing the power, bye! /usr/local/libexec/nut/upsdrvctl shutdown sleep 120 fi fi /copy Even if I name this zz_killpower.sh to make it run last, depending on how long it takes FreeBSD to flush the cash after all rc.d scripts are run, I could end up doing a dirty power down, right? Without this, if the power does come back while before the battery finally dies, the system won't restart since the power was never fully interrupted at the computer side? You are reading the old documentation. The current nut, 2.2, has complete rc scripts that are installed in /usr/local/etc/rc.d You need only define the flag file you want to use in upsmon.conf Also define what actions you want in that file as well. You need to use the sample files installed in /usr/local/etc/nut and be sure to read the comments. -Derek As far as my experiences using nut with RAID and different setups if the shutdown command works from a command line, it will work the same from nut. I would also suggest you test your setup. Pull the plug on your UPS and watch what happens. I absolutely will do a full test as such before I put full faith in the setup, but I want to first minimize the chance of me destroying the file system during the test. Also you should employ other monitoring systems and scripts, should a system not reboot correctly, you do want to know that quickly. -Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.
Re: Postfix with Cyrus SASL
On Thu, 10 Jan 2008 15:46:33 -0600
Shawn Barnhart [EMAIL PROTECTED] wrote:
Paul Schmehl wrote:
It should, because it calls this:
.if defined(WITH_SASL2)
LIB_DEPENDS+= sasl2.2:${PORTSDIR}/security/cyrus-sasl2
POSTFIX_CCARGS+=-DUSE_SASL_AUTH -DUSE_CYRUS_SASL
-I${LOCALBASE}/include -I${LOCALBASE}/include/sasl
POSTFIX_AUXLIBS+= -L${LOCALBASE}/lib -lsasl2 -lpam -lcrypt
.endif
Yes, you need to install saslauthd, however, if you checked the
OPTION when you installed Postfix, it's most likely already
installed. You *also* need to enable saslauthd in /etc/rc.conf:
[EMAIL PROTECTED] /usr/ports/mail/postfix]# grep sasl /etc/rc.conf
saslauthd_enable=YES
saslauthd_flags= -a pam -n 2
(This uses /etc/passwd through pam, btw.)
Look at /usr/local/etc/rc.d/saslauthd.sh for the options and flags
available or read man (8) saslauthd.
Either I'm totally fubar, or the ports snapshot I have is braindead
as I did select the SASL option when I built postfix and I have sasl
libs in /usr/local/lib and /usr/local/lib/sasl2 but none of the other
sasl components are installed. No saslauthd in /usr/local/etc/rc.d,
no manpage, just libraries mentioned above, and my postfix smtpd does
appear to have a sasl library run-time dependency per ldd.
Is the better fix to manually re-install the same Cyrus sasl port or
deinstall both it and postfix and rebuild postfix with the sasl
option and hope I get a complete build?
It has been awhile; however, if I remember correctly, the 'saslauthd'
daemon is not installed by Postfix. I think you are confusing this with
SASL in general. You might want to read the 'Complete Book of Postfix
for further information on getting SASL up and running. BTW, unless it
has changes, 'saslauthd' only handles plain text authentication.
--
Gerard
[EMAIL PROTECTED]
A chronic disposition to inquiry
deprives domestic felines of vital qualities.
signature.asc
Description: PGP signature
Re: Postfix with Cyrus SASL
--On Thursday, January 10, 2008 15:46:33 -0600 Shawn Barnhart
[EMAIL PROTECTED] wrote:
Paul Schmehl wrote:
It should, because it calls this:
.if defined(WITH_SASL2)
LIB_DEPENDS+= sasl2.2:${PORTSDIR}/security/cyrus-sasl2
POSTFIX_CCARGS+=-DUSE_SASL_AUTH -DUSE_CYRUS_SASL
-I${LOCALBASE}/include -I${LOCALBASE}/include/sasl
POSTFIX_AUXLIBS+= -L${LOCALBASE}/lib -lsasl2 -lpam -lcrypt
.endif
Yes, you need to install saslauthd, however, if you checked the OPTION
when you installed Postfix, it's most likely already installed. You
*also* need to enable saslauthd in /etc/rc.conf:
[EMAIL PROTECTED] /usr/ports/mail/postfix]# grep sasl /etc/rc.conf
saslauthd_enable=YES
saslauthd_flags= -a pam -n 2
(This uses /etc/passwd through pam, btw.)
Look at /usr/local/etc/rc.d/saslauthd.sh for the options and flags
available or read man (8) saslauthd.
Either I'm totally fubar, or the ports snapshot I have is braindead as I did
select the SASL option when I built postfix and I have sasl libs in
/usr/local/lib and /usr/local/lib/sasl2 but none of the other sasl components
are installed. No saslauthd in /usr/local/etc/rc.d, no manpage, just
libraries mentioned above, and my postfix smtpd does appear to have a sasl
library run-time dependency per ldd.
Is the better fix to manually re-install the same Cyrus sasl port or
deinstall both it and postfix and rebuild postfix with the sasl option and
hope I get a complete build?
If Postfix is working as you expect (except for auth of course), I would just
force the reinstall of sasl (or deinstall and reinstall if that's your
preferred method.)
Saslauthd is installed in /usr/local/sbin/saslauthd, btw.
--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
How backup huge pgsql ?
Hi all I want to known how can I make backup of huge postgresql database (huge mean ~ 2To). I can stop the access of the database during N1 hours. Any idea about this ? Regards. -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Heure local/Local time: Jeu 10 jan 2008 23:05:00 CET ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix with Cyrus SASL
--On Thursday, January 10, 2008 17:01:03 -0500 Gerard [EMAIL PROTECTED]
wrote:
On Thu, 10 Jan 2008 15:46:33 -0600
Shawn Barnhart [EMAIL PROTECTED] wrote:
Paul Schmehl wrote:
It should, because it calls this:
.if defined(WITH_SASL2)
LIB_DEPENDS+= sasl2.2:${PORTSDIR}/security/cyrus-sasl2
POSTFIX_CCARGS+=-DUSE_SASL_AUTH -DUSE_CYRUS_SASL
-I${LOCALBASE}/include -I${LOCALBASE}/include/sasl
POSTFIX_AUXLIBS+= -L${LOCALBASE}/lib -lsasl2 -lpam -lcrypt
.endif
Yes, you need to install saslauthd, however, if you checked the
OPTION when you installed Postfix, it's most likely already
installed. You *also* need to enable saslauthd in /etc/rc.conf:
[EMAIL PROTECTED] /usr/ports/mail/postfix]# grep sasl /etc/rc.conf
saslauthd_enable=YES
saslauthd_flags= -a pam -n 2
(This uses /etc/passwd through pam, btw.)
Look at /usr/local/etc/rc.d/saslauthd.sh for the options and flags
available or read man (8) saslauthd.
Either I'm totally fubar, or the ports snapshot I have is braindead
as I did select the SASL option when I built postfix and I have sasl
libs in /usr/local/lib and /usr/local/lib/sasl2 but none of the other
sasl components are installed. No saslauthd in /usr/local/etc/rc.d,
no manpage, just libraries mentioned above, and my postfix smtpd does
appear to have a sasl library run-time dependency per ldd.
Is the better fix to manually re-install the same Cyrus sasl port or
deinstall both it and postfix and rebuild postfix with the sasl
option and hope I get a complete build?
It has been awhile; however, if I remember correctly, the 'saslauthd'
daemon is not installed by Postfix. I think you are confusing this with
SASL in general. You might want to read the 'Complete Book of Postfix
for further information on getting SASL up and running. BTW, unless it
has changes, 'saslauthd' only handles plain text authentication.
I think you're right. It's been a while for me as well, but looking at ports I
see that there's a totally separate cyrus-sasl2-saslauthd port, and it doesn't
appear to be a dependency for postfix.
I think saslauthd will handle kerberos as well as plaintext, but most people
use plaintext and then ssl-ize postfix to encrypt the session.
--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network monitoring program.
If you have the correct network setup available (network tap, hubs, SPAN/mirror port) then ntop will give you a good deal of help. On Jan 10, 2008 7:14 AM, Darryl Hoar [EMAIL PROTECTED] wrote: Greetings, I need to monitor the network traffic from specific IP addresses. I need to be able to deduce the applications that are running that are generating the traffic. What software in the ports collection will allow me to do this ? thanks, Darryl ___ 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: Python threading - some ports depend on it, others break with it
Jim Stapleton wrote: I'm having so much trouble with this. I'm hosting a trac based project which is implemented in python and uses an sqlite db backend along with its python bindings. Now it turns out that pysqlite breaks badly (compiles and installs fine but chokes on import, see http://lists.initd.org/pipermail/pysqlite/2006-May/000553.html) if python itself is compiled *without threading* support. However, on the same box I run a postgresql development and testing database and we have some triggers and other functions implemented in pl/python. Guess what? The compile of postgresql-plpython chokes upon configure if python is built *with threading* support. Running it seems to work fine, but there's a reason upstream put this check into configure because supposedly this is known to break things. ... I need both of these ports on one box and I'm not sure what to do to sort out this mess properly. Any ideas? What's up with Python's threading support on FreeBSD in any case, why is is broken? I would suggest framing either some of the programs/libraries with a few counts of 1st degree murder, and sending it to jail for life, where it can run for life in a nice little cell with it's own pet python. Would that work? It's probably a bit more work than a desirable solution, but if you don't need them running in the same space, it should work. Or have I completely missed the point (very likely given me). It's a good suggestion but I can see that being more trouble than it's worth. I wouldn't want to spend countless hours making sure that all those files, their dependencies, libraries and all that other jazz is in a jail on its own working smoothly, and even if I get it right upgrading components (e.g. security vulnerabilities) will prove to be a nightmare. Getting a second box is out of the question, for now at least, and while I thought virtualization might be the answer I see that FreeBSD only has guest support for Xen :-( Oh well, guess I'll post to freebsd-python to get some solution perhaps. Gunther ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nut and RAID on FreeBSD 7.0
Greetings, I have a RAID fileserver plugged into a UPS and nut is able to communicate with it successfully. With the winds making the lights flicker, I started looking into having the computer shut down when power goes out for more than say 5 minutes or so. Looking at the documentation, I found that the 'true' solution is more like the system goes into a safe state when the battery gets low, then the ups eventually dies. When power is restored, the UPS and computer are supposed to both come back to life. This would be a great system to have in place, but it does sound a bit risky and so may not be worth doing just to save my home fileserver. The instructions and the conf file have the shutdown command of 'shutdown -h +0' which will halt the system. The man page for halt says the the disk cache will be flushed, but doesn't mention anything about going to read-only or anything. I suppose my first question is whether or not flushing the cache is sufficient to save the RAID (5) array, or if I need to find a way to get the file systems into read only mode? The second question has to do with a rc.d script that nut recommends creating. The script does a 'upsdrvctl shutdown' and then a sleep 120, basically waiting for the machine to die while in the script. Won't this block the other rc.d scripts? Also, is this the magic part that enables the machine to auto power up when power is restored? Changing the shutdown command in nut to 'shutdown -p +0' looks like the sure fire way to get the system down clean before the power is lost, but if my concerns are not valid, then I could be missing out on some nice functionality for no reason. Does anyone have experience with this? I have my servers all using nut to safely shutdown. My configuration is the servers are set up with one as master for nut, that master connected to the UPS. The other servers are slaves and get their nut information from the master. My setup has the servers wait until the UPS is on low battery, then they all shutdown. As a separate part of the setup, the servers are set in their BIOS to power on, after a power failure. This is in the BIOS power setup. So if there is a minor power problem, the servers run from battery. In a larger power outage, they are shutdown cleanly once the battery level is low, and power up automatically once power is restored. In my upsmon.conf file I have this: SHUTDOWNCMD /sbin/shutdown -h +0 If you want more specifics, I can look through the configuration files and email you relevant settings. After doing more reading, I am confident that a shutdown -h would be sufficient, but am a bit concern on the order of operations. The nut documentation has a recommendation to add a kill script as such: #!/bin/sh if [ $1 == stop ] then if [ -f /etc/killpower ] then echo Killing the power, bye! /usr/local/libexec/nut/upsdrvctl shutdown sleep 120 fi fi /copy Even if I name this zz_killpower.sh to make it run last, depending on how long it takes FreeBSD to flush the cash after all rc.d scripts are run, I could end up doing a dirty power down, right? Without this, if the power does come back while before the battery finally dies, the system won't restart since the power was never fully interrupted at the computer side? You are reading the old documentation. The current nut, 2.2, has complete rc scripts that are installed in /usr/local/etc/rc.d You need only define the flag file you want to use in upsmon.conf Also define what actions you want in that file as well. You need to use the sample files installed in /usr/local/etc/nut and be sure to read the comments. I have 2.2 installed and am using the existing scripts. In the comments in uspmon.conf, there is this part: # -- # POWERDOWNFLAG - Flag file for forcing UPS shutdown on the master system # # upsmon will create a file with this name in master mode when it's time # to shut down the load. You should check for this file's existence in # your shutdown scripts and run 'upsdrvctl shutdown' if it exists. # # See the shutdown.txt file in the docs subdirectory for more information. POWERDOWNFLAG /etc/killpower Which in the related documentation means I need the custom shutdown script mentioned above which checks for the existence of the /etc/killpower file before doing the upsdrvctl shutdown command to kill the UPS before the battery is completely dead. I suppose in your situation you won't need this extra script as you run until the UPS is critical whereas I am trying to kill the system a bit early, before it is critical. Perhaps I need to re-evaluate my line of
Re: Nut and RAID on FreeBSD 7.0
At 04:43 PM 1/10/2008, Derrick Ryalls wrote: Greetings, I have a RAID fileserver plugged into a UPS and nut is able to communicate with it successfully. With the winds making the lights flicker, I started looking into having the computer shut down when power goes out for more than say 5 minutes or so. Looking at the documentation, I found that the 'true' solution is more like the system goes into a safe state when the battery gets low, then the ups eventually dies. When power is restored, the UPS and computer are supposed to both come back to life. This would be a great system to have in place, but it does sound a bit risky and so may not be worth doing just to save my home fileserver. The instructions and the conf file have the shutdown command of 'shutdown -h +0' which will halt the system. The man page for halt says the the disk cache will be flushed, but doesn't mention anything about going to read-only or anything. I suppose my first question is whether or not flushing the cache is sufficient to save the RAID (5) array, or if I need to find a way to get the file systems into read only mode? The second question has to do with a rc.d script that nut recommends creating. The script does a 'upsdrvctl shutdown' and then a sleep 120, basically waiting for the machine to die while in the script. Won't this block the other rc.d scripts? Also, is this the magic part that enables the machine to auto power up when power is restored? Changing the shutdown command in nut to 'shutdown -p +0' looks like the sure fire way to get the system down clean before the power is lost, but if my concerns are not valid, then I could be missing out on some nice functionality for no reason. Does anyone have experience with this? I have my servers all using nut to safely shutdown. My configuration is the servers are set up with one as master for nut, that master connected to the UPS. The other servers are slaves and get their nut information from the master. My setup has the servers wait until the UPS is on low battery, then they all shutdown. As a separate part of the setup, the servers are set in their BIOS to power on, after a power failure. This is in the BIOS power setup. So if there is a minor power problem, the servers run from battery. In a larger power outage, they are shutdown cleanly once the battery level is low, and power up automatically once power is restored. In my upsmon.conf file I have this: SHUTDOWNCMD /sbin/shutdown -h +0 If you want more specifics, I can look through the configuration files and email you relevant settings. After doing more reading, I am confident that a shutdown -h would be sufficient, but am a bit concern on the order of operations. The nut documentation has a recommendation to add a kill script as such: #!/bin/sh if [ $1 == stop ] then if [ -f /etc/killpower ] then echo Killing the power, bye! /usr/local/libexec/nut/upsdrvctl shutdown sleep 120 fi fi /copy Even if I name this zz_killpower.sh to make it run last, depending on how long it takes FreeBSD to flush the cash after all rc.d scripts are run, I could end up doing a dirty power down, right? Without this, if the power does come back while before the battery finally dies, the system won't restart since the power was never fully interrupted at the computer side? You are reading the old documentation. The current nut, 2.2, has complete rc scripts that are installed in /usr/local/etc/rc.d You need only define the flag file you want to use in upsmon.conf Also define what actions you want in that file as well. You need to use the sample files installed in /usr/local/etc/nut and be sure to read the comments. I have 2.2 installed and am using the existing scripts. In the comments in uspmon.conf, there is this part: # -- # POWERDOWNFLAG - Flag file for forcing UPS shutdown on the master system # # upsmon will create a file with this name in master mode when it's time # to shut down the load. You should check for this file's existence in # your shutdown scripts and run 'upsdrvctl shutdown' if it exists. # # See the shutdown.txt file in the docs subdirectory for more information. POWERDOWNFLAG /etc/killpower Which in the related documentation means I need the custom shutdown script mentioned above which checks for the existence of the /etc/killpower file before doing the upsdrvctl shutdown command to kill the UPS before the battery is completely dead. I suppose in your situation you won't need this extra script as you run until the UPS is critical whereas I am trying to kill the system a bit early, before it is
Re: Nut and RAID on FreeBSD 7.0
On 1/10/08, Derrick Ryalls [EMAIL PROTECTED] wrote: Perhaps I need to re-evaluate my line of thinking. Light sometime flicker, but power almost never goes out. When it does it is either back on in less than 1 minute, or out for hours. If the UPS detects critical correctly and gives me at least a minute before death, then that should be plenty of time for the system to auto-shutdown. Guess I will have to do some experimentation tonight. While you experiment, keep in mind the following sequence of events: -- Power fails -- UPS signals low battery -- System shuts down -- Power returns before UPS shuts itself down -- System never reboots, because it never lost power. Getting around this is the tricky part. I haven't used NUT in about seven years, but back then the recommendation was to shut down to single user mode and run a script that delayed for some time longer than the remaining battery life of the UPS, then rebooted the system. There didn't seem to be an easy hook for running a script after shutting down to single user mode (maybe there is now). I haven't looked at NUT recently, but I expect the various flags that you are supposed to test are another way around this problem. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with Groups
Hi everybody Freebsd 6.2 sorry this question is a bit thick I know but after getting the usb and cdrom open as root I tried as user and got the following message A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface org.freedesktop.Hal.Device.Volume member Mount error name (unset) destination org.freedesktop.Hal) a suggested work around was to add user to storage group would somebody be kind enough to tell me how to add user to storage group Thanks Andrew _ Share what Santa brought you https://www.mycooluncool.com___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nut and RAID on FreeBSD 7.0
On Jan 10, 2008 3:14 PM, Bob Johnson [EMAIL PROTECTED] wrote: On 1/10/08, Derrick Ryalls [EMAIL PROTECTED] wrote: Perhaps I need to re-evaluate my line of thinking. Light sometime flicker, but power almost never goes out. When it does it is either back on in less than 1 minute, or out for hours. If the UPS detects critical correctly and gives me at least a minute before death, then that should be plenty of time for the system to auto-shutdown. Guess I will have to do some experimentation tonight. While you experiment, keep in mind the following sequence of events: -- Power fails -- UPS signals low battery -- System shuts down -- Power returns before UPS shuts itself down -- System never reboots, because it never lost power. Getting around this is the tricky part. I haven't used NUT in about seven years, but back then the recommendation was to shut down to single user mode and run a script that delayed for some time longer than the remaining battery life of the UPS, then rebooted the system. There didn't seem to be an easy hook for running a script after shutting down to single user mode (maybe there is now). I haven't looked at NUT recently, but I expect the various flags that you are supposed to test are another way around this problem. At which point, you either hit the power button manually, or you telnet/ssh/web to your contollable PDU and tell it to remove power from the outlet(s) for 10 seconds. Kurt ___ 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 Groups
On Thu, Jan 10, 2008 at 11:28:17PM +, Andrew Stevens wrote: Hi everybody Freebsd 6.2 sorry this question is a bit thick I know but after getting the usb and cdrom open as root I tried as user and got the following message A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface org.freedesktop.Hal.Device.Volume member Mount error name (unset) destination org.freedesktop.Hal) a suggested work around was to add user to storage group would somebody be kind enough to tell me how to add user to storage group Thanks Andrew http://www.freebsd.org/gnome/docs/faq2.html#q19 HTH, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW-TO get Flash7 working!
Aryeh M. Friedman wrote: rm /usr/ports/distfiles/flashplugin/fp7_archive.zip An other way to fix it in some ways is to run a make makesum to update the distfile checksums The fp7_archive.zip was an odd case were I felt more comfortable deleting it -- hadn't see that error before (and didn't save it to cut and paste). I thought it was only my system, but apparently, others had this same issue with the fp7_archive.zip file. Maybe a new one was released with the same filename on adobe? Would makesum would blindly use what is in the /usr/ports/distfiles -- corrupt, man-in-the-middled, or whatever was there? I've never used makesum... I will RTFM. :) Rudy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD's problems as seen by the BSDForen.de community
On Thu, Jan 10, 2008 at 03:06:55PM -0600, Erik Osterholm wrote: Sorry to cold-CC you on this, yongari--please ignore if this doesn't interest you. I'm interesting in fixing drivers in tree. txp(4) is one of drivers that need more attention, I guess. It seems that datasheet for 3Com Typhoon is not available to developers so fixing may require lots of time and trial and errors. Unfortunately I don't have that hardware (I can't find that hardware in local store.) so it would be hard for me to fix it. If you can ship the hardware to me, please let me know. I'm somewhat overloaded so it would take more time than usual... On Thu, Jan 10, 2008 at 09:40:50PM +0100, Kris Kennaway wrote: Erik Osterholm wrote: On Thu, Jan 10, 2008 at 11:56:15PM +0900, Adrian Chadd wrote: On 10/01/2008, Dominic Fandrey [EMAIL PROTECTED] wrote: This is the thing though. Its working for the developers, its not working for the users, so how do you think it'll get fixed? The second big problem is the handling of regressions. PRs remain unanswered or the reporters are told that the regressions they report do not exist. Some of our members have even suffered the experience that they developed a patch, but it simply was ignored or turned down for the reason that it was a Linux solution. Especially frustrating for those among us who have never looked at Linux code. Whats the PR number? I'm coming in in the middle of this thread, but here's one from July 2006: kern/100839 No one from the FreeBSD community ever responded on it. I thought that I'd even suggested removing the driver entirely, due to this showstopping bug, and removing its listing as compatible, but now I can't find an archived reference, so maybe it was in my head. I love FreeBSD, and I used it on a daily basis, but there's an example, if you're genuinely interested. Erik Yeah, that's a pretty good example of hardware with no real maintainer in the FreeBSD community. Actually it does look like yongari@ worked on it a couple of months ago, so you might want to bring it to his attention. Kris I can do that, though it looks like the changes made were quite generic to interfaces in general, and not specific to the TXP. While I was trying to get this to work, it looked pretty likely that the problem was in how the kernel was talking to the device itself--the device would get confused when it was brought down and back up. My recollection is that the Linux driver just stops I/O to the card, but leaves it in its online state, effectively disconnecting it from the TCP/IP stack, in order to bring it down. FreeBSD tries to actually disable the interface, but doesn't re-initialize it correctly when bringing it back up. If someone doesn't want to take accountability for the bug, I'd really like to see it removed from the compatibility list. I could probably find some hardware to donate to the cause of fixing it, if someone was committed to fixing it, though. Erik -- Regards, Pyun YongHyeon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network monitoring program.
Hi, I need to monitor the network traffic from specific IP addresses. I need to be able to deduce the applications that are running that are generating the traffic. Unless you have full acess to the machine with that specific IP, you will never be able to do more than guessing what are the application generating the traffic: let say you are on a router smowhere on your network and you are interested by the traffic generated by some client accessing Internet, if you see traffic on TCP 80, maybe it i Internet Explorer, maybe Firefox, but it coul dalso be an anti-virus that uses port 80 to update the virus definition. And if you have very strict network usage policy on your network and you are blocking everything except port 80, it could even be Emule on top of port 80. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: system programming
Hi, I am a computer science student taking the operating systems course. All of our assignments are supposed run on Linux and I don't have a Linux machine. Programming the operating system is very dependent on the operating system. Talk your prof to accept a project based on FreeBSD, that would even broaden the scope of the course by introducing a glimpse to another OS. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW-TO get Flash7 working!
On Thu, 10 Jan 2008, Rudy wrote: Aryeh M. Friedman wrote: rm /usr/ports/distfiles/flashplugin/fp7_archive.zip An other way to fix it in some ways is to run a make makesum to update the distfile checksums The fp7_archive.zip was an odd case were I felt more comfortable deleting it -- hadn't see that error before (and didn't save it to cut and paste). I thought it was only my system, but apparently, others had this same issue with the fp7_archive.zip file. Maybe a new one was released with the same filename on adobe? Would makesum would blindly use what is in the /usr/ports/distfiles -- corrupt, man-in-the-middled, or whatever was there? Yes. Don't use make makesum unless you're porting or at least know the distfile is safe. make distclean and a refetch is the safer way to go, or updating the ports tree so the checksum comes from someone who is presumably more aware of the correct distfile. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
configure printers
I would like to configure a HP laserjet 1018 USB on freebsd. So far I have had no luck. During the boot cycle I can see the Laserjet 1018 listed as a peripheral (ulpt0 HP LaserJet 1018 address 3 rev 9.00/1.00 iclass 7/1 using bi directional niods). when I go to settings in the pop-down menu then to printers, change to administrator, freebsd doesn't show any printers connected to the computer. HELP thank you, Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail from: field question
On Thu, 10 Jan 2008 13:22:47 + Jim Bow [EMAIL PROTECTED] wrote: Mike Bristow wrote: On Thu, Jan 10, 2008 at 10:46:30AM +, Jim Bow wrote: If I run the script (or just send a mail) on the command line using sudo, then it's sent as me and not root. Same happens if I su to root first. use 'su -'. It means you get a login shell (which sets up the enviroment in the same way that login does). That makes perfect sense, but doesn't seem to work. Here's the output of my terminal session: host% whoami jim host% sudo su - (tried doing su - also, with same results) Password: host# whoami root host# env USER=root HOME=/root SHELL=/bin/csh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin MAIL=/var/mail/root BLOCKSIZE=K FTP_PASSIVE_MODE=YES TERM=screen HOSTTYPE=FreeBSD VENDOR=intel OSTYPE=FreeBSD MACHTYPE=i386 SHLVL=1 PWD=/root LOGNAME=root GROUP=wheel HOST=host.example.com EDITOR=vi PAGER=more host# cat /etc/motd | mail -s hello [EMAIL PROTECTED] This results in the mail from: header of [EMAIL PROTECTED] I've tried this on two different hosts with the same result. I can confirm this behaviour, also using csh and sendmail, and 'su -' from originally having logged in as myself, since freebsd 2.2 .. I use this csh alias whenever not entirely sure who or where I am .. paqi# alias um tty;id -p;who am i paqi# um /dev/ttyp3 login smithi uid root groups wheel operator network root ttyp3Jan 11 14:09 Note 'id -p' showing 'login smithi'; see id(1) .. I gather that sendmail must also use getlogin(2) - which value does not appear in `env` - when sending mail from an su'd session, as opposed to an original root login, and don't know whether or how this may be configurable in sendmail. paqi# mail smithi Subject: boo hoo . EOT Return-Path: [EMAIL PROTECTED] Received: from paqi.nimnet.asn.au (localhost.nimnet.asn.au [127.0.0.1]) by paqi.nimnet.asn.au (8.13.8/8.13.8) with ESMTP id m0B2gGpU059565 for [EMAIL PROTECTED]; Fri, 11 Jan 2008 13:42:16 +1100 (EST) (envelope-from [EMAIL PROTECTED]) Received: (from [EMAIL PROTECTED]) by paqi.nimnet.asn.au (8.13.8/8.13.8/Submit) id m0B2gFPr059564 for smithi; Fri, 11 Jan 2008 13:42:15 +1100 (EST) (envelope-from smithi) Date: Fri, 11 Jan 2008 13:42:15 +1100 (EST) From: Ian Smith [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: boo hoo Note 'received from [EMAIL PROTECTED]' but 'envelope-from smithi'. Also note I'm not using domain masquerading here, as I don't actually mail out from this box currently. The actual thing Im trying to do is to email something from a script that runs as root from devd, but I run into the same problem of the email arriving from somebody other than root, hence trying this manually on the command line. Hmm .. I know mail sent from cron scripts properly comes 'from root', and don't know why scripts run as root from devd would be any different. Is 'somebody other than root' consistent, and someone who's logged in, perhaps before su'ing and then starting the session that invokes devd? There is definitely something that I am overlooking, but what is it? I'm extremely curious to work-out why I'm seeing such behavior as its defeating all my expectations so far. I noticed later that Paul gets a different result .. maybe postfix as mentioned, if Paul was starting from an su'd session, not a root login? cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configure printers
Bob Falanga wrote: I would like to configure a HP laserjet 1018 USB on freebsd. So far I have had no luck. During the boot cycle I can see the Laserjet 1018 listed as a peripheral (ulpt0 HP LaserJet 1018 address 3 rev 9.00/1.00 iclass 7/1 using bi directional niods). when I go to settings in the pop-down menu then to printers, change to administrator, freebsd doesn't show any printers connected to the computer. HELP thank you, Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Which spooling do you use? LPD, LPRng, or CUPS. Did you start daemons correctly? Did you change permission on device nodes so that daemons can access the printer? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: system programming
Michael wrote: I am a computer science student taking the operating systems course. All of our assignments are supposed run on Linux and I don't have a Linux machine. I've taken programming classes and learned the hard way that the only way to ensure that my software worked correctly on the teacher's machine was to have a matching development environment. In practice, this can be very expensive and/or time consuming to achieve. Fortunately, matching the Linux distribution make, model, and version was sufficient. Now there are more options -- notably, virtual machines. I suggest that you ask your instructor to pick a free VMware Linux virtual appliance and that the teacher and students all use that: http://www.vmware.com/vmtn/appliances/directory/cat/45 HTH, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configure printers
Bob Falanga wrote: I would like to configure a HP laserjet 1018 USB on freebsd. So far I have had no luck. During the boot cycle I can see the Laserjet 1018 listed as a peripheral (ulpt0 HP LaserJet 1018 address 3 rev 9.00/1.00 iclass 7/1 using bi directional niods). when I go to settings in the pop-down menu then to printers, change to administrator, freebsd doesn't show any printers connected to the computer. HELP thank you, Bob ___ I happen to have a Laserjet 1015 that works perfectly. I believe they are quite similar. I suggest you use CUPS to operate this. A quick guide specific to FreeBSD can be found in DesktopBSD's site here: http://desktopbsd.net/wiki/doku.php?id=doc:printing Install all the ports mentioned (you may have some already installed and others will be pulled as dependencies) and then follow the rest of the instructions for setting device permissions and so on. You will have the printer running in no time. Manolis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Shell Menu that populates from /var/db/pkg
Hello all, I'd like to have a shell menu on my system that gives them available programs they can learn, but that also learns from ports/packages which options are available. (I.e. it won't list every branch port, but will list things from, say, editors, games, and possibly only certain things from graphics (for example I'd like to list imagemagick's commands and/or man page), but not gd (since gd is useless from a shell context). Has anyone written something like this? Or even close to? -Dan Mahoney -- It's like GTA, except you pay for it, and you're allowed to use the car. -Josh, on Zipcar on-demand car-rental, 3/20/05 Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot get multiport serial card working with puc driver
I have a 4-port serial card (REX-PCI64) made by RATOC Systems that is
apparently only available in Japan. It's based on the EXAR XR17C154
chip. I'd like to use it with tip(1) to support console access to
various Cisco devices.
I've seen posts indicating that the card works natively on NetBSD
because it's already defined in their /sys/dev/pci/pucdata.c file. Yet
I've been completely unable to get it working with any version of
FreeBSD, even after adding an entry to FreeBSD's /sys/dev/puc/pucdata.c
(shown below). I'm currently working with 7.0-RC1.
First of all, it's not clear to me whether I want the uart or sio
driver. I thought sio was the standard but I can only get uart to
attach itself to the device... though I've failed to get anything but
garbage out of a tip session.
I've recompiled the kernel and rebooted countless times in an effort to
understand the process. And so far, this is what I've found:
o The card is probed by the ppc, uart, and sio drivers. Both the
uart and sio drivers fail to enable port mapping, yet the uart driver
succeeds in enabling memory mapping (sio doesn't attempt memory
mapping).
o The pci_enable_io_method (in /sys/dev/pci/pci.c) uses
pci_set_command_bit to enable port mapping by setting the
PCIM_CMD_PORTEN bit, but the following call to PCI_READ_CONFIG says that
the PCIM_CMD_MEMEN bit is instead set, indicating (I suppose) a failure.
o In /sys/dev/uart/uart_dev_ns8250.c, the ns8250_probe function
checks the modem control register (REG_MCR) against a mask of 0xe0. But
this card is (incorrectly?) setting bit 6 of the MCR causing the check
to fail and resulting in the uart driver's decision to not bid on the
device. The docs for the card claim that bit 6 will be 0 so I'm not
sure what to make of this.
If I change ns8250_probe to ignore the fact that bit 6 of the MCR is
set, then I can get the uart driver to attach which provides me with my
/dev/cuau[0-3] entries. But using tip with a real Cisco router just
displays a few hundred 0xff characters on the terminal.
I'm using a GENERIC kernel to which I only added the following two
lines:
options COM_MULTIPORT
device puc
This is what I added to the puc_pci_devices array definition in
pucdata.c:
{ 0x13a8, 0x0154, 0x, 0,
Exar 4-port-PCI XR17C154,
DEFAULT_RCLK,
PUC_PORT_4S, 0x10, 0, -1,
.config_function = puc_config_exar
},
The numbers are derived from NetBSD's data.
The puc_config_exar function appears to be necessary in order to
generate the port offsets. It's identical to the puc_config_cronyx
function and only includes the following code:
if (cmd == PUC_CFG_GET_OFS) {
*res = port * 0x200;
return (0);
}
I'm not sure the full dmesg would provide much useful information, but
at least here's snippet of a verbose boot that looks interesting:
pci4: ACPI PCI bus on pcib4
pci4: domain=0, physical bus=4
found- vendor=0x13a8, dev=0x0154, revid=0x04
domain=0, bus=4, slot=0, func=0
class=07-00-02, hdrtype=0x00, mfdev=0
cmdreg=0x0102, statreg=0x0080, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=11
map[10]: type Memory, range 32, base 0xfe6ff800, size 11, enabled
pcib4: requested memory range 0xfe6ff800-0xfe6f: good
pcib4: matched entry for 4.0.INTA
pcib4: slot 0 INTA hardwired to IRQ 16
puc0: Exar 4-port-PCI XR17C154 mem 0xfe6ff800-0xfe6f irq 16 at device 0.0
on pci4
puc0: failed to enable port mapping!
puc0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xfe6ff800
puc0: [FILTER]
My main questions at this point are:
1. Do I need the sio driver? Am I wasting my time on the uart driver?
2. Is port mapping necessary? Will memory mapping not give me what I
need?
Any help or hints would be greatly appreciated. I've already spent an
embarrassing amount of time on this and I don't plan on giving up.
Thanks,
Barry
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nut and RAID on FreeBSD 7.0
On Jan 10, 2008 3:52 PM, Kurt Buff [EMAIL PROTECTED] wrote: On Jan 10, 2008 3:14 PM, Bob Johnson [EMAIL PROTECTED] wrote: On 1/10/08, Derrick Ryalls [EMAIL PROTECTED] wrote: Perhaps I need to re-evaluate my line of thinking. Light sometime flicker, but power almost never goes out. When it does it is either back on in less than 1 minute, or out for hours. If the UPS detects critical correctly and gives me at least a minute before death, then that should be plenty of time for the system to auto-shutdown. Guess I will have to do some experimentation tonight. While you experiment, keep in mind the following sequence of events: -- Power fails -- UPS signals low battery -- System shuts down -- Power returns before UPS shuts itself down -- System never reboots, because it never lost power. Getting around this is the tricky part. I haven't used NUT in about seven years, but back then the recommendation was to shut down to single user mode and run a script that delayed for some time longer than the remaining battery life of the UPS, then rebooted the system. There didn't seem to be an easy hook for running a script after shutting down to single user mode (maybe there is now). I haven't looked at NUT recently, but I expect the various flags that you are supposed to test are another way around this problem. Trying to test out the scripts, I ran into a road block. I see that upsmon is working and detecting the events I wanted to detect from these sorts of entries in /var/log/messages: Jan 10 23:28:57 frodo upsmon[80983]: UPS [EMAIL PROTECTED] on line power Plus a similar message for going to battery power. However, the notify executable is having issues and is dumping dozens of lines like this in /var/log/messages: Jan 10 23:28:09 frodo kernel: pid 81029 (upssched), uid 1005: exited on signal 11 Jan 10 23:28:09 frodo kernel: pid 81031 (upssched), uid 1005: exited on signal 11 Jan 10 23:28:10 frodo kernel: pid 81032 (upssched), uid 1005: exited on signal 11 Jan 10 23:28:10 frodo kernel: pid 81033 (upssched), uid 1005: exited on signal 11 Jan 10 23:28:11 frodo kernel: pid 81034 (upssched), uid 1005: exited on signal 11 Jan 10 23:28:11 frodo kernel: pid 81035 (upssched), uid 1005: exited on signal 11 I tried giving the user the user in question (nutmon) a shell of /bin/sh instead of /sbin/nologin but that didn't help. Any clues on how to fix this? Executing upssched from the command line it tells me not to execute directly (similar to what the man page states), and manually executing the upsched-cmd shell script does work and the script itself uses full paths for commands. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Unable to unmount idle filesystem on 6.2
I'm unable to unmount an idle filesystem (or even drop it to read-only): # mount /dev/da0s1a on / (ufs, local, noatime) devfs on /dev (devfs, local) /dev/da0s1d on /var (ufs, local, noatime, soft-updates) /dev/da0s1e on /usr (ufs, local, noatime, soft-updates) /dev/da0s1fp1 on /usr/obj (ufs, asynchronous, local, noatime) /dev/da0s1fp2 on /usr/ports (ufs, local, soft-updates) /dev/da0s1fp3 on /usr/src (ufs, local, soft-updates) /dev/da0s2d on /data (ufs, local, noatime, soft-updates) # fstat -f /usr/ports USER CMD PID FD MOUNT INUM MODE SZ|DV R/W # umount /usr/ports umount: unmount of /usr/ports failed: Device busy # umount -f /usr/ports umount: unmount of /usr/ports failed: Device busy # mount -o ro /usr/ports mount: /dev/da0s1fp2: Operation not permitted # uname -r 6.2-RELEASE-p8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
