Problems with 4.6
I didn't see anything obvious in the archives, so apologies if I missed them. OpenBSD 4.6, Dell PowerEdge 2600 Problem 1: Despite the existence of /etc/defaultdomain, the domain name is not being set at boot time. The domainname `cat /etc/defaultdomain` command is executed, but when the console becomes available, the domain name is no longer set. I had to do everything in rc.local to get NIS working. Problem 2: Using the secure httpd (1.3.something), I am unable to make it see the user public_html directories. On an OpenBSD 4.0 system I have, it works fine, and the 2.2.11 web server package for 4.6 works fine. Any clues would be greatly appreciated. -- Mark Leisher
Re: Problems with 4.6
On 04/07/2010 09:43 AM, Otto Moerbeek wrote: On Wed, Apr 07, 2010 at 09:13:57AM -0600, Mark Leisher ??? wrote: I didn't see anything obvious in the archives, so apologies if I missed them. OpenBSD 4.6, Dell PowerEdge 2600 Problem 1: Despite the existence of /etc/defaultdomain, the domain name is not being set at boot time. The domainname `cat /etc/defaultdomain` command is executed, but when the console becomes available, the domain name is no longer set. I had to do everything in rc.local to get NIS working. Strange, I have never have to do that. But you are giving no details, so it is not possible to see what you did or did not to make it not work. This was on a clean install. The only changes I made when I noticed this problem was a new root password, a different port number for sshd, and of course the creation of /etc/defaultdomain. And to answer Bret's private email, the exit code from the domainname call in /etc/rc is still 0. It isn't a permissions issue. Problem 2: Using the secure httpd (1.3.something), I am unable to make it see the user public_html directories. On an OpenBSD 4.0 system I have, it works fine, and the 2.2.11 web server package for 4.6 works fine. I suppose the use dirs are outside the chroot. The httpd in base does chroot by default. I feel dumb! :-) I got so wrapped up in it I missed the obvious. Thanks. -- Mark Leisher
Re: Problems with 4.6
On 04/07/2010 09:33 AM, Rogier Krieger wrote: On Wed, Apr 7, 2010 at 17:13, Mark Leisher b:mleis...@math.nmsu.edu wrote: snip I had to do everything in rc.local to get NIS working. Did you check the yp(8) manual page and FAQ [1] entries? Did you bind the machine as a client? The info you provide is sketchy at best. Of course. On OpenBSD all you need to do to set up a client machine is create /etc/defaultdomain. The domain name then gets set in /etc/rc and ypbind is started if a domain name has been set. My problem is that the domain name is no longer set by the time it gets around to checking whether this is a YP server or client. -- Mark Leisher
Re: Problems with 4.6
On 04/07/2010 11:00 AM, Bret Lambert wrote: what does running domainname `stripcom /etc/defaultdomain` Technically, nothing because stripcom is a shell function. But when I put it in a script by itself, exit code 0. It has always worked from the command line, just not in /etc/rc. -- Mark Leisher
Re: ypserv problem
Edd Barrett wrote: On 20/07/07, Mark Leisher [EMAIL PROTECTED] wrote: % cd /var/yp ; make Everything builds OK (/var/yp/hostname/*.db and /etc/*.db) and I am not running a slave. Now as far as I know, yp uses the normal linux/unix passwd format (not master.passwd). Did you forget pwd_mkd -p /etc/master.passwd (if you used a custom DIR in makefile, then see the -d switch. I hope you did or you are exporting a root password!!!). Like I said, everything, including /etc/*.db (output of pwd_mkdb), builds OK. Everything is located in the default directories. -- Mark Leisher
Re: ypserv problem
Edd Barrett wrote: Like I said, everything, including /etc/*.db (output of pwd_mkdb), builds OK. Everything is located in the default directories. -- Mark Leisher Maybe thats how it works? Perhaps kill -HUP is required. ypserv only reloads its ACL file on SIGHUP. -- Mark Leisher
ypserv problem
I didn't see anything related in the archives, so apologies if it was there and I missed it. When I add a new user and rebuild the YP files, the new user is not visible on client machines until I kill ypserv and start it again. What am I missing? -- Mark Leisher
Re: ypserv problem
Edd Barrett wrote: Hi, On 20/07/07, Mark Leisher [EMAIL PROTECTED] wrote: I didn't see anything related in the archives, so apologies if it was there and I missed it. When I add a new user and rebuild the YP files, the new user is not visible on client machines until I kill ypserv and start it again. What am I missing? What is your method for rebuilding the maps? % cd /var/yp ; make Everything builds OK (/var/yp/hostname/*.db and /etc/*.db) and I am not running a slave. -- Mark Leisher
