Re: [CentOS] unsuscribe
If you want to unsubscribe, go here: http://lists.centos.org/mailman/options/centos - Original Message - From: "Miguel Varas A." To: "CentOS mailing list" Sent: Tuesday, October 20, 2009 4:09:08 PM Subject: [CentOS] unsuscribe ___ 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
Re: [CentOS] rpm --freshen issue (was: Re: Caught between a Red Hat and a CentOS)
Sorry, don't have time to read the whole thread (busy day!), so please excuse
me if I just add to the noise, but this may work for you (at a bash prompt):
for x in *; do rpm --freshen --repackage $x; done
If it's not what you're looking for, I apologize in advance. :)
--
David Fix
- Original Message -
From: "ken"
To: "CentOS mailing list"
Sent: Wednesday, October 21, 2009 5:12:14 AM
Subject: [CentOS] rpm --freshen issue (was: Re: Caught between a Red Hat and a
CentOS)
On 10/20/2009 12:15 PM Benjamin Franz wrote:
> ken wrote:
>> Okay, here's one. Maybe someone here can figure it out.
>> Upgrading from 4.5 to 4.5. From a 4.6 ISO I copied all the RPMs into a
>> directory... let's call it c:/install :). Now the oracle dba has
>> strict parameters on what versions can be installed and which can't.
>> The rpms in c:/install meet those requirements. In addition, since this
>> is a production machine, it can be down at most for one day. So all I
>> want to do is upgrade what's currently on the system. Moreover, if
>> something horks, I want two chances to back out (the second being asking
>> the backup guy to put the system back to yesterday). The command to do
>> this would be
>>
>> rpm --freshen --repackage *
>>
>> run in that crazy c:/install directory (or what the redhat guy called, a
>> "folder"). This command runs fine for one file which has no
>> dependencies (i.e., change '*' to a specific rpm). It also upgrades
>> three or four co-dependent rpms if they're narrowly specified. But if
>> the file/rpm spec is '*', rpm complains about two missing dependencies
>> and stops.
>>
>> Yeah, this directory contains 1507 rpms (IIRC)... which is a lot, but it
>> should still work. This is Linux, after all. And there's plenty enough
>> memory and cpu to handle it.
>>
>
> Running
>
> rpm --freshen --repackage *
>
> for 1500+ rpms probably exceeds the maximum character length for some
> part of the system after expansion of the '*' by the shell.
That was my first suspicion too. The redhat tech didn't bring that up
though. (That doesn't mean I'm going to ignore that as a possible
workaround; the original conversation here was about tech support per
se. Of course I'm still seeking ways to do the job. And so thanks for
the suggestion.)
I, too, recall reading some years back about a bash line length limit.
Back then, a long time ago, it was 2048 characters. So I ran "echo *"
in that same install/ directory and the output included all 1507 files.
So the problem's not with a bash command line length limit, but still
pointing to the "rpm" command.
>
> Try breaking it up into smaller chunks (say two or three hundred at a
> time). You can match subsets of the files using shell expansions like
>
> rpm --freshen --repackage [a-g]*
>
> and tweak the line for any dependency complaints manually.
This solution occurred to me also. And right now it's a top contender
(along with another I'll mention shortly). If the job environment were
different, I'd go with it. But my boss is making me jump through a lot
of hoops for this project. This upgrade from v.4.5 to v.4.6 needs to
happen in a single, specified day *and* my boss needs to know how long
it will take me to accomplish, this so the Oracle dba knows when he can
start to on what he's got to do for this upgrade. And I have at most
fifteen hours (i.e., two working days) to come up with this fool-proof
plan. Plus, I don't have a test box to try things out on. But I've had
to do trickier stuff than this in the past with not dissimilar time
constraints, so though I should be taking extra boxers to work, I'm not
(yet).
So what I was thinking of doing is scripting the solution you suggest
above. But then, if I'm going to script something, I might as well
write a script that will take on the entire task wholistically. I mean
something like this:
ls -1 install/ > what-to-upgrade.list # create package list
while read package | {upgrade package} #just quasi-code here. Loop.
if {there's nothing to upgrade}
remove pkg from what-to-upgrade.list
log this
continue
fi
if {there are dependencies}
then for {each dependency} {upgrade package} # yep, recursion
fi
else [upgrade package} # simplest case, just upgrade one pkg
The {upgrade package} function would be fairly simple (I think):
- Find the correct package in the install/ directory (containing the
RPMs for v.4.6).
- Upgrade the 4.5 package with that correct 4.6 package.
- Confirm that the 4.6 is installed.
- Remove that package name from what-to-
Re: [CentOS] rpm --freshen issue (was: Re: Caught between a Red Hat and a CentOS)
Gotcha. :) Sorry about that. :)
--
David Fix
- Original Message -
From: kfis...@lakelandcc.edu
To: "CentOS mailing list"
Sent: Wednesday, October 21, 2009 7:53:31 AM
Subject: Re: [CentOS] rpm --freshen issue (was: Re: Caught between a Red Hat
and a CentOS)
The problem with such a loop is that only one pkg is the arg to each invocation
of the rpm command. So if there are any dependencies for a particular
invocation, nothing will be installed.
From: David Fix
To: CentOS mailing list
Date: 10/21/2009 07:32 AM
Subject:Re: [CentOS] rpm --freshen issue (was: Re: Caught
between a Red Hat and a CentOS)
Sent by:centos-boun...@centos.org
Sorry, don't have time to read the whole thread (busy day!), so please excuse
me if I just add to the noise, but this may work for you (at a bash prompt):
for x in *; do rpm --freshen --repackage $x; done
If it's not what you're looking for, I apologize in advance. :)
--
David Fix
- Original Message -
From: "ken"
To: "CentOS mailing list"
Sent: Wednesday, October 21, 2009 5:12:14 AM
Subject: [CentOS] rpm --freshen issue (was: Re: Caught between a Red Hat and a
CentOS)
On 10/20/2009 12:15 PM Benjamin Franz wrote:
> ken wrote:
>> Okay, here's one. Maybe someone here can figure it out.
>> Upgrading from 4.5 to 4.5. From a 4.6 ISO I copied all the RPMs into a
>> directory... let's call it c:/install :). Now the oracle dba has
>> strict parameters on what versions can be installed and which can't.
>> The rpms in c:/install meet those requirements. In addition, since this
>> is a production machine, it can be down at most for one day. So all I
>> want to do is upgrade what's currently on the system. Moreover, if
>> something horks, I want two chances to back out (the second being asking
>> the backup guy to put the system back to yesterday). The command to do
>> this would be
>>
>> rpm --freshen --repackage *
>>
>> run in that crazy c:/install directory (or what the redhat guy called, a
>> "folder"). This command runs fine for one file which has no
>> dependencies (i.e., change '*' to a specific rpm). It also upgrades
>> three or four co-dependent rpms if they're narrowly specified. But if
>> the file/rpm spec is '*', rpm complains about two missing dependencies
>> and stops.
>>
>> Yeah, this directory contains 1507 rpms (IIRC)... which is a lot, but it
>> should still work. This is Linux, after all. And there's plenty enough
>> memory and cpu to handle it.
>>
>
> Running
>
> rpm --freshen --repackage *
>
> for 1500+ rpms probably exceeds the maximum character length for some
> part of the system after expansion of the '*' by the shell.
That was my first suspicion too. The redhat tech didn't bring that up
though. (That doesn't mean I'm going to ignore that as a possible
workaround; the original conversation here was about tech support per
se. Of course I'm still seeking ways to do the job. And so thanks for
the suggestion.)
I, too, recall reading some years back about a bash line length limit.
Back then, a long time ago, it was 2048 characters. So I ran "echo *"
in that same install/ directory and the output included all 1507 files.
So the problem's not with a bash command line length limit, but still
pointing to the "rpm" command.
>
> Try breaking it up into smaller chunks (say two or three hundred at a
> time). You can match subsets of the files using shell expansions like
>
> rpm --freshen --repackage [a-g]*
>
> and tweak the line for any dependency complaints manually.
This solution occurred to me also. And right now it's a top contender
(along with another I'll mention shortly). If the job environment were
different, I'd go with it. But my boss is making me jump through a lot
of hoops for this project. This upgrade from v.4.5 to v.4.6 needs to
happen in a single, specified day *and* my boss needs to know how long
it will take me to accomplish, this so the Oracle dba knows when he can
start to on what he's got to do for this upgrade. And I have at most
fifteen hours (i.e., two working days) to come up with this fool-proof
plan. Plus, I don't have a test box to try things out on. But I've had
to do trickier stuff than this in the past with not dissimilar time
constraints, so though I should be taking extra boxers to work, I'm not
(yet).
So what I was thinking of doing is scripting the solution you suggest
above. But then, if I'm going to script something, I might as well
write a script that will take o
[CentOS] Screensaver (or screen blanking) at login screen - CentOS 5.2 or 5.3
Hey guys, I've done a ton of googling, searching and asking in the forums, etc, and I haven't found a way to do this... :) I'm trying to find a way of having some type of screen saver at the login screen so that if I leave a machine not logged into, it won't burn-in the screen. Does anyone know of a way to achieve this? In specific, I'd love to have it simply blank the screen and leave the screen on, just black after maybe 5 minutes of inactivity at the login screen. :) Thanks in advance, it's really appreciated! :) Dave ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Initial backup prior to daily rsync backups
Simple... :) Just rsync to the external drive, then rsync from the drive to your local server. :) -- David Fix Senior Systems Administrator Mr. X Inc. 35 McCaul Street, Ste. #100 Toronto, ON M5T 1V7 T: (416) 595-6222, x 241 F: (416) 595-9122 E: dav...@mrxfx.com - Original Message - From: "Jeff Gregor" To: centos@centos.org Sent: Thursday, July 16, 2009 10:52:46 AM GMT -05:00 US/Canada Eastern Subject: [CentOS] Initial backup prior to daily rsync backups I have a few CentOS 5.3 servers out at remote sites that connect over a satellite link (a painfully slow satellite link). There's a time period in the wee hours of the morning when the satellite provider doesn't stiff me for bandwidth, and when the link is generally idle, where I want to use rsync to back up files to my local server. I've got rsync working in in combination with cron and ssh, and that process works fine. The problem is getting the initial copy of the files over to the local server so that rsync can just deal with files changed during the day (there tend to not be too many changes -- mostly office-type documents, few pictures, that sort of thing, so limited bandwidth is not a problem). If I run rsync now, however, it is trying to copy over all the files since none exist on the local servers, and by my calculations copying that 160gb worth of data should be done some time in mid-February, 2010. I can make the 4-hour round trip out to the remote site with a USB hard drive and copy the files that way, but my concern is how to get the file structure, timestamps, permissions, etc copied exactly from the remote server > USB drive > local server so that rsync can run most efficiently (and not have to do a compare on every single file the first time it runs.) So the question is, how do I copy the files from the remote server back to my local server in a way that will allow rsync, once the copy is complete, to start dealing just with the daily changes in the most efficient way possible? Thanks! ___ 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
Re: [CentOS] Setting up large (12.5 TB) filesystem howto?
And just to add to the discussion... We use JFS here for large filesystems. :) (We have some 24TB filesystems in place here using JFS, with no problems like XFS has when it gets corrupted). -- David Fix Senior Systems Administrator Mr. X Inc. 35 McCaul Street, Ste. #100 Toronto, ON M5T 1V7 T: (416) 595-6222, x 241 F: (416) 595-9122 E: dav...@mrxfx.com - Original Message - From: "Akemi Yagi" To: "CentOS mailing list" Sent: Friday, August 28, 2009 11:58:27 AM GMT -05:00 US/Canada Eastern Subject: Re: [CentOS] Setting up large (12.5 TB) filesystem howto? On Fri, Aug 28, 2009 at 8:36 AM, Joshua Baker-LePain wrote: > You do not have to switch to 64bit, and your setup should be fully > supported. Other folks have mentioned XFS, and that's an option. But if > you want to stay fully compatible with upstream, then ext3 is your only > option. Support for xfs has been added to RHEL 5.4 which will be released any day now. Akemi ___ 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
Re: [CentOS] how to clean YUM download?
yum clean all :) - Original Message - From: "mcclnx mcc" To: centos@centos.org Sent: Tuesday, September 8, 2009 8:48:06 AM Subject: [CentOS] how to clean YUM download? We have CENTOS 5.2 on DELL server. While I run "yum update" and yum start download files. in middle of download there have power surge and computer reboot. Does there has way to clean yum download? Thanks ___ 您的生活即時通 － 溝通、娛樂、生活、工作一次搞定！ http://messenger.yahoo.com.tw/ ___ 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
Re: [CentOS] gdm-simple-greeter config?
grep face /home/ -r :) -- David Fix Senior Systems Administrator Mr. X Inc. - Original Message - From: "m roth" To: "CentOS mailing list" Sent: Friday, September 18, 2009 9:01:27 AM Subject: Re: [CentOS] gdm-simple-greeter config? > Greetings, > > On Fri, Sep 18, 2009 at 8:34 AM, mark wrote: >> itxakaserr...@gmail.com wrote: >>> Enviado desde mi iPhone >>> El 18/09/2009, a las 04:39, mark escribió: >>>> R P Herrold wrote: >>>>> On Thu, 17 Sep 2009, mark wrote: >>>>> >>>>>> I have googled. I have find ...-exec grep. One server >>>>>> continues to send error messages to /var/log/messages that >>>>>> gdm-simple-greeter can't find some file in a user's (another >>>>>> admin, actually) home directory. Any ideas where it's >>>>>> getting it from? > > There are couple of directories starting with '.' (i.e. hidden ones) > pertaining to gnome .gconf, .gdm maybe you can find the answers there. > > /me putting up the sheild for hiding from "insufficient accuracy" missiles Yeah, I always alias ll="ls -laF", so they're never hidden from me. Anyway, the situation is that users logging onto this system, as most of our systems, get their home directory automounted. However, this guy hasn't been on this system most of the time I've tried to find this error. Based on that, it's got to be somewhere in a *system* file, not in a home directory, yet it complains: gdm-simple-greeter[2361]: GLib-GIO-WARNING: Missing callback called fullpath = /home//.face#012 Now, I found /var/lib/gdm, and have looked under .config, .gconf, and .gconfd, and not found it. I have also killed the simple greeter, and it respawned, and started griping again. So, where is it storing this, and, more important, *WHY* is it caching this? Ideally, I'd like to not only clear whatever's causing it now, but also change the relevant system configuration file so that it doesn't happen again. mark ___ 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
