Re: Netatalk (Apple Filing Protocol) daemon replies Something wrong with the volume's CNID DB

2013-05-01 Thread Tim Leonard 
On May 1, 2013 5:54:32 AM EDT, Yoshihisa Matsushita y...@m8a.org said:

 From: Tim Leonard tim.leon...@charter.net
 Subject: Netatalk (Apple Filing Protocol) daemon replies Something wrong 
 with the volume's CNID DB
 Date: Tue, 30 Apr 2013 22:36:40 -0400
 
 I'm having a problem using Apple Filing Protocol (AFP) services provided by
 netatalk on OpenBSD, from an OS X Mountain Lion client.
 
 I have OpenBSD 5.2 running on an old iMac, with the netatalk-2.2.3p0 package.
 I made no changes to the default configuration beyond editing
 /etc/netatalk/afpd.conf to assign the server its name and IP address.
 I started afpd (the AFP daemon provided by netatalk).
 
 My guess is you forgot starting cnid_metad with afpd.
 
 Try:
 
 $ sudo /etc/rc.d/cnid_metad start
 $ sudo /etc/rc.d/afpd start
 
 and see if this solves the problem.
 

 Basically afpd and cnid_metad are meant to be used together. 
 Try 'man cnid_metad' for more details.

Yes, that solved the problem.
(Though I first had to stop an instance of afpd that was already running.)

 By the way,
 
 pkg_scripts=afpd cnid_metad
 
 is what you want in your rc.conf.local. 'man rc.conf.local'
 and 'man rc.d' are your friends.

The man pages were a great help.
In order to make sure that cnid_metad gets started first during system startup,
I instead listed the two daemons in the other order in /etc/rc.conf.local:
pkg_scripts=cnid_metad afpd

Netatalk (Apple Filing Protocol) daemon replies Something wrong with the volume's CNID DB

2013-04-30 Thread Tim Leonard 
I'm having a problem using Apple Filing Protocol (AFP) services provided by
netatalk on OpenBSD, from an OS X Mountain Lion client.

I have OpenBSD 5.2 running on an old iMac, with the netatalk-2.2.3p0 package.
I made no changes to the default configuration beyond editing
/etc/netatalk/afpd.conf to assign the server its name and IP address.
I started afpd (the AFP daemon provided by netatalk).

From another Mac, I can connect to the resulting server, but get:
Message from server oldMac
Something wrong with the volume's CNID DB, using
temporary CNID DB instead.Check server messages
for details. Switching to read-only mode.

I looked for help on the web and found
[Solved] [netatalk] Something wrong with CNID DB - The FreeBSD Forums
(http://forums.freebsd.org/showthread.php?t=20324)
which suggested
1. Stop netatalk.
2. Delete the .AppleDB cnid db in the root of your share(s).
3. Make sure that the cnidscheme is set to dbd in AppleVolumes.default
4. Crucially, make sure that the cnid_metad daemon has been started, by
adding the following line to /etc/rc.conf:
cnid_metad_enable=YES
5. Start netatalk.

Following that suggestion, I stopped afpd, enabled cnid_metad_enable in
/etc/rc.conf.local, and restarted afpd.
I did not change AppleVolumes.default because the cnidscheme is already dbd by
default.
I did not delete an .AppleDB folder or its contents because none exists
(though there is a .AppleDouble folder).
The changes did not solve the problem.

I also found
609: Mac OS X Mountain Lion  Lion clients receive CNID DB error 
when
connecting to OMV AFP shares - MantisBT
(http://bugtracker.openmediavault.org/print_bug_page.php?bug_id=609)
which suggested
Edit /etc/netatalk/afpd.conf and change the entry to:
- -tcp -noddp -uamlist uams_dhx.so,uams_dhx2_passwd.so
Edit /etc/default/netatalk and add this line at the end:
AFPD_UAMLIST=-U uams_dhx.so,uams_dhx2_passwd.so

I added the suggested switches to the configuration line in afpd.conf.
I did not add anything to a /etc/default/netatalk because I don't have such a
file. Other web pages imply that that file is Debian-ish rather than
OpenBSD-ish.
I stopped and restarted afpd.
The changes did not solve the problem.

Do any of you have other suggestions?

How can I turn off the LCD console backlight on an iMac?

2013-03-08 Thread Tim Leonard 
Is there any way of turning off an iMac's LCD console backlight, 
with OpenBSD 5.2 running on an iMac (2006)?
(The video card died so the machine is running as a server
in console mode, and I don't want the backlight to burn out.)

If this were a PowerPC Mac, OpenBSD/macppc could do it, with
wsconsctl -w display.backlight=0
but the iMac (2006) has an Intel Core 2 Duo.

I was able to use
wsconsctl display.kbdact=on
to blank the screen so to avoid burn-in, but the backlight is still lit.

If there's no current method, what would it take to port the 
macppc solution to Intel Macs?