Hi All,

I seem to have found something interesting on my Linux system... I'm not sure how I did it, but all of my files are set to read, write and execute...

cut<=-

-rwxrwxrwx 1 dan dan 2226 Jun 11 00:30 userstat.ans
-rwxrwxrwx 1 dan dan 299 Jan 7 2017 votehdr.asc
-rwxrwxrwx 1 dan dan 928 Mar 7 20:58 voting.ans

cut<=-

Two questions...
Could this be part of my problem with the semaphore files not being created? And, is there an easy way to change these back? Or do I need to modify them
by directory/file...

It seems that this has affected the entire /mystic directory...

I just spent the last twenty minutes laughing at the fact of an executable
ansi file... ;)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

I seem to have found something interesting on my Linux system... I'm not sure how I did it, but all of my files are set to read, write and execute...

cut<=-

-rwxrwxrwx 1 dan dan 2226 Jun 11 00:30 userstat.ans
-rwxrwxrwx 1 dan dan 299 Jan 7 2017 votehdr.asc
-rwxrwxrwx 1 dan dan 928 Mar 7 20:58 voting.ans

cut<=-

When you chown recursively, it hits all files in all directories. If you
gave it a combination that has r+w+x then that would explain it.

Could this be part of my problem with the semaphore files not being created? And, is there an easy way to change these back? Or do I need to

No, that should not be related to semaphore files.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)