From: jliddle@rs6000.cmp.ilstu.edu (Jean Liddle)
Subject: shell-init permission denieds
Date: Sat, 19 Dec 1992 16:01:10 GMT
Organization: Illinois State University

Hi again everybody!

First, the GOOD news:  Someone recently posted a question on how to make
xfish a screen saver under x.  Go directly to export.lcs.mit.edu (do not 
pass Go, etc.) and pick up the file xsaver.tar.Z.  This is a neat screen
saver which will let you use ANY program which can be configured to write 
to the root window as a screen saver (including xfish and xlock and the
tons of screen savers which come with it) and allows you to add new modules
without recompiling the code.  Very nice.  To port, comment out all of the
offending duplicate declarations and SYGSYS, SIGBUS stuff.  I would upload
patched code/binaries, but I have not been able to get sz from within 
Seyon 1.5 to talk to the remote unix machine (on which I had started rz).

Which leads me to my first question :-)

In Seyon, I have the following command to upload files:

"regular zmodem ul"   "$ cd /usr/local/ul; sz -b"       y
(the y means prompt for filenames)

on my unix machine I tried rz -vv and rz alone, before starting sz.  Both
seem to start, but neither talks to one another.  sz from the remote and
xrz on the local machine work flawlessly!  Any ideas, tips, glaring
stupidies I'm committing?

And now my 2nd question:

When running this nifty new screen saver, I get the following messages to
standard out:

: Permission denied
shell-init: Permission denied
: Permission denied
shell-init: Permission denied

many, many times ...

: Permission denied
shell-init: Permission denied
: Permission denied
shell-init: Permission denied
shell-init: Permission denied
shell-init: Permission denied
shell-init: Permission denied

These occur each time the screen saver tries to load a new module
(every 10 minutes the way I have it configured).  All the programs load
and run just fine, except for these annoying messages in my xterm
window.  This happened before all of a sudden when I logged in as non-
root, and I fixed the problem by backing up my root partition and 
rebuilding the filesystem.

(by the way, I got these messages running the program as ROOT).

A sample of the executables:

-rwx--x--x   1 root     root        32807 Dec 18 23:57 attraction*
-rwx--x--x   1 root     root        31609 Dec 18 23:55 hypercube*
-rwx--x--x   1 root     root        41659 Dec 18 23:55 xscreensaver*
-rwx--x--x   1 root     root        13600 Dec 18 23:55 xscreensaver-command*

Is there a permisseion set wrong somewhere?  Is my filesystem (which has
served me so well for so long) about to die?  Any help, ideas, etc.
would be much appreciated!!

Thanks in advance!

Jean.

PS - I will upload binaries of the screensaver if I can get the rz/sz
thing figured out.  To those porting, all but rocks works -- rocks dumps
core with a floating point exception on my i486.  I didn't bother to 
look at it last night to figure out why, and I'm off to a friends graduation
today -- so if anyone beats me to the solution, I'd love to hear from you!

-- 
Jean Liddle                                 
Computer Science, Illinois State University  
e-mail:  jliddle@ilstu.edu                  
--------------------------------------------