4/29    Help, Al Qaeda has infiltrate csua and nuking motd is!!!
        \_ CSUA Motd has Yoda as member, not!
           \_ Actually...
              soda:[~] finger yoda
              Login: yoda                             Name: Sean Yoda Rouse
              Directory: /home/sequent/yoda           Shell: /usr/local/bin/ksh
              Last login Thu Apr 22 15:02 (PDT) on ttyBu from 128.222.185.145
              New mail received Fri Apr 30 10:17 2004 (PDT)
                Unread since Fri Apr 30 05:57 2004 (PDT)
              No Plan.
              ...
              though I suppose it's an unanswerable question whether yoda@soda
              (I love that) is a "member of CSUA Motd". What exactly
              constitutes motd membership? -- ulysses
              \_ [formatd]
        \_ b/w al qaeda & the u.s., the world knows that only the u.s.
           definately has nukes!!!  so, it might be the u.s. nuking the motd..
           if it is al qaeda, it is blasting airplanes into the motd!!
           \_ Israel has nukes!  It must be the evil Jews!  Kill the Jews!
              Think of the children!  Save the motd whales!
              \_ Thinking like this will destabalize the Middle East for
                 generations.
                 \_ w00t!
        \_ I think I will institute a new rule. Anytime my posts are
           deleted three times in a row, either by malice or by cowardly
           ssh'ing scumbags who refuse to use motd, I will nuke the motd.
           Sound fair?
           ssh'ing scumbags, I will nuke the motd. Sound fair?
           \_ Nukes are not the answer -liburl
              \_ I like Bush! -moron
                 \_ I like bush too! -lesbian
              \_ I like Bush! -moron
                    \_ I like bush and Bush! -Mary Cheney
           \_ just run your own motd archive if you want to restore after
              a nuke.  that's what i did, after mehlhaff stopped his.  obtw,
              how often does motd update from motd.public?  i'd like to make
              sure i have a good sampling rate.
              \_ fyi, from looking at mehlhaff's log, it looked like his
                 was done every two minutes
                 \_ That's the default with motdwatch.
                    See "/csua/bin/motdwatch -h"  to see how to make your own
                    motd archive.
                    \_ yep, though i didn't even bother with motdwatch.
                       i am running mine every 120 seconds, because that's
                       the motdwatch standard, but i am still curious if that
                       is sufficient.
                       \_ I'd venture to guess that the time between motd
                          changes follows a power-law distribution, and so
                          there's diminishing returns as you watch ever more
                          closely.  Since almost all changes are simple non
                          conflicting additions and subtractions, you really
                          only need to watch often enough to catch most changes
                          that orrur right before a nuke.
                          \_ you would be right if you were not interested
                             in microchanges in the motd.  me, i like to make
                             sure i can recover if someone just wants to
                             censor a particular comment or thread (cf.
                             the guy who's trying to kill the java job ad).
              \_ speaking of which, what's a good way to automate the
                 rotating of the archive, assuming i don't have access to
                 cron/at?
                 \_ I'd make a monitoring program generate filenames based on
                    `date "+%Y.%m.%d.%H.%M.%S"` and then purge stuff older than
                    a day or so.
           ssh'ing scumbags, I will nuke the motd. Sound fair?
           \_ Get lost, loser.
           \_ Nukes are not the answer -liburl
              sure i have a good sampling rate.
                    `date "+%Y.%m.%d.%H.%M.%S"` and then purge stuff older than
                    a day or so.
                    \_ find . \! -mtime 1 -exec /bin/rm {} \;
                       \_ i was going to make it based on -size, but yes.