Opened 14 years ago

Closed 12 years ago

#156 closed task (invalid)

n-f should run our zephyr logger

Reported by: geofft Owned by:
Priority: minor Milestone:
Component: internals Keywords:


n-f is our ~stock Fedora machine. While it shouldn't run the scripts config in general, we should know if something funky happens to n-f (not that it's running much of anything, but still), so we should deploy the zephyr logger.

Also, it possibly shouldn't take password logins? There may be some other minimal set of config to take from the scripts web hosts without making it a scripts web host.

Change History (2)

comment:1 Changed 14 years ago by mitchb

I'm not sure that I really have strong feelings about the zephyr logger, though you (Geoff) have said that we should not treat it as if it were a trusted machine, which implies that it should take password auth so that we can get into it without necessarily being at a trusted machine. I've certainly used that functionality on a regular basis. While I don't really think there's a big problem with running the zephyr logger (modulo that we need zephyr, sigh...), the normal way to figure out whether something funky happened to it (admittedly not in realtime) is to look at the logwatch mail, which really means we should set the root alias.

comment:2 Changed 12 years ago by achernya

  • Resolution set to invalid
  • Status changed from new to closed

We no longer have a not-forward.

Note: See TracTickets for help on using tickets.