From: balaji <balaji.srinivasa@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] log oversight
Date: Sun, 15 Mar 2009 19:35:49 -0700 [thread overview]
Message-ID: <948781140903151935y51e45cedl6ab826ee9c68b115@mail.gmail.com> (raw)
In-Reply-To: <4D743982-1C38-4BBC-B77E-DCBB5791361A@corpus-callosum.com>
intentional. if you do a ls -ltm, you will see [none] would have
updated smtp*, runq etc...
upas/*, others run as none, and well...
is it a shortcoming compared to unix world? these logs
are not sacrosanct.
On Sun, Mar 15, 2009 at 6:49 PM, Jeff Sickel <jas@corpus-callosum.com> wrote:
> I've just built out a new Plan 9 cpu/auth server and noticed that others are
> able to write to the logs. Is this intentional or just an oversight?
>
>
> cpu% ls -l /sys/log
> a-rw-rw-rw- M 2936 sys sys 0 Aug 3 2007 /sys/log/6in4
> a-rw-rw-rw- M 2936 sys sys 0 Apr 26 2002 /sys/log/aan
> a-rw-rw-rw- M 2936 sys sys 9644 Mar 15 19:45 /sys/log/auth
> a-rw-rw-r-- M 2936 bootes bootes 219734 Mar 15 20:30 /sys/log/cron
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/cs
> a-rw-rw-rw- M 2936 sys sys 1273328 Mar 15 20:37 /sys/log/dns
> a-rw-rw-rw- M 2936 sys sys 0 Sep 12 2007 /sys/log/fossil
> a-rw-rw-rw- M 2936 sys sys 1145 Mar 7 14:55 /sys/log/ftp
> d-rwxrwxr-x M 2936 sys sys 0 Feb 28 13:32 /sys/log/httpd
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/imap4d
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/ipboot
> a-rw-rw-rw- M 2936 sys sys 0 Jul 31 2007 /sys/log/ipconfig
> a-rw-rw-rw- M 2936 sys sys 29713 Mar 13 01:46 /sys/log/listen
> a-rw-rw-rw- M 2936 sys sys 914 Sep 12 2007 /sys/log/mail
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/nfs
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/nfsserver
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/pop3
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/portmapper
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/ppp
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/pptpd
> a-rw-rw-rw- M 2936 sys sys 182 Mar 24 2004 /sys/log/runq
> a-rw-rw-rw- M 2936 sys sys 0 Jan 5 2005 /sys/log/secstore
> a-rw-rw-rw- M 2936 sys sys 69 Mar 24 2004 /sys/log/smtp
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/smtp.fail
> a-rw-rw-rw- M 2936 sys sys 1032 Mar 13 06:56 /sys/log/smtpd
> a-rw-rw-rw- M 2936 sys sys 0 Oct 29 2004 /sys/log/smtpd.mx
> a-rw-rw-rw- M 2936 sys sys 4965 Mar 14 10:24 /sys/log/ssh
> a-rw-rw-rw- M 2936 sys sys 0 May 21 2000 /sys/log/telnet
> a-rw-rw-rw- M 2936 sys sys 1764 Mar 8 12:57 /sys/log/timesync
> d-rwxrwxr-x M 2936 sys sys 0 Feb 28 13:32 /sys/log/timesync.d
> a-rw-rw-rw- M 2936 sys sys 0 Jul 31 2007 /sys/log/v6routeradv
>
>
>
>
next prev parent reply other threads:[~2009-03-16 2:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 1:49 Jeff Sickel
2009-03-16 2:35 ` balaji [this message]
2009-03-16 3:04 ` erik quanstrom
2009-03-16 3:18 ` ron minnich
2009-03-16 3:55 ` J.R. Mauro
2009-03-16 4:31 ` Alex Efros
2009-03-16 6:30 ` ron minnich
2009-03-16 15:06 ` J.R. Mauro
2009-03-16 4:23 ` Nathaniel W Filardo
2009-03-16 4:36 ` Jeff Sickel
2009-03-16 13:37 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=948781140903151935y51e45cedl6ab826ee9c68b115@mail.gmail.com \
--to=balaji.srinivasa@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).