Red Mop wrote: > On Thursday 07 February 2008 08:34:33 pm Bernd Haug wrote: > >> Red Mop wrote: >> >>> The idea here is that I don't want to leave all of my computers on all >>> the time. So when they boot up, or if they happen to be on, once per >>> day, it creates a file on the server via ssh. The server, having >>> detected this file via inotify, then immediately proceeds to backup the >>> server. This cuts down on the error messages cron sends me, and also >>> allows for simultaneous backups. >>> >> Now I get you, cool. >> But IMO, you kinda do that bass-ackwards. >> >> I would have to agree with Red Mop on this one. I think it is better to keep all the configuration and work at the server rather than have to maintain different configurations on the clients. Keep the clients simple and uniform. GO BIG RED!!!! (esoteric Trailways Bus Line reference) > >> Why not just do the following: >> <snip> >> > > The file that I intend to create is named the client's hostname, and the > contents is the IP(s). I don't want the client machines having the command > lines on them. > > Exactly!!!! >> <more snipping> > >> Also, please get your posting in order. Your top-posting was annoying >> and you changed that; thanks. But now I see newlines between all the >> lines in your posts, and I see your bottom-posts in a different font >> than all the others - have you turned on HTML by mistake? If you did it >> intentionally, it was still a mistake, if you catch my drift. >> > > And I tried SO hard to bring posting issues to light in a positive humorous way.... :) > Personally, I prefer top posts over bottom posts, as every email client I've > yet seen starts at the top, and top posting lets me get right to the topic at > hand, as opposed to paging down through stuff I've already read. I'll try to > remember to use bottom posting for this list. > Well just because someone starts a bad habit doesn't mean it's good.
A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Top-posting is viewed as seriously destructive to mailing-list digests. Some believe that "top-posting" is appropriate for interpersonal e-mail, but inline posting should always be applied to threaded discussions such as newsgroups. With "bottom-posting" the reply is placed below the quote to preserve the logical order of the replies and follow the Western reading direction from top to bottom. "Bottom-posting" is usually extended to "inline replying" where chunks of quoted material and subsequent replies are interleaved, giving a specific response to each paragraph or sentence. If quoting large sections of discussion, particularly in newsgroup discussions, it is recommended to trim the message such that only a taste of the original (a reminder) is left. Paragraphs which are not replied to are frequently "snipped" completely. In such a circumstance it is customary to append an indicator. --Paraphrased from http://en.wikipedia.org/wiki/Top-posting#Inline_replying Read more there and on the rest of that page to help you understand why those of us who give and receive lots of technical support on a day-to-day basis think the way we do. I have a feeling that you might even come around on this issue. > HTML was an accident. And it was only one post. > > :) Dang those HTML mail clients!! :) I frequently disappoint my users by showing them how there fancy emails to me get totally mutilated and 'dumbed' down when I only display them in plain text. :) Keep up the good work, Red. You're on the right track. No two solutions are exactly the same and even some solutions MUST go against the recommended grain for technical reasons. (Richard holds his tongue..grrr) -- Richard _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
