Re: calcru negative time error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 3 Jun 2003, Jimi Thompson wrote: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIV That web page said to enter this command (which I do not have a good understanding of but did anyway) # sysctl -w kern.timecounter.method=1 which I did, but apparently my 5.0 doesn't like that because it promptly spit back: sysctl: unknown oid 'kern.timecounter.method' I looked at that FAQ page, and right underneath where it lists that command it says the following: Note: The -w option of sysctl(8) is deprecated and silently ignored in FreeBSD 4.4-RELEASE and all newer versions. You can safely ommit it when setting options with sysctl as shown above. I'd give it a try with out the '-w' flag. Although I don't know if it'll fix your issues. Just maybe a step in the right direction. Thanks, Ms. Jimi Thompson, CISSP, Rev. ~Shane Kinney Web: http://www.freebsdhackers.net IRC: irc.freebsdhackers.net #freebsd PGP: http://www.freebsdhackers.net/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+3XyIgsso3QO013ERAqQ5AKCOOAzKidPBCGCJ2W/Jb23nXdCRwACeIzOO T7nUctlbH/J02Ewo7JO/fX0= =bkPR -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vidcontrol(1) FreeBSD 5.0 on Laptop
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey everyone, I just encountered a very strange problem with my notebook thats running 5.0-RELEASE and XFree86. Normally the regular color of the plain VT is a black background with a white forground. I have been running XFree86 on the laptop for about a month. Everynow and then when I close the laptop lid while XFree86 is still running when I re-open the top the screen is black and in some kinda suspend mode. I was meaning to disable this in the BIOS. But the last time it happened, the background of the VT is blue and the forground is black. And if i do this command: `vidcontrol white black`, and it stays with the blue background and the black forground. It's almost as if XFree86 somehow munged the original values for vidcontrol are set to. Do any of you know where these values might be held? Or has anyone seen something like this before? Thanks a ton for any help. ~Shane Kinney Build Ramps, Not Bombs. pgp key: http://www.freebsdhackers.net/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+dganIyUr/yoGQnYRAq4GAJ9iktHkhM/2yEcp9gud76oq8kJGswCfaKZQ USPNuvWMTa+sVfUsruKs+VE= =8LWb -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: open relay server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 27 Feb 2003, Walt wrote: I have a freebsd 4.0 server with sendmail 8.9.3 that is acting as an open relay server now. beginning to get lost after trying so many ways to stop it. any help will be most appreciated. You can upgrade to 8.12.7 from sendmail.org. These newer versions of sendmail make it harder to accidentilly run an open relay. And if your feeling really confident, give Postfix a try. :) http://www.postfix.org. Both of these MTA's are in your ports, but your going to need to `cvsup` your ports tree before you use them (since your version of FreeBSD is rather old). For info on that read this section in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Good luck! ~Shane -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+XjUsIyUr/yoGQnYRAlmtAJ9SjoSBbCirbn55qx+NfKuiMwRvTwCcCoe9 tUyIjTeG1tJcyabOvJqrbIU= =T98M -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Refusing Connections
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OS - 5.0 RC2 Apache - 2.0.43 OpenSSL - 0.9.6g I'm having a rather odd problem and I can't quite put my finger on it. I can verify that the apache httpd is running but I am unable to connect to the box on port 80. I verified that httpd.conf specifies port 80. I've verified that the firewall is disabled. I can connect on other ports so I know that the network settings are working properly.If someone could point out what I'm missing, I'd really appreciate it. I have a feeling that it's going to be a DOH! momemt. Thanks, Ms. Jimi Thompson Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com I think I know what you are trying to say Ms. Thompson. It probably seems that you have gotten your Apache configuration to start and run, however, for whatever reason, can not seem to get the Apache Daemon to serve you a webpage. By default, unless you changed it in /usr/local/apache/conf/httpd.conf, apache will create a socket and bind (listen) to incomming connections on Port 80. As, previously mentioned, some ISP's do block incomming Port 80 connections before they can get to your webserver, for various reasons, I won't tread into why they do that. However, even though your ISP might block the connection, that does not mean that you cannot have Apache serve you a webpage from inside your LAN. To test that Apache is up and running this is what you need know now, and the steps you should take. 1) Find out the internal IPv4 address of your webserver. (If you only have 1 internal machine behind your router you can use 127.0.0.1). Make sure that there is a good Route to host from whatever your workstation might be at to the webserver, i.e. Ping the webserver make sure it responds. 2) Make sure that Apache is running. This will tell you for sure: # netstat -an | grep -i 80 You should see some output like this: tcp40 0 *.80 *.* LISTEN 3) If you have X Windows running, you can use your normal browser, otherwise you'll want to install Lynx, you can find and install this port by doing the following: # cd /usr/ports/www/lynx ; make make install 4) Then time to test to see if this really works, with your browser we need to enter the IP address of the webserver on the LAN, again, if you are going to test the webserver from your one box, 127.0.0.1 works fine. So enter this into your browser: http://the_webserver_ip_address -- Possibly could look somthing like this: http://192.168.1.2 -- or -- http://127.0.0.1 If you did install Lynx to use it from the command line: # /usr/local/bin/lynx http://your_webserver_ip_address or # /usr/local/bin/lynx http://127.0.0.1 Hopefully you got something back on this request, if not, something might be incorrect with your Apache config. If you did get back a default webpage or what you did expect from this request (one of your own webpages perhaps), thats good, it means that everything is just fine with Apache. 5) Now all you need to do to get around your ISP's blocking of Port 80 is just stop apache: # /usr/local/apache/bin/apachectl stop then edit the /usr/local/apache/conf/httpd.conf file and change the line that now specifies Port 80 and change it to something else, many people use Port 8080 as an alternative. Then just start Apache again: # /usr/local/apache/bin/apachectl start Check to make sure that your listening on the correct port: # netstat -an | grep -i 8080 tcp40 0 *.8080 *.* LISTEN Thats all! Hope that'll get you going in the right direcetion. ~Shane pgp key: http://www.freebsdhackers.net PS: Stacey Roberts posted some good information about why your internal name resolution might not work, read up on /etc/hosts and BIND to solve thoes problems if they exist. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+CeDBtGSLUf7ussURAr3fAJ0UqgQfsBwxPlZMJUGFSnbEyyh+YACfZUPH L+H+NuUS4MOUU2CuqW6Ylww= =Hg6A -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: what do these named messages mean? and ideas?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 24 Dec 2002, Gary D Kline wrote: These messages may not be a concern since named really *is* running. This looks like a packet-filter issue and I am stumped? First things first. Turn of named. Then turn off IPF. Attempt to start named again, then see if you still see thoes messages showing up in /var/log/messages. If you don't then you may have some IPF rule set issues. We won't know until you paste them to this list. (date) sage /usr/local/sbin/named[722]: starting BIND 9.1.3 -c /etc/namedb/named.conf (date) sage /usr/local/sbin/named[722]: could not listen on UDP socket: address in use (date) sage /usr/local/sbin/named[722]: creating IPv4 interface dc0 failed; interface ignored (date) sage /usr/local/sbin/named[722]: could not listen on UDP socket: address in use (date) sage /usr/local/sbin/named[722]: creating IPv4 interface dc1 failed; interface ignored (date) sage /usr/local/sbin/named[722]: could not listen on UDP socket: address in use (date) sage /usr/local/sbin/named[722]: creating IPv4 interface lo0 failed; interface ignored (date) sage /usr/local/sbin/named[722]: not listening on any interfaces (date) sage /usr/local/sbin/named[722]: could not get query source dispatcher (date) sage /usr/local/sbin/named[722]: loading configuration: address in use (date) sage /usr/local/sbin/named[722]: exiting (due to fatal error) Looking at this, it seems like BIND attemts to start up, can not listen on a socket, then dies. So are you positive that the named process is running on your server? Did you accidently try to start another instantce of named? Hope this helps points you in the right direction. ~Shane PGP Key: http://www.freebsdhackers.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+CNKEtGSLUf7ussURAr0tAJ4hz/JSCmttzXtDobnsHnVsXt2NygCaAreZ EPpHBm/uCp5s1jf/q+UHinE= =SXRz -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: problem with installing new ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 20 Dec 2002, David S. Jackson wrote: step 2: google search for the exact tarball name uncovered from the previous command. It should be found at http://www.mpg123.de/cgi-bin/sitexplorer.cgi?/mpg123/ step 3: copy said tarballs to /usr/ports/distfiles and try making the port again. This method will work just fine, however: Please be aware that if you do not continue to update your ports tree, eventually the same problem will happen to every port you attempt to install. The problem will also arise that when you go to the site to download the tarball and you notice that there is a newer version that contains bug fixes, security patches or general performance/enhancements. If you get the new version rather than the version that is specified in your Makefile, you will have MD5 Checksum issues. It is still in your and your computers best interst to update your ports tree, keeping you safe from other nasty issues. :) Good luck. ~Shane pgp key: http://www.freebsdhackers.net/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+A2yQtGSLUf7ussURAs9VAJwJKzg43u8Lu5ob28ossHF636wQSwCfVqNm nsOx/x2xqSCo8QpqZAuUiFc= =qVRc -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think that I have seen problems like this before as well, unrelated to the software. Typiclly when something has not worked in the install, it was due to faluty or broken hardware. Is your system pretty old? Maybe the CDROM is flaky? I have just tried different hardware then had sucess. Hope that helps. ~Shane pgp key: http://www.freebsdhackers.net/pgp On Thu, 19 Dec 2002, mark nelson wrote: I installed the last box the same way. I selecte d preconfigured package even and I get the same error , my cd works becasue I used it on the last machine too? -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+AgvptGSLUf7ussURAtpnAKCFRWbBmrv1tHUhjWnFk0UCCYBg0ACfWUEW 5BP07qfUSlQsyAB/u0tzKiI= =Z1j/ -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
