Problems with OpenOffice 2.3.1 on FreeBSD
I use OpenOffice 2.3.1 on several hardwareplatforms running FreeBSD 7.0-PRE/AMD64 and since I upgraded OpenOffice from OO 2.3.0 to 2.3.1 I have massive problems, rendering OO unusuable! Before doing a PR I would like to aks whethere there is a solution out. Whenever I try to save a document in OO writer, OO gets stuck and I have to kill it. The document gets saved, but I never can load it again without rendering OO unusuable. Opening M$ Word docs or OO docs doesn't matter. This breakage is identical on all of my systems I run OO 2.3.1 on, they all have in common running FreeBSD 7.0-PRE, being 64 Bit, having diablo-1.5-JDK installed. This behaviour even occurs on a freshly installed box. Any ideas? This is a serious situation to me, due to the need of a properly working OO :-( Regards, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Imap authentication
Chris Kottaridis [EMAIL PROTECTED] writes: I have been using pop to download email messages. I'd like to switch to imap. My mail server is running FreeBSD 5.3 The imap executable is in /usr/local/libexec and inetd.conf is setup right. I can telnet to port 143 I am talking to the imapd daemon. However, I can't seem to get logged in. It seems to not like the username and password I provide. I am providing the username and password that will work to login interactively to the server. I assume there is a different authentication method besides the standard password file, but as yet I haven't been able to find what that might be. Clearly I am missing something here. Any pointers to how to set up imap accounts on the mail server would be appreciated. It depends on the particular IMAP server you are using. Most of them will (by default) authenticate against the system password file. The best hints are probably to be found in the log file, but you might need to configure the daemon for greater verbosity first. With dovecot, I used verbose_ssl = yes to do so. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS issues ??
Chris Maness wrote: I am trying to mount a Linux box with NFS from my FreeBSD box, with the command: # mount_nfs4 192.168.1.66:/home/chris/ /mnt/nfs/ where the IP is the Linux box and the share is /home/chris When I run the command I get: mount_nfs4: /mnt/nfs: No such file or directory Now /mnt/nfs exists and is writable. Running showmount returns: # showmount -e 192.168.1.66 /home/chrisns1 Very strange, I have done this in the past with no problems. Any suggestions? Are you certain you used NFSv4? It's more likely you used NFSv3 or v2. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Resolution too high with 7-RC1, nVidia, xorg
I am having trouble getting X to use a screen resolution that is less than the maximum. When I edit my xorg.conf to add a DefaultDepth and a Mode of 1024x768, it still comes up at 1280x1024. I did not create any modeline entries yet, since I'm not sure how to do that. My GUI (icewm) works, but browsing the web creates enormous eye-strain from the high-resolution letters. My hardware is a Dell Inspiron 530 Desktop with an nVidia Card. It comes with SATA CD's, so I have to install with FreeBSD 7-RC1. I started by running xorg -configure, and used the xorg.conf that it generated. I looked at /var/log/Xorg.0.log, and it had many entries from probing my hardware. It appears there is some kind of dynamic configuration going on, but I know its using the xorg.conf, because it got an error when I changed the adapter entry from nv to vga. I actually had a similar problem on Ubuntu, and they had some xorg-reconfigure program that would let you use less than maximum values. I was wondering if FreeBSD had something similar. The DefaultDepth 24 and Modes 1024x786 entries are from the online FreeBSD Handbook, I believe I followed the Handbook instructions properly. Am I missing something obvious? From using Linux, I was expecting the Modes values to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
Xn == Xn Nooby [EMAIL PROTECTED] writes: Xn I am having trouble getting X to use a screen resolution that is less Xn than the maximum. When I edit my xorg.conf to add a DefaultDepth and Xn a Mode of 1024x768, it still comes up at 1280x1024. I did not Xn create any modeline entries yet, since I'm not sure how to do that. Xn My GUI (icewm) works, but browsing the web creates enormous eye-strain Xn from the high-resolution letters. Xn My hardware is a Dell Inspiron 530 Desktop with an nVidia Card. It Xn comes with SATA CD's, so I have to install with FreeBSD 7-RC1. Xn I started by running xorg -configure, and used the xorg.conf that it Xn generated. I looked at /var/log/Xorg.0.log, and it had many entries Xn from probing my hardware. It appears there is some kind of dynamic Xn configuration going on, but I know its using the xorg.conf, because it Xn got an error when I changed the adapter entry from nv to vga. Xn I actually had a similar problem on Ubuntu, and they had some Xn xorg-reconfigure program that would let you use less than maximum Xn values. I was wondering if FreeBSD had something similar. Xn The DefaultDepth 24 and Modes 1024x786 entries are from the Xn online FreeBSD Handbook, I believe I followed the Handbook Xn instructions properly. Xn Am I missing something obvious? From using Linux, I was expecting the Xn Modes values to work. TargetRefresh, and PreferredMode options, available in recent Xorg releases (probably since 7.2), you'll require. I'm using TargetRefresh (75 Hz) on my Intel 945G graphics to set my monitor to display 1440x900 rather than 1280x1024. And this same configuration is working fine for both FreeBSD 7.0-BETA4 (amd64), and Ubuntu 7.10 (amd64). HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- pgpLpiBuDw85c.pgp Description: PGP signature
Re: Problems with OpenOffice 2.3.1 on FreeBSD
Philipp Ost writes: Any ideas? This is a serious situation to me, due to the need of a properly working OO :-( No, perhaps using an other word processor (AbiWord, StarOffice). Or going back to OOo 2.3.0... This has been discussed within the last two weeks on the openoffice@ list. A message from Peter Jeremy on December 14 contains both information about the cause and a patch. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
Dear Xn Nooby, Im not sure if there is such a tool to edit xorg.conf file and limit the maximum resolution. In gnome desktop there is a graphical tool to switch resolution (System - Preferences - Screen Resolution) To make things obvious you will have to take a look at your xorg.conf file Please do change dir to its parent folder (cd /etx/X11/) and run cat xorg.conf | tr -s \n | grep -v # that should make your xorg.conf look simple and clear. There is a sample output below. It is a working xorg.conf Take a look at the section Screen It has Identifier, Device, Monitor, DefaultDepth options and 3 Subsections named Display for each depth where the screen resolution modes are listed: 1024 x 7 6 8 - 800 x 600 640x480 Hint: One of the following key sequence switches modes on a running server. CTRL+ALT+KP_- or CTRL+ALT+KP_+ KP_-, KP_+ (those are keypad minus or keypad plus, or gray -/+) Sincerely, Nash Section Module SubSection extmod EndSubSection Loadtype1 Loadfreetype EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/TTF/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath /usr/X11R6/lib/X11/fonts/local/ EndSection Section ServerFlags Option AllowMouseOpenFail False EndSection Section InputDevice Identifier Keyboard1 Driver kbd Option AutoRepeat 500 30 Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Mouse1 Driver mouse Option Device /dev/ums1 Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Philips105B HorizSync 31.5 - 57.0 VertRefresh 50-100 EndSection Section Device Identifier Standard VGA VendorName Unknown BoardName Unknown Driver vga EndSection Section Device Identifier S3G IGP PRO Driver vesa EndSection Section Screen Identifier Screen 1 Device S3G IGP PRO Monitor Philips105B DefaultDepth 24 Subsection Display Depth 8 Modes 1024x768 800x600 640x480 ViewPort0 0 EndSubsection Subsection Display Depth 16 Modes 1024x768 800x600 640x480 ViewPort0 0 EndSubsection Subsection Display Depth 24 Modes 1024x768 800x600 640x480 ViewPort0 0 EndSubsection EndSection Section ServerLayout Identifier Simple Layout Screen Screen 1 InputDevice Mouse1 CorePointer InputDevice Keyboard1 CoreKeyboard EndSection - Original Message From: Xn Nooby [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Tuesday, January 1, 2008 2:01:47 PM Subject: Resolution too high with 7-RC1, nVidia, xorg I am having trouble getting X to use a screen resolution that is less than the maximum. When I edit my xorg.conf to add a DefaultDepth and a Mode of 1024x768, it still comes up at 1280x1024. I did not create any modeline entries yet, since I'm not sure how to do that. My GUI (icewm) works, but browsing the web creates enormous eye-strain from the high-resolution letters. My hardware is a Dell Inspiron 530 Desktop with an nVidia Card. It comes with SATA CD's, so I have to install with FreeBSD 7-RC1. I started by running xorg -configure, and used the xorg.conf that it generated. I looked at /var/log/Xorg.0.log, and it had many entries from probing my hardware. It appears there is some kind of dynamic configuration going on, but I know its using the xorg.conf, because it got an error when I changed the adapter entry from nv to vga. I actually had a similar problem on Ubuntu, and they had some xorg-reconfigure program that would let you use less than maximum values. I was wondering if FreeBSD had something similar. The DefaultDepth 24 and Modes 1024x786 entries are from the online FreeBSD Handbook, I believe I followed the Handbook instructions properly. Am I missing something obvious? From using Linux, I was expecting the Modes values to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] 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: Resolution too high with 7-RC1, nVidia, xorg
On Jan 1, 2008 10:11 AM, Ashish Shukla आशीष शुक्ल [EMAIL PROTECTED] wrote: Xn == Xn Nooby [EMAIL PROTECTED] writes: Xn I am having trouble getting X to use a screen resolution that is less Xn than the maximum. When I edit my xorg.conf to add a DefaultDepth and Xn a Mode of 1024x768, it still comes up at 1280x1024. I did not Xn create any modeline entries yet, since I'm not sure how to do that. Xn My GUI (icewm) works, but browsing the web creates enormous eye-strain Xn from the high-resolution letters. Xn My hardware is a Dell Inspiron 530 Desktop with an nVidia Card. It Xn comes with SATA CD's, so I have to install with FreeBSD 7-RC1. Xn I started by running xorg -configure, and used the xorg.conf that it Xn generated. I looked at /var/log/Xorg.0.log, and it had many entries Xn from probing my hardware. It appears there is some kind of dynamic Xn configuration going on, but I know its using the xorg.conf, because it Xn got an error when I changed the adapter entry from nv to vga. Xn I actually had a similar problem on Ubuntu, and they had some Xn xorg-reconfigure program that would let you use less than maximum Xn values. I was wondering if FreeBSD had something similar. Xn The DefaultDepth 24 and Modes 1024x786 entries are from the Xn online FreeBSD Handbook, I believe I followed the Handbook Xn instructions properly. Xn Am I missing something obvious? From using Linux, I was expecting the Xn Modes values to work. TargetRefresh, and PreferredMode options, available in recent Xorg releases (probably since 7.2), you'll require. I'm using TargetRefresh (75 Hz) on my Intel 945G graphics to set my monitor to display 1440x900 rather than 1280x1024. And this same configuration is working fine for both FreeBSD 7.0-BETA4 (amd64), and Ubuntu 7.10 (amd64). HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- When I create a PreferredMode value, the X-Server hangs when I run startx. I cannot end X with ctrl-alt-backspace, but I can reboot with ctrl-alt-del. I am using xorg 7.3 (installed via 'pkg_add -r xorg'), and this was apparently a known bug. I'm not sure if it is supposed to be fixed in now, the bug was from September: http://bugs.freedesktop.org/show_bug.cgi?id=12476 I also tried TargetRefresh with values of 60 and 75, but it did not seem to do anything. When you use TargetRefresh, is that with the Horizontal and Vertical refresh values - or does it replace them? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
Here are the values I am experimenting with: The Monitor Section: Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model # Option PreferredMode 1024x768 # HorizSync 24-80 # VertRefresh 56-75 # Option TargetRefresh 60 EndSection A snippet from the Screen Section: SubSection Display Viewport 0 0 Depth 24 Modes 1024x768 EndSubSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
To make things obvious you will have to take a look at your xorg.conf file Please do change dir to its parent folder (cd /etx/X11/) and run cat xorg.conf | tr -s \n | grep -v # that should make your xorg.conf look simple and clear. Here is mine, which still wont go in to 1024x768 mode: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/local/share/X11/rgb ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ FontPath /usr/local/lib/X11/fonts/TrueType/ EndSection Section Module Load GLcore Load dbe Load dri Load extmod Load glx Load record Load xtrap Load freetype Load type1 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync 24.0 - 80.0 VertRefresh 56.0 - 75.0 Option TargetRefresh 60 EndSection Section Device Identifier Card0 Driver nv VendorName nVidia Corporation BoardName GeForce 8300 GS BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 Modes 1024x768 800x600 EndSubSection EndSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
a customized sysinstall
Hi, I am looking a way in to integrating a afterinstall scripts/files in to standart FreeBSD sysinstall program. What I think is to add a new distribution (like src,ports,doc,local..) to FreeBS, create ISO and after that run after-install script on the chrooted directory. Can anyone suggest me where to look ? (URL or whatever that may be useful) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a customized sysinstall
Omer Faruk Sen wrote: Hi, I am looking a way in to integrating a afterinstall scripts/files in to standart FreeBSD sysinstall program. What I think is to add a new distribution (like src,ports,doc,local..) to FreeBS, create ISO and after that run after-install script on the chrooted directory. Can anyone suggest me where to look ? (URL or whatever that may be useful) Look in src/usr.sbin/sysinstall/ and src/release/ Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nagios + 6.3-RELEASE == Hung Process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 G'day ... Yesterday, I setup nagios to do some system monitoring ... installed the latest version from ports into a jail, so that I could easily move it around between machines as I upgrade, without losing data ... after about 30 minutes running, I get a second nagios process running (fork?) that takes up ch CPU time as is available, and just hangs there until I kill -9 it ... Figuring that it might be a problem with the jail (trying to access somethign that isn't available to the process in a jail), I moved it to the physical server level ... but, again, after ~30 minutes, its doing the same thing: # ps aux | grep nagios nagios 32065 73.2 0.1 10948 3516 ?? R11:15AM 7:40.77 /usr/local/bin/nagios -d /usr/local/etc/nagios/nagios.cfg nagios 82120 0.0 0.1 10948 3580 ?? Ss 10:47AM 0:01.18 /usr/local/bin/nagios -d /usr/local/etc/nagios/nagios.cfg So, definitely not jail related ... I've tried to do a 'truss -p 32065', it just hangs. And: ktrace -f /tmp/output -p 32065 ... produces nothing: # kdump -f /tmp/output 32065 nagios PSIG SIGKILL SIG_DFL Once I kill -9 the process, a bunch of 'check_ping' processes start up and then things go back to normal ... My last kernel / world build on that box is: Mon Nov 12 06:43:30 AST 2007 After searching the 'Net a bit, came across this thread: http://www.nagiosexchange.org/nagios-users.34.0.html?tx_maillisttofaq_pi1%5Bmode%5D=1tx_maillisttofaq_pi1%5BshowUid%5D=7694 That recommends modifying libmap.conf with: [/usr/local/bin/nagios] libpthread.so.2 libthr.so.2 libpthread.so libthr.so This seems to fix the problem on the physical server, and am currently testing it in the jail itself to make sure it fixes it there too ... Should this be something that is more prominently documented somewhere? Maybe in the port itself? azureus has similar problems that are fixed with entries in libmap.conf, so its not just a nagios issue ... - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHemsH4QvfyHIvDvMRApUOAKCLRDnmRba6ho4St8qZ6U19V8yJ+wCghMBp Xph3ac9d7QsMjeKBMtmgkuw= =mXxF -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
abcde and uppercase filenames
Hello, Happy New Year. I'm running abcde 2.3.3 port on FreeBSD 6.x. I'm wanting to convert all uppercase paths/filenames in my output from first character uppercase or whatever character is uppercase, to all lowercase. I first uncommented the mungegenre function in /usr/local/etc/abcde.conf, that didn't do it. I then replaced the tr call with A-Z a-z This gave me the same results, first letter of each word or filename path uppercase. If anyone has a fix i'd like to hear about it. Thanks. Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
Xn == Xn Nooby [EMAIL PROTECTED] writes: To make things obvious you will have to take a look at your xorg.conf file Please do change dir to its parent folder (cd /etx/X11/) and run cat xorg.conf | tr -s \n | grep -v # that should make your xorg.conf look simple and clear. Xn Here is mine, which still wont go in to 1024x768 mode: You've 3 options: Xn SubSection Display Xn Viewport 0 0 Xn Depth 24 Xn Modes 1024x768 800x600 1. How about appending 1280x1024 to the above line. AFAIK, these modes are listed in the order of preference. See, if it works. 2. Another thing you can try, is to change the VertRefresh, and HorizRefresh limits of your monitor, change them in such a way, so that X server won't be able to display 1280x1024 mode, resulting in switch to 1024x768 mode. Since 1280x1024 requires a lower refresh rate as compared to 1024x768, so .e.g. if 1280x1024 works on 60 Hz (vertical refresh rate), and 1024x768 is available in 60 Hz, 75 Hz, 85 Hz, then you can increase lower limit of VertRefresh, to something greater than 60. 3. Another thing you can try is mode setting, switch to 1024x768 using xrandr. And then use xvidtune -show to generate modeline, [EMAIL PROTECTED] ~ $ xrandr -s 1024x768 Now, in 1024x768 mode, enter this: [EMAIL PROTECTED] ~ $ xvidtune -show 1024x768136.75 1024 1536 1688 1936768 903 909 942 -hsync +vsync NOTE: Don't use above modeline, thats from 1440x900 resolution, except that I changed 1440, 900 to 1024, 768 respectively :) . Now copy above modeline, and add to the Monitor section of your xorg.conf as show below: ModeLine1024x768 136.75 1024 1536 1688 1936 768 903 909 942 -hsync +vsync HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- pgpahEdD7MnMW.pgp Description: PGP signature
sendmail is broken, how do I fix
Hello, I'm not sure what I did. I've been following instructions (really!) and after following the instructions from here: http://www.puresimplicity.net/~hemi/freebsd/sendmail.html to setup SSL/TLS authentication for mail relaying, my sendmail installation always gives me this very frustrating messages in /var/log/maillog: Jan 1 11:24:27 whitbap sm-mta[3706]: starting daemon (8.13.8): [EMAIL PROTECTED]:30:00 Jan 1 11:24:27 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Jan 1 11:24:27 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket Jan 1 11:24:27 whitbap sm-msp-queue[3710]: starting daemon (8.13.8): [EMAIL PROTECTED]:30:00 Jan 1 11:24:27 whitbap sm-mta[3707]: m010sNBM004564: to=[EMAIL PROTECTED], delay=17:30:04, xdelay=00:00:00, mailer=esmtp, pri=1835114, relay=mail02.interchangeusa.com. [63.251.210.81], dsn=4.0.0, stat=Deferred: Connection refused by mail02.interchangeusa.com. Jan 1 11:24:32 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Jan 1 11:24:32 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket Jan 1 11:24:37 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Jan 1 11:24:37 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket Jan 1 11:24:42 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Try as I have, I cannot isolate what is causing this. When I completely kill all sendmail processes (as verified by sockstat and ps -aux) there is *nothing* using port 25. I do not understand what is going on. While following the instructions for smtp authentication in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html I perhaps made one of my blunders. These instructions say to alter the file freebsd.mc rather than hostname.mc. It does say that some admin's like to use hostname.mc, but because I didn't know much about how FreeBSD does the install, I saw freebsd.mc and added the three lines listed in bullet item 6 on that web page. Later, I saw that I did have the file hostname.mc and while researching a resolution to this problem learned that FreeBSD makes the hostname.mc file when doing a make all if memory serves. Anyway, I then removed those three lines from freebsd.mc and pasted them into hostname.mc. Regardless, when I had those three lines in freebsd.mc everything worked. I made the changes for SSL/TLS as Josh Tolbert lays out in his web site (see above link) and when I restarted sendmail, that's when my troubles began. I don't understand what it is that I did and how it made it so that sendmail now thinks something else is using the socket/address. I'm desperate for a solution. Thanks for any help. Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nagios + 6.3-RELEASE == Hung Process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marc G. Fournier wrote: G'day ... Yesterday, I setup nagios to do some system monitoring ... installed the latest version from ports into a jail, so that I could easily move it around between machines as I upgrade, without losing data ... after about 30 minutes running, I get a second nagios process running (fork?) that takes up ch CPU time as is available, and just hangs there until I kill -9 it ... [ .. ] After searching the 'Net a bit, came across this thread: http://www.nagiosexchange.org/nagios-users.34.0.html?tx_maillisttofaq_pi1%5Bmode%5D=1tx_maillisttofaq_pi1%5BshowUid%5D=7694 That recommends modifying libmap.conf with: [/usr/local/bin/nagios] libpthread.so.2 libthr.so.2 libpthread.so libthr.so Thanks for pointing this out. I've had similar problems with nagios but hadn't found a solution until I saw your pointer. Sadly, my expertise with both thread libraries is sufficiently lacking that I have no clue where to start looking for the cause :-( Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHenK4Qv9rrgRC1JIRAqifAKChinXb0dEPTMMlnXNYsuECLJL+vgCgvLF5 G5UYcIuvPe+UEk+qJSplrnY= =xXMF -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
I was able to temporarily change the resolution using the xrandr -s 1024x768 command - but xvidtune -show still displayed a modeline that begins with 1280x1024. I copied that modeline to my xorg.conf, and manually changed the resolution, but I did not fool it. It was great to see the screen at 1024x768, so I know it can do it. I added a 1280x1024 mode to my xorg.conf display list, and it not change the behavior. I was able to get 1280x960 by increasing the lower range for VertRefresh to 70, and was able to get 800x600 by increasing it to 75. I then played around with various other VertRefresh values, but had no luck. I also tried the Horizontal values, but the did not help. I'm using a flat-panel screen, so I don't think I can hurt it. I hope! xrandr worked, though my IceWM menubar fell off my screen. xvidtune could probaly fix that, if I could get the ModeLine command to have an effect. On Jan 1, 2008 12:09 PM, Ashish Shukla आशीष शुक्ल [EMAIL PROTECTED] wrote: Xn == Xn Nooby [EMAIL PROTECTED] writes: To make things obvious you will have to take a look at your xorg.conf file Please do change dir to its parent folder (cd /etx/X11/) and run cat xorg.conf | tr -s \n | grep -v # that should make your xorg.conf look simple and clear. Xn Here is mine, which still wont go in to 1024x768 mode: You've 3 options: Xn SubSection Display Xn Viewport 0 0 Xn Depth 24 Xn Modes 1024x768 800x600 1. How about appending 1280x1024 to the above line. AFAIK, these modes are listed in the order of preference. See, if it works. 2. Another thing you can try, is to change the VertRefresh, and HorizRefresh limits of your monitor, change them in such a way, so that X server won't be able to display 1280x1024 mode, resulting in switch to 1024x768 mode. Since 1280x1024 requires a lower refresh rate as compared to 1024x768, so .e.g. if 1280x1024 works on 60 Hz (vertical refresh rate), and 1024x768 is available in 60 Hz, 75 Hz, 85 Hz, then you can increase lower limit of VertRefresh, to something greater than 60. 3. Another thing you can try is mode setting, switch to 1024x768 using xrandr. And then use xvidtune -show to generate modeline, [EMAIL PROTECTED] ~ $ xrandr -s 1024x768 Now, in 1024x768 mode, enter this: [EMAIL PROTECTED] ~ $ xvidtune -show 1024x768136.75 1024 1536 1688 1936768 903 909 942 -hsync +vsync NOTE: Don't use above modeline, thats from 1440x900 resolution, except that I changed 1440, 900 to 1024, 768 respectively :) . Now copy above modeline, and add to the Monitor section of your xorg.conf as show below: ModeLine1024x768 136.75 1024 1536 1688 1936 768 903 909 942 -hsync +vsync HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Extremely slow authentication via SSH on FreeBSD 6.0
First, thank you to others who posted about this issue. I altered /etc/ssh/sshd_config for UseDNS no, and noticed I get the prompt right away, however it still takes about 15 seconds after authentication to get a shell prompt. This is FreeBSD version: FreeBSD 6.3-PRERELEASE #7: Sat Dec 22 11:12:15 EST 2007 I noticed this behavior after the last system build and install. Prior to that, I didn't see problems like this. I don't see this problem with httpd (apache) etc. The DNS servers my ISP provides are quickly reachable and appear to be caching very well, so I doubt that's the issue. Conversely, and perhaps this is a hint, the GW I log in to has this problem, but if I log in from there to an internal system using the same exact version of FreeBSD, I don't have any problems like this at all. The difference being I also use internal DNS as well as /etc/hosts entries. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
G4 Quicksilver as Web Server?
Sup guys. Hope you all had a new year. I have an old G4 lying about, its got 256mb ram, 733mhz processor. I was wondering, would it be worth setting up the PPC version of FreeBSD (or maybe even OpenBSD, although thats for their mailing list) on it to use as a web server or testing box. The most i'd do on it is probably use it as a testing box to create server applications using C++. Id like ot work within a BSD enviroment because thats what ive been using for a long time now, but i dont want all the extra windows crap you get with OSX, id much rather work with command line. I havn't got an old PC lying about, and because of university i need to keep my PC intact with XP (assignments, research ect.). Before i end the toipic, anyone got any feeback on the Asus Eee (mini laptops) with FreeBSD? Im open to any feedback. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS issues ??
Kris Kennaway wrote: Chris Maness wrote: I am trying to mount a Linux box with NFS from my FreeBSD box, with the command: # mount_nfs4 192.168.1.66:/home/chris/ /mnt/nfs/ where the IP is the Linux box and the share is /home/chris When I run the command I get: mount_nfs4: /mnt/nfs: No such file or directory Now /mnt/nfs exists and is writable. Running showmount returns: # showmount -e 192.168.1.66 /home/chrisns1 Very strange, I have done this in the past with no problems. Any suggestions? Are you certain you used NFSv4? It's more likely you used NFSv3 or v2. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You were correct, I think the Linux kernel version is not nfs4. When I tried mount_nfs instead of mount_nfs4 it worked as advertised. Thanks, -- Chris Maness (909) 223-9179 http://www.chrismaness.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with OpenOffice 2.3.1 on FreeBSD
O. Hartmann wrote: [...] Whenever I try to save a document in OO writer, OO gets stuck and I have to kill it. The document gets saved, but I never can load it again without rendering OO unusuable. Opening M$ Word docs or OO docs doesn't matter. I have similar problems with OpenOffice 2.3.1 on FreeBSD/i386 (I'm running 7.0-PRE as of Dec 23). It's possible to save documents but exiting OOo hangs and I need to kill it. Firing up OOo once again, there's this recovery stuff which hangs also and eats up CPU time. Only way out: kill -9 $PID Opening a document via 'File - Open - ...' hangs also. .odt or .doc doesn't matter. Any ideas? This is a serious situation to me, due to the need of a properly working OO :-( No, perhaps using an other word processor (AbiWord, StarOffice). Or going back to OOo 2.3.0... Regards, Philipp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports 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]
Intel 3945 wpi driver doesn't seem to work ('cause of license problems???)
Context: Router ZyXEL ADSL+2 with dhcp up and running Laptop HP Pavillion Entertainment DV6000 intel centrino duo 2GB of memory hpbsd# uname -a FreeBSD hpbsd.vic 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Thu Dec 27 22:18:53 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HP03 i386 hpbsd# all wpi's necessary devices are compiled in the kernel device wpi device pci device wlan device wlan_amrr device firmware /var/log/messages kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xd800-0xd8000fff irq 16 at device 0.0 on pci2 kernel: wpi0: Ethernet address: 00:19:d2:99:e3:cb kernel: wpi0: [ITHREAD] kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps the line legal.intel_wpi.license_ack=1 is in /boot/loader.conf BUT 1) it seems that sysctl is unable to find it and I have to set it via kenv legal.intel_wpi.license_ack=1 Shouldn't this variable be set by sysctl or by loader.conf? 2) dhclient is unable to get an IP address (trying to set wpi0 up with a fixed IP makes wpi0 not associated to any AP) Here it is a session log SNIP hpbsd# sysctl -a|grep legal hpbsd# hpbsd# kenv legal.intel_wpi.license_ack=1 legal.intel_wpi.license_ack=1 hpbsd# kenv legal.intel_wpi.license_ack 1 hpbsd# ifconfig wpi0 ssid my_wireless weptxkey 1 wepmode on wepkey 0x1f7b0a5a0d hpbsd# dhclient wpi0 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 5 No DHCPOFFERS received. No working leases in persistent database - sleeping. hpbsd# ifconfig wpi0 wpi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:19:d2:99:e3:cb inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: associated ssid my_wireless channel 6 (2437 Mhz 11g) bssid 00:02:cf:61:81:fd authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit txpower 50 bmiss 7 scanvalid 60 protmode CTS /SNIP Even giving an ip fixed address to wpi0 doesn't seem to work, I cannot ping anything and for netstat -rn wpi0 doesn't seem to exist. Please help Ciao from Rome -- Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
Xn == Xn Nooby [EMAIL PROTECTED] writes: Xn I was able to temporarily change the resolution using the xrandr -s Xn 1024x768 command - but xvidtune -show still displayed a modeline Xn that begins with 1280x1024. I copied that modeline to my xorg.conf, Xn and manually changed the resolution, but I did not fool it. It was Xn great to see the screen at 1024x768, so I know it can do it. Hmm..., this is strange. BtW, after adding modeline, you need to restart Xorg. Anyways to get modeline for 1024x768 you can try switching to 'vesa' driver temporarily, extract modeline for 1024x768 From there, and then enter that modeline in xorg.conf. I tried this method when I'm having problem setting my old 15 LG Studioworks 452V to display 1024x768 without getting clipped. HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- pgpqsemdONtz7.pgp Description: PGP signature
Re: Problems with OpenOffice 2.3.1 on FreeBSD
Philipp Ost wrote: O. Hartmann wrote: [...] Whenever I try to save a document in OO writer, OO gets stuck and I have to kill it. The document gets saved, but I never can load it again without rendering OO unusuable. Opening M$ Word docs or OO docs doesn't matter. I have similar problems with OpenOffice 2.3.1 on FreeBSD/i386 (I'm running 7.0-PRE as of Dec 23). It's possible to save documents but exiting OOo hangs and I need to kill it. Firing up OOo once again, there's this recovery stuff which hangs also and eats up CPU time. Only way out: kill -9 $PID Opening a document via 'File - Open - ...' hangs also. .odt or .doc doesn't matter. Any ideas? This is a serious situation to me, due to the need of a properly working OO :-( No, perhaps using an other word processor (AbiWord, StarOffice). Or going back to OOo 2.3.0... Regards, Philipp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports 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] I am not an OpenOffice user but my 2c about the topic as the problem I think underline more serous issue. The question is why is OpenOffice 2.3.1 included in the ports three so quickly without making sure that things work properly. BSD systems are genuinely known for their stability and code correctness which is why most people decided to use them on the first place. Rushing to include new software in the ports three without proper testing is seriously going to damage usability of the whole OS. In my understanding ports tree is supporting stable and the current brunch. I am of the opinion that the ports three of the stable branch should not include nothing but the rock solid and tested software. The easiest way for me to check if the port is bleeding edge that is to try to install the same software using binaries. (pkg_add -r) If the binaries do not exist or if the version installed from binaries is older that clearly indicates that the port version is too new to be trusted. I personally found out that Xfce4-panel is not compiling properly on stable and also Orage (calendar for Xfce) While problems with Xfce4-panel are not as serious as with Orage (which is not usable in any shape or form on FreeBSD) they are still serious. The same packages work flawlessly on the OpenBSD. Happy New Year to Everybody Predrag ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with OpenOffice 2.3.1 on FreeBSD
Robert Huff wrote: Philipp Ost writes: Any ideas? This is a serious situation to me, due to the need of a properly working OO :-( No, perhaps using an other word processor (AbiWord, StarOffice). Or going back to OOo 2.3.0... This has been discussed within the last two weeks on the openoffice@ list. A message from Peter Jeremy on December 14 contains both information about the cause and a patch. Robert Huff ___ I am not an OpenOffice user but my 2c about the topic as the problem I think underline more serous issue. The question is why is OpenOffice 2.3.1 included in the ports three so quickly without making sure that things work properly. BSD systems are genuinely known for their stability and code correctness which is why most people decided to use them on the first place. Rushing to include new software in the ports three without proper testing is seriously going to damage usability of the whole OS. In my understanding ports tree is supporting stable and the current brunch. I am of the opinion that the ports three of the stable branch should not include nothing but the rock solid and tested software. The easiest way for me to check if the port is bleeding edge that is to try to install the same software using binaries. (pkg_add -r) If the binaries do not exist or if the version installed from binaries is older that clearly indicates that the port version is too new to be trusted. I personally found out that Xfce4-panel is not compiling properly on stable and also Orage (calendar for Xfce) While problems with Xfce4-panel are not as serious as with Orage (which is not usable in any shape or form on FreeBSD) they are still serious. The same packages work flawlessly on the OpenBSD. Happy New Year to Everybody Predrag [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports 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: Resolution too high with 7-RC1, nVidia, xorg
Hmm..., this is strange. BtW, after adding modeline, you need to restart Xorg. Anyways to get modeline for 1024x768 you can try switching to 'vesa' driver temporarily, extract modeline for 1024x768 From there, and then enter that modeline in xorg.conf. I tried this method when I'm having problem setting my old 15 LG Studioworks 452V to display 1024x768 without getting clipped. Using the vesa driver worked - I am able to get 1024x768, though the fonts are a little weird. I tried to use the modeline from the vesa driver with nv, but it didn't work. If the nv driver is part of the problem, I will try the native nVidia driver and see how that works. I've been shutting down and restarting X everytime I try something. I made a xorg.conf with the vesa selected by running xorgconfig. Ill try the native driver and see what happens. thanks for all the help so far! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with OpenOffice 2.3.1 on FreeBSD
Predrag Punosevac wrote: Philipp Ost wrote: O. Hartmann wrote: [...] Whenever I try to save a document in OO writer, OO gets stuck and I have to kill it. The document gets saved, but I never can load it again without rendering OO unusuable. Opening M$ Word docs or OO docs doesn't matter. I have similar problems with OpenOffice 2.3.1 on FreeBSD/i386 (I'm running 7.0-PRE as of Dec 23). It's possible to save documents but exiting OOo hangs and I need to kill it. Firing up OOo once again, there's this recovery stuff which hangs also and eats up CPU time. Only way out: kill -9 $PID Opening a document via 'File - Open - ...' hangs also. .odt or .doc doesn't matter. Any ideas? This is a serious situation to me, due to the need of a properly working OO :-( No, perhaps using an other word processor (AbiWord, StarOffice). Or going back to OOo 2.3.0... Regards, Philipp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports 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] I am not an OpenOffice user but my 2c about the topic as the problem I think underline more serous issue. The question is why is OpenOffice 2.3.1 included in the ports three so quickly without making sure that things work properly. BSD systems are genuinely known for their stability and code correctness which is why most people decided to use them on the first place. Rushing to include new software in the ports three without proper testing is seriously going to damage usability of the whole OS. In my understanding ports tree is supporting stable and the current brunch. I am of the opinion that the ports three of the stable branch should not include nothing but the rock solid and tested software. The easiest way for me to check if the port is bleeding edge that is to try to install the same software using binaries. (pkg_add -r) If the binaries do not exist or if the version installed from binaries is older that clearly indicates that the port version is too new to be trusted. I personally found out that Xfce4-panel is not compiling properly on stable and also Orage (calendar for Xfce) While problems with Xfce4-panel are not as serious as with Orage (which is not usable in any shape or form on FreeBSD) they are still serious. The same packages work flawlessly on the OpenBSD. The problem is that ports is maintained by volunteers who are mostly outside of any kind of freebsd core team. I think it is unrealistic to ask port committers to check anything more than to check that the ports build properly. My personal wish list is that opencascade builds on FreeBSD-7 with the new stlport, and that octave-forge not be in its current IGNORE state. But I fully appreciate that I must either wait, or help make it happen. Stephen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
Xn == Xn Nooby [EMAIL PROTECTED] writes: Xn Using the vesa driver worked - I am able to get 1024x768, though the Xn fonts are a little weird. I tried to use the modeline from the vesa Xn driver with nv, but it didn't work. If the nv driver is part of the Xn problem, I will try the native nVidia driver and see how that works. Xn I've been shutting down and restarting X everytime I try something. I Xn made a xorg.conf with the vesa selected by running xorgconfig. Ill try Xn the native driver and see what happens. Following is an excerpt from my xorg.conf with ModeLine, see if you've entered ModeLine properly. -- Section Monitor Identifier Monitor0 ModelNameLCD Panel 1440x900 HorizSync50.0 - 75.0 VertRefresh 60.0 - 85.0 Option dpms ModeLine[EMAIL PROTECTED]136.75 1440 1536 1688 1936900 903 909 942 -hsync +vsync DisplaySize 408.94 254.0 Option TargetRefresh 75.0 EndSection Section Device Identifier Videocard0 Driver intel EndSection Section Screen Identifier Screen0 Device Videocard0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 Modes[EMAIL PROTECTED] 1024x768 800x600 640x480 [EMAIL PROTECTED] EndSubSection EndSection - HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- pgpufzX4sNUnV.pgp Description: PGP signature
Re: Problems with OpenOffice 2.3.1 on FreeBSD
On Tue, Jan 01, 2008 at 10:41:57AM -0500, Robert Huff wrote: This has been discussed within the last two weeks on the openoffice@ list. A message from Peter Jeremy on December 14 contains both information about the cause and a patch. My patch was for a different problem - related to OOo not opening any files. I'm not currently in a position to verify but I don't believe that the patch I made is related to O.Hartmann's problem. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpDkXfzC6i6L.pgp Description: PGP signature
Howcome mail deletion time varies?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I use, for my imap-based mail, a combination of postfix, dovecot, thunderbird, enigmail (for gnupg), and openssl for browser security. When I delete mail messages, the majority of them delete (what seems to me to be) instantaneously, but a small minority of mails takes quite a bit longer, about maybe 20 seconds. Any idea what might be occurring on those mails, to trigger this really long delete time? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHeqUHz62J6PPcoOkRAkTBAJ4uljFiG/fUZZHt/W85bpfI40HRuQCeK+z3 YM43v/HyD+gywhUUNkfsAe8= =Whoq -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with OpenOffice 2.3.1 on FreeBSD
Le Mar 1 jan 08 à 21:21:43 +0100, Stephen Montgomery-Smith [EMAIL PROTECTED] écrivait : My personal wish list is that opencascade builds on FreeBSD-7 with the new stlport, and that octave-forge not be in its current IGNORE state. But I fully appreciate that I must either wait, or help make it happen. A patch is ready for that, and is available at http://people.freebsd.org/~thierry/ports/opencascade.diff but I cannot commit it right now: it will fail without the patch included in PR ports/118958. That means that we have to wait untill the ports tree is totally unfrozen. Best regards, -- Th. Thomas. pgpH41T7RN6Gt.pgp Description: PGP signature
DigiBoard Classic
Hello All, I have a digiboard classic PCI, and I am trying to build a system to monitor many serial systems (UPSes) using FreeBSD. I cannot find any documentation referring to this driver -- it seems that everything digi related in the BSD tree refers to the intelligent cards, whereas the ClassicBoard is not intelligent, but does manage to do interrupt sharing. (It's also frequently available on ebay, which makes it an ideal candidate for experimentation). Linux drivers are here: http://www.digi.com/support/productdetl.jsp?pid=1694osvid=102tp=1 I'm going to try basing some tests on COM_MULTIPORT and on best-guesses for configs, however I'd really love to hear from anyone who knows for sure if this board will work or not. If someone can read C and feels like having a quick LOOK at the driver (or at my test system), I could try to compensate you for some time. -Dan Mahoney -- Tonite on reboot! People misspelling as many words with sexual connotations as possible... -Keyo-Chan, February 10th 1999, Undernet #reboot 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]
Re: Problems with OpenOffice 2.3.1 on FreeBSD
Peter Jeremy writes: This has been discussed within the last two weeks on the openoffice@ list. A message from Peter Jeremy on December 14 contains both information about the cause and a patch. My patch was for a different problem - related to OOo not opening any files. I'm not currently in a position to verify but I don't believe that the patch I made is related to O.Hartmann's problem. I just turned around and there conclusions were. Sorry about that. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Future development of Jail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You mean like: http://wiki.freebsd.org/JailResourceLimits and: http://docs.freevps.com/doku.php?id=freebsd:index - --On Monday, December 31, 2007 19:10:51 -0800 Karl Triebes [EMAIL PROTECTED] wrote: On Dec 31, 2007 5:51 PM, Andy Dills [EMAIL PROTECTED] wrote: Not that I have a pile of money laying around I could throw at it, but the thing I wish for most from FreeBSD is a more mature and robust jail implementation. Specifically, the ability to implement per-jail quotas and resource limitations on disk, memory, network and cpu. I'd really love a seperate network stack for each jail...that's critical for a plethora of reasons. I'd be curious what sort of commitment (in $) that would require. I would like to see per-jail quotas such as the ones Andy mentions, and would like to hear if anyone would be interested in doing it for the right price. You may contact me via this list or in private. Cheers, and, a happy New Year. Karl. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHeraV4QvfyHIvDvMRApXeAJ9K+cwH1U8DKc7BbPOZKEOS8QwwQQCg4jbB HgqqfQWVKfMmM73Wj7+FN44= =WYax -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with OpenOffice 2.3.1 on FreeBSD
O. Hartmann wrote: I use OpenOffice 2.3.1 on several hardwareplatforms running FreeBSD 7.0-PRE/AMD64 and since I upgraded OpenOffice from OO 2.3.0 to 2.3.1 I have massive problems, rendering OO unusuable! Before doing a PR I would like to aks whethere there is a solution out. Whenever I try to save a document in OO writer, OO gets stuck and I have to kill it. The document gets saved, but I never can load it again without rendering OO unusuable. Opening M$ Word docs or OO docs doesn't matter. This breakage is identical on all of my systems I run OO 2.3.1 on, they all have in common running FreeBSD 7.0-PRE, being 64 Bit, having diablo-1.5-JDK installed. This behaviour even occurs on a freshly installed box. Any ideas? This is a serious situation to me, due to the need of a properly working OO :-( Regards, Oliver ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports 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] I had a similar problem on my i386 - openoffice would hang using lots of CPU when opening or saving a file. After a recent ports update (csup/portmanager) it has gone away. %uname -a FreeBSD eco 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Mon Dec 31 00:44:10 GMT 2007 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKRNL01 i386 %pkg_info -Ix openoffice en-openoffice.org-GB-2.3.1 %head -5 /usr/ports/editors/openoffice.org-2/Makefile # New ports collection makefile for: OpenOffice.org # Date created: 28 February 2002 # Whom: Martin Blapp # # $FreeBSD: ports/editors/openoffice.org-2/Makefile,v 1.292 2007/12/07 23:55:16 maho Exp $ Also I am using java/jdk15 not java/diablo-jdk15. Somehow I did manage to save a file with the faulty port. When I tried to open it with the later version it did the same trick but on second opening it worked fine. portmanager will create packages as well so you can roll them out to the other machines. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution too high with 7-RC1, nVidia, xorg
Well, after 15 hours of experimenting, I have 1024x768 working! Getting PreferredMode to work was the main thing, I think. It was literally on my last try, before I reinstalled Ubuntu, that I got it to work, lol. Maybe these note will be of value to another nooby. thanks again! There 3 things that I needed: 1) A modeline from the Modeline Calculator website 2) To use the RefreshRate in the PreferredMode option 3) To use the RefreshRate in the Modes line Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model Modeline [EMAIL PROTECTED] 64.56 1024 1056 1296 1328 768 783 791 807 Option PreferredMode [EMAIL PROTECTED] EndSection DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 Modes [EMAIL PROTECTED] EndSubSection On Jan 1, 2008 3:23 PM, Ashish Shukla आशीष शुक्ल [EMAIL PROTECTED] wrote: Xn == Xn Nooby [EMAIL PROTECTED] writes: Xn Using the vesa driver worked - I am able to get 1024x768, though the Xn fonts are a little weird. I tried to use the modeline from the vesa Xn driver with nv, but it didn't work. If the nv driver is part of the Xn problem, I will try the native nVidia driver and see how that works. Xn I've been shutting down and restarting X everytime I try something. I Xn made a xorg.conf with the vesa selected by running xorgconfig. Ill try Xn the native driver and see what happens. Following is an excerpt from my xorg.conf with ModeLine, see if you've entered ModeLine properly. -- Section Monitor Identifier Monitor0 ModelNameLCD Panel 1440x900 HorizSync50.0 - 75.0 VertRefresh 60.0 - 85.0 Option dpms ModeLine[EMAIL PROTECTED]136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync DisplaySize 408.94 254.0 Option TargetRefresh 75.0 EndSection Section Device Identifier Videocard0 Driver intel EndSection Section Screen Identifier Screen0 Device Videocard0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 Modes[EMAIL PROTECTED] 1024x768 800x600 640x480 [EMAIL PROTECTED] EndSubSection EndSection - HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Changing work directory of port for make
Hey guys, I installed Freebsd 7 on a Dell laptop I have. When I configured the /usr partition I only gave it 10GB of space figuring that would be plenty. Well now, since I don't see a pre-compiled version of OpenOffice for i386, looks like I have to compile it myself. No big deal, except when I go to compile it I run out of disk space on /usr. Is there a way I can tell make to create it's work directory someplace else? I have more space in home, so if I make a /home/work, can I compile OpenOffice to use the /home/work directory instead of /usr/port/editors/openoffice.org-2? I tried creating a link for the work directory but that appears to be over ridden. Thanks for the help, Chad ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing work directory of port for make
On Tue, Jan 01, 2008 at 06:35:43PM -0500, Chad Kellerman wrote: Hey guys, I installed Freebsd 7 on a Dell laptop I have. When I configured the /usr partition I only gave it 10GB of space figuring that would be plenty. Well now, since I don't see a pre-compiled version of OpenOffice for i386, looks like I have to compile it myself. No big deal, except when I go to compile it I run out of disk space on /usr. Is there a way I can tell make to create it's work directory someplace else? I have more space in home, so if I make a /home/work, can I compile OpenOffice to use the /home/work directory instead of /usr/port/editors/openoffice.org-2? I tried creating a link for the work directory but that appears to be over ridden. Sure. Just set the WRKDIRPREFIX make variable in /etc/make.conf to point to the desired directory. This (and much else) is documented in the ports(7) manpage. -- Insert your favourite quote here. Erik Trulsson [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: sendmail is broken, how do I fix
At 11:17 AM 1/1/2008, Andrew Falanga wrote: Hello, I'm not sure what I did. I've been following instructions (really!) and after following the instructions from here: http://www.puresimplicity.net/~hemi/freebsd/sendmail.html to setup SSL/TLS authentication for mail relaying, my sendmail installation always gives me this very frustrating messages in /var/log/maillog: Jan 1 11:24:27 whitbap sm-mta[3706]: starting daemon (8.13.8): [EMAIL PROTECTED]:30:00 Jan 1 11:24:27 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Jan 1 11:24:27 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket Jan 1 11:24:27 whitbap sm-msp-queue[3710]: starting daemon (8.13.8): [EMAIL PROTECTED]:30:00 Jan 1 11:24:27 whitbap sm-mta[3707]: m010sNBM004564: to=[EMAIL PROTECTED], delay=17:30:04, xdelay=00:00:00, mailer=esmtp, pri=1835114, relay=mail02.interchangeusa.com. [63.251.210.81], dsn=4.0.0, stat=Deferred: Connection refused by mail02.interchangeusa.com. Jan 1 11:24:32 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Jan 1 11:24:32 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket Jan 1 11:24:37 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Jan 1 11:24:37 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket Jan 1 11:24:42 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Try as I have, I cannot isolate what is causing this. When I completely kill all sendmail processes (as verified by sockstat and ps -aux) there is *nothing* using port 25. I do not understand what is going on. While following the instructions for smtp authentication in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html I perhaps made one of my blunders. These instructions say to alter the file freebsd.mc rather than hostname.mc. It does say that some admin's like to use hostname.mc, but because I didn't know much about how FreeBSD does the install, I saw freebsd.mc and added the three lines listed in bullet item 6 on that web page. Later, I saw that I did have the file hostname.mc and while researching a resolution to this problem learned that FreeBSD makes the hostname.mc file when doing a make all if memory serves. Anyway, I then removed those three lines from freebsd.mc and pasted them into hostname.mc. Regardless, when I had those three lines in freebsd.mc everything worked. I made the changes for SSL/TLS as Josh Tolbert lays out in his web site (see above link) and when I restarted sendmail, that's when my troubles began. I don't understand what it is that I did and how it made it so that sendmail now thinks something else is using the socket/address. I'm desperate for a solution. Thanks for any help. Andy While you think there is nothing on that port something is running not letting that socket connection. Try rebooting the system and see if the problem is still there. -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]
pIII coppermine?
I have an ABIT VP6 dual socket that I want to use as my FreeBSD server. I only have one CPU installed, and I was told that if I were to add another CPU that the serial numbers of the CPU had to be sequential. Is this true? I see these processors on e-bay for $7 it would be nice to be able to boost the power of this box. Chris Maness ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pIII coppermine?
Hi, Chris Maness wrote: I have an ABIT VP6 dual socket that I want to use as my FreeBSD server. I only have one CPU installed, and I was told that if I were to add another CPU that the serial numbers of the CPU had to be sequential. Is this true? I see these processors on e-bay for $7 it would be nice to be able to boost the power of this box. this is nonsense. What would be helpful is the same stepping number. As the price is low, jsut go for it. Older CPUs needed that both CPU have had to be of the same stepping. Yours is new enough to work with any CPU of the same type. Just make sure that this is the case. Same cache size, same clock rate ... Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Remote control for a multimedia computer
I've been using the computer in my bedroom for watching movies more often lately, and getting out of bed to pause, rewind, and handle volume has gotten more and more annoying. I don't need anything very fancy, but I don't want to do something like use a wireless game controller. I'm not sure about using a wireless keyboard due to size and connectivity, since I imagine the keyboard would also have to be the primary keyboard which would make connectivity annoying with a console. I'd prefer something other than an IR solution due to line of sight issues. Considering how many people are using their computer for home entertainment, I'm surprised at the lack of options. Does anyone on the list know of a good remote that works well with FreeBSD? Or would it be more of an issue of a remote receiver? In any case, what would be the best option? I'm not interested in spending too much money(anything capable of running NetBSD is probably out of the question). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with OpenOffice 2.3.1 on FreeBSD
Am Dienstag, 1. Januar 2008 14:15:40 schrieb O. Hartmann: I use OpenOffice 2.3.1 on several hardwareplatforms running FreeBSD 7.0-PRE/AMD64 and since I upgraded OpenOffice from OO 2.3.0 to 2.3.1 I have massive problems, rendering OO unusuable! Before doing a PR I would like to aks whethere there is a solution out. Whenever I try to save a document in OO writer, OO gets stuck and I have to kill it. The document gets saved, but I never can load it again without rendering OO unusuable. Opening M$ Word docs or OO docs doesn't matter. Just to chime in: the problem has been identical for me since I upgraded to FreeBSD 7 some two months ago. Any OpenOffice.org build I did (2.3.0 and 2.3.1) fails to save and load any form of documents with the exact same symptoms that you describe (i.e., the UI not being responsive anymore after trying to save or load from a file). I used the Sun JDK source build (1.5) to compile OpenOffice.org, not the Diablo JDK by the way, and if anybody is willing to look at this problem deeper, search this list to see a post of mine where I attached gdb to the running (and hung) OpenOffice.org process and gave a backtrace of where the (100%) CPU time is being spent. IIRC it was in some input filter, but I don't really know anymore. I've since moved on to KOffice, but if there's some fix for this, I'm more than happy to try it out. -- 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]
