Messages in this thread | | | Date | Thu, 1 Oct 1998 15:26:20 +0100 | From | "Stephen C. Tweedie" <> | Subject | Re: Building Big Ass Linux Machine, what are the limits? |
| |
Hi,
On Thu, 1 Oct 1998 15:45:24 +0200 (MEST), R.E.Wolff@BitWizard.nl (Rogier Wolff) said:
> My thought was that if you access the device, you should run the > application that shows you the message. If you're accessing the > multivolume device and forget to run the application, you're on your > own.
> The person at the console is the one that most likely has physical > access to the devices in question, so running the reporting program > would for the "change disks" message be most appropriate for those > sitting at the console.
> But if it's say a departemental server, all of the X sessions might > want to include the "get messages program", allowing the person that's > working on the volume to step up and walk over to the server to change > disks.
Sounds like you need syslog. syslog already lets you define which consoles receive which messages. It allows certain classes of users to be notified of certain types of message, and lets you propogate messages between hosts.
--Stephen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |