Dylan writes:

On Thursday 18 December 2003 16:29 pm, Mark Gray wrote: <SNIP>

...

Ah, I read your question too fast and thought your program was blocking trying to open /dev/ttyS0

That's what I thought to begin with, but it's definitely the access permissions.

...

Are you running kde using kdm or are you using console mode, xdm, or startx? If you are not using kdm then you are probably having trouble with the resmgr. Then the solution is just to add this to the end of /etc/pam.d/logins

session required pam_resmgr.so

I'm using kdm. I added that line to /etc/pam.d/login (there is no logins file)

Typo -- sorry. It should work with kdm.

and still have to make the device rw-rw-rw-. Still, I figure the security issues there are relatively minimal...

Then I am at a total loss. My serial devices work fine with the rw-rw---- permissions, and I have had to do nothing while using kdm.

...

(Or if you are using ssh, you can uncomment the line at the end of /etc/pam.d/sshd) See /usr/share/doc/packages/resmgr/README.SuSE for more info. If that is not it, what is wrong with setting your user as the owner?

Because four different users, with their own xephem configs need to use it.

If they are the only four users of the machine, then rw-rw-rw- should be good enough. Grasping at straws here, I would at this point start to look into how the resmgr works its magic, because your theory about NIS having something to do with it begins to make more sense. What does the command groups give you? I get: markgray@k6:~> groups users uucp dialout audio video