RE: nvidia-driver segmentation fault
On Thursday, May 24, 2007 9:46 PM, Howard Goldstein wrote: Ernest Sales wrote: (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) Are you loading the glx module in xorg.conf? The first command was just to show that with the nv driver X didn't hang, while the second command, using nvidia driver, caused a segmentation fault. I suppose this error means I will not have OpenGL under the nv driver, but there are other drawbacks of using these instead of the nvidia driver, so I don't care. For instance, with the nv driver I get the desktop at most at 1/4 the maximum available resolution. Thanks anyway. Ernest ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: nvidia-driver segmentation fault
Sorry, in my previous answer didn't edit the subject. On Thu, 24 May 2007 10:10:57 -0500, Derek Ragona wrote: At 07:26 AM 5/24/2007, Ernest Sales wrote: To celebrate te Xorg upgrade I got rid of all ports installed in my system, then did a fresh install. No problems building; well, I installed first gnome-lite expecting it would pull the complete xorg meta-port and finally had to install this to get all the stuff, but suppose this is harmless. Now, the sad history: I can run X apps with the nv driver, but the nvidia-driver fails. Typescript [...comments...]: [...using the nv driver...] # X -config xorg.conf.new X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu May 24 11:56:19 2007 (++) Using config file: /root/xorg.conf.new (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) [...works fine; same if I launch the desktop...] [...now as configured with nvidia-xconfig...] # X -config /etc/X11/xorg.conf X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu May 24 11:57:34 2007 (++) Using config file: /etc/X11/xorg.conf [...shows the nvidia splash screen and then aborts...] Fatal server error: Caught signal 11. Server aborting Abort (core dumped) # tail /var/log/messages [...] May 24 11:57:37 asinusaureus kernel: pid 1840 (Xorg), uid 0: exited on signal 6 (core dumped) No relevant info in xorg logs. After much looking, I am still clueless. Any hint? Make sure you are using the correct driver for your specific graphics chip. Older chips need a legacy driver you have to install yourself. From /var/log/dmesg.today: [...] nvidia0: Quadro FX Go700 mem 0xfc00-0xfcff,0xd000-0xdfff irq 11 at device 0.0 on pci1 [...] From NVIDIA-FreeBSD-x86-1.0-9746/doc/README [...] Appendix A. Supported NVIDIA Graphics Chips [...] Quadro FX Go700 0x031C [...] So I am afraid this is not the guilty. Thanks anyway. Ernest There is information on the nvidia website. -Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nvidia-driver segmentation fault
To celebrate te Xorg upgrade I got rid of all ports installed in my system, then did a fresh install. No problems building; well, I installed first gnome-lite expecting it would pull the complete xorg meta-port and finally had to install this to get all the stuff, but suppose this is harmless. Now, the sad history: I can run X apps with the nv driver, but the nvidia-driver fails. Typescript [...comments...]: [...using the nv driver...] # X -config xorg.conf.new X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu May 24 11:56:19 2007 (++) Using config file: /root/xorg.conf.new (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) [...works fine; same if I launch the desktop...] [...now as configured with nvidia-xconfig...] # X -config /etc/X11/xorg.conf X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu May 24 11:57:34 2007 (++) Using config file: /etc/X11/xorg.conf [...shows the nvidia splash screen and then aborts...] Fatal server error: Caught signal 11. Server aborting Abort (core dumped) # tail /var/log/messages [...] May 24 11:57:37 asinusaureus kernel: pid 1840 (Xorg), uid 0: exited on signal 6 (core dumped) No relevant info in xorg logs. After much looking, I am still clueless. Any hint? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: freebsd-questions Digest, Vol 179, Issue 12
On Thu, 24 May 2007 10:10:57 -0500, Derek Ragona wrote: At 07:26 AM 5/24/2007, Ernest Sales wrote: To celebrate te Xorg upgrade I got rid of all ports installed in my system, then did a fresh install. No problems building; well, I installed first gnome-lite expecting it would pull the complete xorg meta-port and finally had to install this to get all the stuff, but suppose this is harmless. Now, the sad history: I can run X apps with the nv driver, but the nvidia-driver fails. Typescript [...comments...]: [...using the nv driver...] # X -config xorg.conf.new X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu May 24 11:56:19 2007 (++) Using config file: /root/xorg.conf.new (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) [...works fine; same if I launch the desktop...] [...now as configured with nvidia-xconfig...] # X -config /etc/X11/xorg.conf X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD asinusaureus 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu May 24 11:20:28 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZORN i386 Build Date: 21 May 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu May 24 11:57:34 2007 (++) Using config file: /etc/X11/xorg.conf [...shows the nvidia splash screen and then aborts...] Fatal server error: Caught signal 11. Server aborting Abort (core dumped) # tail /var/log/messages [...] May 24 11:57:37 asinusaureus kernel: pid 1840 (Xorg), uid 0: exited on signal 6 (core dumped) No relevant info in xorg logs. After much looking, I am still clueless. Any hint? Make sure you are using the correct driver for your specific graphics chip. Older chips need a legacy driver you have to install yourself. From /var/log/dmesg.today: [...] nvidia0: Quadro FX Go700 mem 0xfc00-0xfcff,0xd000-0xdfff irq 11 at device 0.0 on pci1 [...] From NVIDIA-FreeBSD-x86-1.0-9746/doc/README [...] Appendix A. Supported NVIDIA Graphics Chips [...] Quadro FX Go700 0x031C [...] So I am afraid this is not the guilty. Thanks anyway. Ernest There is information on the nvidia website. -Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: sendmail init error: Can't assign requested address
On Tuesday, May 15, 2007 6:29 PM, Chuck Swiger wrote: On May 15, 2007, at 9:06 AM, Ernest Sales wrote: [ ... ] Honestly, I don't understand what each of this four daemons is supposed to do. I just want the minimal working sendmail config in a NATed host, the /etc/defaults/rc.conf reads as your sample, and init says sendmail_outbound_enable is set to NO, which seems odd but dunno the consequences. There are only two daemons, actually: the MTA, and the client mqueue runner. The separation was made because sendmail used to run as a single, setuid-root executable, and has had a rather infamous security history as a consequence. If you want sendmail to be running and listening on port 25 as a MTA, you need to set the sendmail_enable/ sendmail_outbound_enable to YES. [ ... ] Is there any standard, anything like the CIDR blocks reserved for private networks? The zeroconf/rendezvous stuff likes to use .local as the domain unless other info is available. Cool. Tried .local and works too. Looks like sendmail is happy with finding 'dot anything' after the hostname. So far, my problem is fixed. But the init behavior for unqualified hostnames is less than optimal: having to wait one minute until sendmail agrees --and it finally agrees-- is annoying; and this happens for every sendmail daemon launch. As more end-users using PCs without FQDN jump to FreeBSD this could be more heard of. Wonder if filing a PR; comments welcome. The standard period for a DNS timeout is anywhere up to about two minutes, depending on how many resolvers are configured in /etc/ resolv.conf. It's possible to tell sendmail not to use DNS, and avoid this timeout, but normally people run mailservers only on machines with working DNS and a sensible hostname. This isn't a bug, it's just an assumption that sendmail makes which is typically appropriate, but not for the case of a random client machine without working DNS A broader point of view. OK, I forget about PR. Thanks. Ernest -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: .login_conf ignored [solved]
On Wednesday, May 16, 2007 9:20 AM, Christopher Illies wrote:
On Tue, May 15, 2007 at 06:39:05PM +0200, Ernest Sales wrote:
On Tue, 15 May 2007 09:14:42 +0200, Christopher
Illies wrote:
The locale settings in my .login_conf are ignored:
[...]
Try compiling just your ~/login_conf, make sure a
~/login_conf.db file appears.
Ernest
Thanks, that has worked!
Before I always used cap_mkdb /etc/login.conf plus all the user's
$HOME/.login_conf, but just using it on my ~/.login_conf did the
trick. A ~/.login_conf.db file has appeared.
I feel a bit silly for not having come up with it myself.
I guess what
confused me was that on another user's account the
cap_mkdb compiling
wasn't neccessary, but I don't need to understand that now that it
works for me.
Thanks again.
Christopher
But you are still curious, aren't you?
Yes
AFAIK, there are two possible
explanations:
1) There _is_ a .login_conf.db file in the other user's homedir.
No
2) The other account pertains to a different login class than yours,
which already sets the desired locale and so masquerades the user's
settings being ignored. Dunno if a user can see his own
login class. If
you have permissions, can use vipw to find out (if
unfamiliar, take a
look to vipw(8) and passwd(5) manpages, notice the 'class' field).
Ernest
Not that I can see. I 'chris' is my login, and 'bill' in another
account that does not have this problem:
; sudo cat /etc/master.passwd | egrep 'chris|bill' | awk
-F: '{ print $1,:, $5,:}'
chris : :
bill : :
; whoami
chris
; ls /home/bill/.login*
/home/bill/.login /home/bill/.login_conf
; cat /home/bill/.login_conf
# $FreeBSD: src/share/skel/dot.login_conf,v 1.3 2001/06/10 17:08:53
# ache Exp $
#
# see login.conf(5)
#
me:\
:charset=iso-8859-1:\
:lang=se_SE.ISO8859-1:
; sudo sed -i.bak -e 's/se_SE/de_DE/' /home/bill/.login_conf
; su -l bill
Password:
$ whoami
bill
$ env | egrep -i 'lang|charset'
MM_CHARSET=iso-8859-1
LANG=de_DE.ISO8859-1
But to change settings on the 'chris' account I have to use cap_mkdb
/home/chris/.login_conf. Strange...
Christopher
And your test also discards some login script directly setting the variables
(assuming bill locale is usually se_SE). Wish some day we get enlightened.
Ernest
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: .login_conf ignored
On Tue, 15 May 2007 09:14:42 +0200, Christopher Illies wrote: The locale settings in my .login_conf are ignored: ; cat .login_conf # $FreeBSD: src/share/skel/dot.login_conf,v 1.3 2001/06/10 17:08:53 # ache Exp $ # # see login.conf(5) # me:\ :charset=UTF-8:\ :lang=en_US.UTF-8: ; env | egrep -i 'lang|charset' LANG=en_US.ISO8859-1 MM_CHARSET=iso-8859-1 ; ls -l .login_conf -rw-r--r-- 1 chris chris 146 May 15 08:26 .login_conf ; uname -r 6.2-STABLE My .login_conf file is not a symlink or world writable etc. Also, an identical .login_conf for another user is applied without problems. What am I missing? Christopher Did you run cap_mkdb? From login.conf manpage: The default /etc/login.conf shipped with FreeBSD is an out of the box configuration. Whenever changes to this, or the user's ~/.login_conf, file are made, the modifications will not be picked up until cap_mkdb(1) is used to compile the file into a database. This database file will have a .db extension and is accessed through cgetent(3). Never had to deal with ~/.login_conf files, but what cap_mkdb manpage seems to say is that you have to concatenate all sources in one run, i.e. cap_mkdb /etc/login.conf /home/user1/.login.conf /home/user2/.login.conf ... HTH Ernest ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: .login_conf ignored
On Tuesday, May 15, 2007 1:18 PM, Christopher Illies wrote: On Tue, May 15, 2007 at 12:27:10PM +0200, Ernest Sales wrote: On Tue, 15 May 2007 09:14:42 +0200, Christopher Illies wrote: The locale settings in my .login_conf are ignored: ; cat .login_conf # $FreeBSD: src/share/skel/dot.login_conf,v 1.3 2001/06/10 17:08:53 # ache Exp $ # # see login.conf(5) # me:\ :charset=UTF-8:\ :lang=en_US.UTF-8: ; env | egrep -i 'lang|charset' LANG=en_US.ISO8859-1 MM_CHARSET=iso-8859-1 ; ls -l .login_conf -rw-r--r-- 1 chris chris 146 May 15 08:26 .login_conf ; uname -r 6.2-STABLE My .login_conf file is not a symlink or world writable etc. Also, an identical .login_conf for another user is applied without problems. What am I missing? Christopher Did you run cap_mkdb? From login.conf manpage: The default /etc/login.conf shipped with FreeBSD is an out of the box configuration. Whenever changes to this, or the user's ~/.login_conf, file are made, the modifications will not be picked up until cap_mkdb(1) is used to compile the file into a database. This database file will have a .db extension and is accessed through cgetent(3). Never had to deal with ~/.login_conf files, but what cap_mkdb manpage seems to say is that you have to concatenate all sources in one run, i.e. cap_mkdb /etc/login.conf /home/user1/.login.conf /home/user2/.login.conf ... HTH Ernest Thanks, unfortunately no success. When I concatenate all ~/login_conf files with /etc/login.conf I get the following warning message: cap_mkdb: ignored duplicate: me So I was mistaken. Try compiling just your ~/login_conf, make sure a ~/login_conf.db file appears. Ernest It did not help with my locale setting, though. Strangely, another user account on the same computer works correctly in that respect. Also, running cap_mkdb after changing the ~/login_conf of that user is not neccessary for the changes to take effect. This makes me think that there is something wrong with my user account. But what? Christopher ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: sendmail init error: Can't assign requested address
On Tuesday, May 15, 2007 12:24 AM, Chuck Swiger wrote: On May 14, 2007, at 2:25 PM, Ernest Sales wrote: Well, actually not so (sendmail_outbound_enable is supposed to be set to YES, as per defaults, but init says otherwise -- and I don't know what that means). But it starts without delays and can send/receive mail (even internet mail, wow!). Take a look at /etc/defaults/rc.conf for all of the gory details. You probably meant sendmail_enable=YES, but: # Settings for /etc/rc.sendmail and /etc/rc.d/sendmail: sendmail_enable=NO# Run the sendmail inbound daemon (YES/NO). sendmail_pidfile=/var/run/sendmail.pid# sendmail pid file sendmail_procname=/usr/sbin/sendmail # sendmail process name sendmail_flags=-L sm-mta -bd -q30m # Flags to sendmail (as a server) sendmail_submit_enable=YES# Start a localhost-only MTA for mail submission sendmail_submit_flags=-L sm-mta -bd -q30m - ODaemonPortOptions=Addr=localhost # Flags for localhost-only MTA sendmail_outbound_enable=YES # Dequeue stuck mail (YES/NO). sendmail_outbound_flags=-L sm-queue -q30m # Flags to sendmail (outbound only) sendmail_msp_queue_enable=YES # Dequeue stuck clientmqueue mail (YES/NO). sendmail_msp_queue_flags=-L sm-msp-queue -Ac -q30m # Flags for sendmail_msp_queue daemon. Honestly, I don't understand what each of this four daemons is supposed to do. I just want the minimal working sendmail config in a NATed host, the /etc/defaults/rc.conf reads as your sample, and init says sendmail_outbound_enable is set to NO, which seems odd but dunno the consequences. I chose .localhost to qualify the hostname because the notion of public domain name is where I get lost. Can I pick any word as TLD/SLD to operate in a private LAN? Yes, but using a local domain which conflicts with existing domains is strongly not recommended. Consider what happens if a local config issue bounces email or worse to somebody else, or consider what happens if you chose .net or .com instead of .localhost. Is there any standard, anything like the CIDR blocks reserved for private networks? The zeroconf/rendezvous stuff likes to use .local as the domain unless other info is available. Cool. Tried .local and works too. Looks like sendmail is happy with finding 'dot anything' after the hostname. So far, my problem is fixed. But the init behavior for unqualified hostnames is less than optimal: having to wait one minute until sendmail agrees --and it finally agrees-- is annoying; and this happens for every sendmail daemon launch. As more end-users using PCs without FQDN jump to FreeBSD this could be more heard of. Wonder if filing a PR; comments welcome. Researchs led me to RFC 2606, alternative DNS roots, and the like, but I couldn't distill any practical advice. Which will be the interactions if I choose e.g. .somedomain.com? Now if I send a mail to the internet, it has a From field ([EMAIL PROTECTED]) unusable to reply to; if this was [EMAIL PROTECTED] it could fake some real mail address. Yes, absolutely, or to bounce email back to the example domain. Network admins get cross when you pretend to be in a domain that you have no affiliation with and they have to get your ISP to clean up after you :-) -- -Chuck Thanks. Ernest ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: .login_conf ignored [solved]
On Tuesday, May 15, 2007 5:00 PM, Christopher Illies wrote: On Tue, May 15, 2007 at 04:36:46PM +0200, Ernest Sales wrote: On Tuesday, May 15, 2007 1:18 PM, Christopher Illies wrote: On Tue, May 15, 2007 at 12:27:10PM +0200, Ernest Sales wrote: On Tue, 15 May 2007 09:14:42 +0200, Christopher Illies wrote: The locale settings in my .login_conf are ignored: ; cat .login_conf # $FreeBSD: src/share/skel/dot.login_conf,v 1.3 2001/06/10 17:08:53 # ache Exp $ # # see login.conf(5) # me:\ :charset=UTF-8:\ :lang=en_US.UTF-8: ; env | egrep -i 'lang|charset' LANG=en_US.ISO8859-1 MM_CHARSET=iso-8859-1 ; ls -l .login_conf -rw-r--r-- 1 chris chris 146 May 15 08:26 .login_conf ; uname -r 6.2-STABLE [...] Never had to deal with ~/.login_conf files, but what cap_mkdb manpage seems to say is that you have to concatenate all sources in one run, i.e. cap_mkdb /etc/login.conf /home/user1/.login.conf /home/user2/.login.conf ... HTH Ernest Thanks, unfortunately no success. When I concatenate all ~/login_conf files with /etc/login.conf I get the following warning message: cap_mkdb: ignored duplicate: me So I was mistaken. Try compiling just your ~/login_conf, make sure a ~/login_conf.db file appears. Ernest Thanks, that has worked! Before I always used cap_mkdb /etc/login.conf plus all the user's $HOME/.login_conf, but just using it on my ~/.login_conf did the trick. A ~/.login_conf.db file has appeared. I feel a bit silly for not having come up with it myself. I guess what confused me was that on another user's account the cap_mkdb compiling wasn't neccessary, but I don't need to understand that now that it works for me. Thanks again. Christopher But you are still curious, aren't you? AFAIK, there are two possible explanations: 1) There _is_ a .login_conf.db file in the other user's homedir. 2) The other account pertains to a different login class than yours, which already sets the desired locale and so masquerades the user's settings being ignored. Dunno if a user can see his own login class. If you have permissions, can use vipw to find out (if unfamiliar, take a look to vipw(8) and passwd(5) manpages, notice the 'class' field). Ernest ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: sendmail init error: Can't assign requested address
On Monday, May 14, 2007 3:15 AM, Jeffrey Goldberg wrote: On May 13, 2007, at 5:07 PM, Ernest Sales wrote: A laptop running 6-STABLE is connected to the Internet thru a DSL modem-router doing NAT. It gets a dynamic local IP (fairly recurring 192.168.1.33) at every boot. Of course there is no FQDN for this host. I'm not entirely sure if this will solve your problem but you can set up a FQDN for that IP without causing any conflicts. If you have a public domain name, say, yourdomain.com than you could set up a subdomain private.yourdomain.com I crafted it a little different. Now /etc/hosts reads: ::1 asinusaureus asinusaureus.localhost localhost 127.0.0.1 asinusaureus asinusaureus.localhost localhost Sendmail starts smoothly: [...] /etc/rc: DEBUG: checkyesno: sshd_enable is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_enable is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: checkyesno: sendmail_enable is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: pid file (/var/run/sendmail.pid): not readable. /etc/rc: DEBUG: run_rc_command: evaluating sendmail_precmd(). /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: run_rc_command: evaluating /usr/sbin/sendmail -L sm-mta -bd -q30 m -ODaemonPortOptions=Addr=localhost(). /etc/rc: DEBUG: checkyesno: sendmail_outbound_enable is set to NO. /etc/rc: DEBUG: checkyesno: sendmail_msp_queue_enable is set to YES. /etc/rc: DEBUG: pid file (/var/spool/clientmqueue/sm-client.pid): not readable. /etc/rc: DEBUG: run_rc_command: evaluating sendmail_precmd(). /etc/rc: DEBUG: checkyesno: sendmail_msp_queue_enable is set to YES. /etc/rc: DEBUG: run_rc_command: evaluating /usr/sbin/sendmail -L sm-msp-queue -A c -q30m(). /etc/rc: DEBUG: checkyesno: cron_dst is set to YES. [...] Well, actually not so (sendmail_outbound_enable is supposed to be set to YES, as per defaults, but init says otherwise -- and I don't know what that means). But it starts without delays and can send/receive mail (even internet mail, wow!). I chose .localhost to qualify the hostname because the notion of public domain name is where I get lost. Can I pick any word as TLD/SLD to operate in a private LAN? Is there any standard, anything like the CIDR blocks reserved for private networks? Researchs led me to RFC 2606, alternative DNS roots, and the like, but I couldn't distill any practical advice. Which will be the interactions if I choose e.g. .somedomain.com? Now if I send a mail to the internet, it has a From field ([EMAIL PROTECTED]) unusable to reply to; if this was [EMAIL PROTECTED] it could fake some real mail address. These are questions for the sake of correcteness. I rather won't get into the arcanes of sendmail, but as it is part of base and used for admin purposes, would like to set it up properly. As for the real email stuff, will be dealt from the GUI some day; but there is always the chance of a guy playing with the CLI. and locally run your own DNS server to serve for that domain, and to forward DNS requests for all other domains. You can also make that some local DNS server do reverse lookups in 192.168.0.0/16 without worries as long as DNS queries are only coming from within your local network. Maybe in the future. At present there is only this laptop in the LAN -- the LAN is just the way to connect with the modem-router. Some day there will be more inhabitants, however, so I would like to set up a schema able to encompass the growth. Also, try to configure your DHCP server (on your modem-router) to always give the same IP address to your laptop (you can do this by associating an IP with the hardware ethernet (or wireless) MAC address. You mean the local IP, I suppose. Not checked yet... -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ Thanks for your help. Ernest ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sendmail init error: Can't assign requested address
A laptop running 6-STABLE is connected to the Internet thru a DSL modem-router doing NAT. It gets a dynamic local IP (fairly recurring 192.168.1.33) at every boot. Of course there is no FQDN for this host. Lately (after a sendmail upgrade?) init shows some oddities: /etc/rc: DEBUG: checkyesno: sendmail_submit_enable is set to YES. /etc/rc: DEBUG: run_rc_command: evaluating /usr/sbin/sendmail -L sm-mta -bd -q30 m -ODaemonPortOptions=Addr=localhost(). May 12 21:59:35 asinusaureus sm-mta[970]: My unqualified host name (asinusaureus ) unknown; sleeping for retry [...after quite a while...] May 12 22:06:20 asinusaureus sm-mta[970]: unable to qualify my own domain name ( asinusaureus) -- using short name [...] May 12 22:06:20 asinusaureus sm-mta[987]: NOQUEUE: SYSERR(root): opendaemonsocke t: daemon Daemon0: cannot bind: Can't assign requested address May 12 22:06:20 asinusaureus sm-mta[987]: daemon Daemon0: problem creating SMTP socket [...lots of this, and finally...] May 12 22:07:10 asinusaureus sm-mta[987]: daemon Daemon0: problem creating SMTP socket May 12 22:07:10 asinusaureus sm-mta[987]: NOQUEUE: SYSERR(root): opendaemonsocke t: daemon Daemon0: server SMTP socket wedged: exiting Relevant custom config: /etc/rc.conf: --- [...] # net hostname=asinusaureus ifconfig_bge0=dhcp [...] --- /etc/hosts: --- [...comments...] ::1 asinusaureus localhost 127.0.0.1 asinusaureus localhost [...comments...] --- Neither named, pf, nor nis are enabled. Sendmail is started as per defaults in /etc/defaults/rc.conf What am I missing? And BTW, would it make any sense to qualify this hostname? Ernest --- plain text emails preferred, cf http://expita.com/nomime.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: find and timezone
On May 6, 2007 Lowell Gilbert wrote: Ernest Sales [EMAIL PROTECTED] writes: Could someone explain why this works fine: # find . -newermt May 2 12:00:09 CET 2007 [...] # ...whereas this doesn't: # find . -newermt May 2 12:00:09 CEST 2007 find: Can't parse date/time: May 2 12:00:09 CEST 2007 # (CET: Central European Time, ...S...: Summer) I don't really know the details, but /usr/share/zoneinfo seems to define CET and not CEST. If you figure out the syntax, it should be easy to add the extra abbreviations. Thanks for the hint. It looks rather difficult; cf tzfile(5), zic(8). Moreover the system seems to be aware of CEST: # date dilluns, 7 de maig de 2007, 21:03:53 CEST # zdump CEST CEST Mon May 7 19:04:03 2007 UTC # Looks to me rather as a problem with the way find parses dates. FWIW, my login.conf reads: [... my (indirect) login class:] # # Usuaris de La Franja. Català, UTF-8 i retocs # lafranja|usuaris de La Franja:\ :lang=ca_ES.UTF-8:\ :lc_all=ca_ES.UTF-8:\ :lc_collate=ca_ES.UTF-8:\ :lc_ctype=ca_ES.UTF-8:\ :lc_messages=ca_ES.UTF-8:\ :lc_monetary=ca_ES.UTF-8:\ :lc_numeric=ca_ES.UTF-8:\ :lc_time=ca_ES.UTF-8:\ :charset=UTF-8:\ :tc=default: [...] ...but only LANG is passed to the environment -- i.e. LC_TIME is not: # echo $LANG ca_ES.UTF-8 # echo $LC_TIME LC_TIME: Undefined variable. I used to use the output of uname -v (words 5 to 9) with find in a qd script to backup custom config files, and this is worked around by now. Just wonder if it deserves a PR. --- plain text emails preferred, cf http://expita.com/nomime.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't fetch several ports (return error code 127) and seems nothing to do with these ports themselves
Maybe this is due to the xorg 7.2 upgrade. See http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040488.html and http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040510.html --- plain text emails preferred, cf http://expita.com/nomime.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
find and timezone
Could someone explain why this works fine: # find . -newermt May 2 12:00:09 CET 2007 [...] # ...whereas this doesn't: # find . -newermt May 2 12:00:09 CEST 2007 find: Can't parse date/time: May 2 12:00:09 CEST 2007 # (CET: Central European Time, ...S...: Summer) Thanks in advance! Ernest --- plain text emails preferred, cf http://expita.com/nomime.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
