Line 195: |
Line 195: |
| best advice is, set the CD-ROM to a higher device number than the HD | | best advice is, set the CD-ROM to a higher device number than the HD |
| and avoid the problem altogether. | | and avoid the problem altogether. |
| + | </pre> |
| + | |
| + | ===Error: Cannot grab ptys from subprocess.=== |
| + | <pre> |
| + | after I did a restore from a tape without restoring the file |
| + | permissions, I get "Error: Cannot grab ptys from subprocess." I did |
| + | that restore on a blank disk with no OS installed. The error occurs |
| + | in Open Sesam when I try to launch an application as root, when I try |
| + | to dial in Gatekeeper etc. It only happens when I am logged in as a |
| + | normal user, I don't have that problem as root. So there must be a |
| + | permission for a file or device that is not set correct, but there are |
| + | so many in my NeXTstep 3.3pl1 system... So can someone give a hint to |
| + | solve this problem? |
| + | |
| + | |
| + | ---- |
| + | |
| + | Going by my system (which seems to work :-), you could run, as root: |
| + | |
| + | chown root.wheel /dev/pty[pq]? |
| + | chown root.tty /dev/tty[pq]? |
| + | chmod 666 /dev/[pt]ty[pq]? |
| + | |
| + | Another alternative might be to delete them, and in /dev/ run "MAKEDEV |
| + | pty", though since I've never done that, I'm not sure how it would |
| + | work out. [I'd suggest doing it at a single-user prompt, though.] |
| + | |
| + | If that's not the problem, then it may be something to do with the |
| + | permissions of Open Sesame or Gatekeeper, rather than the devices. |
| + | Open Sesame uses rsh, which uses ptys, so it could also be an rsh |
| + | problem. |
| + | |
| + | |
| + | ---- |
| + | |
| + | Try "/dev/MAKEDEV std" to rebuild and fix permissions on the device files |
| + | (including the pty's). Otherwise, you're probably missing a setuid bit on |
| + | the OpenSesame binary itself.... |
| </pre> | | </pre> |
| | | |