One argument for attaching config files, logs and whatnot directly is that they are more persistent in the list archives. If pastebin shut down, if the posts expired or something else caused the links to fail, it could hinder someone down the road trying to solve a similar problem. The main issue behind compressed attachments is that, specially for windows users, they could carry viruses. Further, many mail servers simply reject files like zip archives. digimer On 08/23/2012 11:05 AM, Nick Khamis wrote: > Even better don't attach config files.... That is what Pastebin is for > "http://pastebin.com/"; > > On Tue, Aug 21, 2012 at 4:53 PM, Digimer <lists@xxxxxxxxxx> wrote: >> On 08/21/2012 04:39 PM, João Nobre wrote: >>> Hello, >>> I'm trying to make two clusters with two nodes which, using Corosync and >>> Pacemaker: >>> One cluster -> two nodes. >>> and install them in three servers, all ubuntu 12.04 LTS. >>> One of the three servers will run one node belonging to each cluster , >>> separately, but in the same network. >>> I have try all the settings but the server with the two clusters doesn't >>> work. >>> >>> Can you please help me? >>> I send the configuration files in a .zip file. >>> >>> Thanks in advance. >> >> First off, sending a zip file attachment to a mailing list is a pretty >> bad idea. It's much better to attach plain-text files as-is. >> >> Next, you can not have one node be a member in to different clusters. It >> is much better to create a single 3-node cluster and use constraints to >> keep a given service on one of two nodes. >> >> -- >> Digimer >> Papers and Projects: https://alteeve.ca >> _______________________________________________ >> discuss mailing list >> discuss@xxxxxxxxxxxx >> http://lists.corosync.org/mailman/listinfo/discuss -- Digimer Papers and Projects: https://alteeve.ca _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
