Hi everybody,
I have many server in production but I would verify this:
ex.: I have many domain in /var/www/html/ (domain1 / domain2 / domain3)
now,
How I do check if the files are added or changed? I should apply this "politic" for all domains but I don't know how
It is possible send me an email with the modification? so, exist diff command with some option but I don't understand how to apply it
Can help me somebody? Thanks in advance
Regards
On 03/01/2014 10:23 PM, Paolo De Michele wrote:
Hi everybody,
I have many server in production but I would verify this:
ex.: I have many domain in /var/www/html/ (domain1 / domain2 / domain3)
now,
How I do check if the files are added or changed? I should apply this "politic" for all domains but I don't know how
It is possible send me an email with the modification? so, exist diff command with some option but I don't understand how to apply it
Can help me somebody? Thanks in advance
why not use git on each domain directory? it will show you changes that need to be committed, side benefit is you can roll back and change manage, document .... as well.
Regards _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, Mar 1, 2014 at 3:23 AM, Paolo De Michele paolo@paolodemichele.it wrote:
Hi everybody,
I have many server in production but I would verify this:
ex.: I have many domain in /var/www/html/ (domain1 / domain2 / domain3)
now,
How I do check if the files are added or changed? I should apply this "politic" for all domains but I don't know how
It is possible send me an email with the modification? so, exist diff command with some option but I don't understand how to apply it
If you installed with an rpm you can use 'rpm -q -V packagename' to check that files haven't changed since the install.
If you have a master copy on some other server, you can use 'rsync -avn --delete dir user@production_host:/path/above/dir' to see a list of files with differences. And if you remove the n from the arguement list it will fix any differences (but be very sure you are in the right place if you use --delete without -n).
Ultimately, you should probably be using subversion or git to maintain this master copy. If you only have one or a few production servers you can just use the version control tools to update them directly, but I prefer a staging copy where you can test the changes before rsyncing to production.
On 03/01/2014 08:01 AM, Les Mikesell wrote:
On Sat, Mar 1, 2014 at 3:23 AM, Paolo De Michele paolo@paolodemichele.it wrote:
Hi everybody,
I have many server in production but I would verify this:
ex.: I have many domain in /var/www/html/ (domain1 / domain2 / domain3)
now,
How I do check if the files are added or changed? I should apply this "politic" for all domains but I don't know how
It is possible send me an email with the modification? so, exist diff command with some option but I don't understand how to apply it
If you installed with an rpm you can use 'rpm -q -V packagename' to check that files haven't changed since the install.
If you have a master copy on some other server, you can use 'rsync -avn --delete dir user@production_host:/path/above/dir' to see a list of files with differences. And if you remove the n from the arguement list it will fix any differences (but be very sure you are in the right place if you use --delete without -n).
Ultimately, you should probably be using subversion or git to maintain this master copy. If you only have one or a few production servers you can just use the version control tools to update them directly, but I prefer a staging copy where you can test the changes before rsyncing to production.
All good suggestions. I'd prefer mercurial to either of Subversion (central repo? Blagh!) or git (mercurial has easier syntax) but that's minor.
One more (super simple) thing to try:
$ touch releasetime.txt; // do something else for a day or three $ find /var/www -newer releasetime.txt;
On Sat, Mar 1, 2014 at 1:14 PM, Lists lists@benjamindsmith.com wrote:
All good suggestions. I'd prefer mercurial to either of Subversion (central repo? Blagh!)
A central repo is exactly what you want when you want one authoritative copy and you have a network to reach it.
On Sat, Mar 1, 2014 at 2:20 PM, Les Mikesell lesmikesell@gmail.com wrote:
On Sat, Mar 1, 2014 at 1:14 PM, Lists lists@benjamindsmith.com wrote:
All good suggestions. I'd prefer mercurial to either of Subversion (central repo? Blagh!)
A central repo is exactly what you want when you want one authoritative copy and you have a network to reach it.
How about something like puppet or ansible on the top of that?
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 2 Mar 2014, at 7:25, Mauricio Tavares raubvogel@gmail.com wrote:
On Sat, Mar 1, 2014 at 2:20 PM, Les Mikesell lesmikesell@gmail.com wrote:
On Sat, Mar 1, 2014 at 1:14 PM, Lists lists@benjamindsmith.com wrote:
All good suggestions. I'd prefer mercurial to either of Subversion (central repo? Blagh!)
A central repo is exactly what you want when you want one authoritative copy and you have a network to reach it.
How about something like puppet or ansible on the top of that?
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Take a look at incrond (notify) http://inotify.aiken.cz/?section=common&page=home&lang=en
On 03/01/2014 11:20 AM, Les Mikesell wrote:
On Sat, Mar 1, 2014 at 1:14 PM, Lists lists@benjamindsmith.com wrote:
All good suggestions. I'd prefer mercurial to either of Subversion (central repo? Blagh!)
A central repo is exactly what you want when you want one authoritative copy and you have a network to reach it.
Oh, it's often very useful to have an "authoritative" copy. We have a few such beasts that are authoritative within their context.
When you are using a DCVS, you can take any arbitrary copy you want and call it the "Central" repo. You can always commit to and pull from the "Central" repo, just as you would with SVN. The bonus of using a DCVS is that when you pull, you get the entire repo, so if your "Central" repo server dies/crashes, you can just start using another one without skipping a beat. Another neat trick is to daisy chain repos, where A is the master of B is the master of C. B gets the changes from A, but not C. C gets changes from A and B. This makes it trivial to try out new features in a fork for a while before pushing changes in C back to B or A.
That you want to have a "Central" or "Master" repo is no reason set things up so you have no ability to change your mind, IMHO. I cannot think of any significant features that SVN offers that Mercurial does not. We started with SVN before switching to Mercurial and there's no way we're going back.
On Sat, Mar 1, 2014 at 6:57 PM, Lists lists@benjamindsmith.com wrote:
That you want to have a "Central" or "Master" repo is no reason set things up so you have no ability to change your mind, IMHO. I cannot think of any significant features that SVN offers that Mercurial does not. We started with SVN before switching to Mercurial and there's no way we're going back.
The biggest thing for us is subversion's ability to use svn 'external' properties at any point in a tree to reference any other svn URL. Checkouts and updates automatically pull in those other locations into your working copy. That lets each component of a large project have its own release schedule by tagging versions and the consuming projects can each advance the versions they use as they are ready simply by changing their external references. And an automated build system like jenkins will see anything new and rebuild as needed simply by polling the top level project.
On 03/01/2014 06:15 PM, Les Mikesell wrote:
The biggest thing for us is subversion's ability to use svn 'external' properties at any point in a tree to reference any other svn URL. Checkouts and updates automatically pull in those other locations into your working copy. That lets each component of a large project have its own release schedule by tagging versions and the consuming projects can each advance the versions they use as they are ready simply by changing their external references. And an automated build system like jenkins will see anything new and rebuild as needed simply by polling the top level project.
See Merc's "subrepos": http://mercurial.selenic.com/wiki/Subrepository?action=show&redirect=sub...
(Or not. If SVN's working well for you, more power to you.)
On Mar 1, 2014 9:39 PM, "Lists" lists@benjamindsmith.com wrote:
On 03/01/2014 06:15 PM, Les Mikesell wrote:
The biggest thing for us is subversion's ability to use svn 'external' properties at any point in a tree to reference any other svn URL. Checkouts and updates automatically pull in those other locations into your working copy. That lets each component of a large project have its own release schedule by tagging versions and the consuming projects can each advance the versions they use as they are ready simply by changing their external references. And an automated build system like jenkins will see anything new and rebuild as needed simply by polling the top level project.
See Merc's "subrepos":
http://mercurial.selenic.com/wiki/Subrepository?action=show&redirect=sub...
(Or not. If SVN's working well for you, more power to you.)
SVN, git, whatever. In the end of the show they are all the same. whichever you are comfortable with _______________________________________________
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Using Firefox 24.3.0 in Centos 5.10 (kernel: 2.6.18-371.3.1.el5xen This message fill the logs: 4gb seg fixup, process firefox (PID31086), cs:IP73::0805bf49 print K; message suppressed
Do somebody experienced this problem?
--- Michel Donais