Re: write protecting syslog

From: Kras Kresh (
Date: 02/25/02

>From: Tom Whiting <>
>Date: Mon, 25 Feb 2002 12:09:31 -0600
>Write protection means you (as a user) can NOT write to the file. What
>sense is there having a file (syslog especially) that you can't write
>to. None.
>Logs aren't meant to be set so that they can't be written to. In fact,
>logs HAVE to be written to by your own account (if not, then who is
>keeping the logs neh?).
>It most obviously was NOT  write protected during game times, as logs
>are kept for things such as, well, logging in, certain logged actions,
>etc.  Had it been u-w it would have never started the game at all.
>Again, if something need to be written to, don't touch it. Syslogs NEED
>to be written to, so you defeat the purpose by chmod'ing them as such.

You have mistaken what I was saying. I was saying write protecting from
users on the system meaning it is read-only for all except the mud.

Before, if I pressed a key while in edit, it would say that file is
read-only. Now, it is modifiable.

Join the world’s largest e-mail service with MSN Hotmail.

   | FAQ: |
   | Archives: |
   | Newbie List:   |

This archive was generated by hypermail 2b30 : 06/25/03 PDT