Re: [CentOS] run script on cron job only run on first Saturdat every month???
On 08/04/2013 10:17 PM, zGreenfelder wrote: > or... if it really has to be on the first Saturday and only on the first > Saturday, > then running something like > 15 4 1-7 * * /home/app/oracle/backup/monthlybk.sh > > with the top of the monthlybk.sh script doing soemthing like No, really. We went over this. You don't have to modify your scripts. You can put the "test" in the crontab. John's example should work properly: 15 04 * * 6test $(date +"%d") -le 07 && /home/app/oracle/backup/monthlybk.sh Cron will run those commands every Saturday. On the first Saturday in the month, "test" will succeed and the script will be run. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 102, Issue 3
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CEBA-2013:1131 CentOS 5 cman Update (Karanbir Singh)
--
Message: 1
Date: Mon, 5 Aug 2013 10:26:38 +
From: Karanbir Singh
Subject: [CentOS-announce] CEBA-2013:1131 CentOS 5 cman Update
To: centos-annou...@centos.org
Message-ID: <20130805102638.ga3...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2013:1131
Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1131.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
8cca452c8b30e288fc53d2ae3692a9a6a4ed132d32b2881f72f1db99a56c05cb
cman-2.0.115-109.el5.4.i386.rpm
bfcecfec10a8545462def5b00cda1506d31f92da696ff052bec5815eece9e555
cman-devel-2.0.115-109.el5.4.i386.rpm
x86_64:
b5084d9c985433b00024b4b0d239ac7673255614219fde3368a520998cec933f
cman-2.0.115-109.el5.4.x86_64.rpm
bfcecfec10a8545462def5b00cda1506d31f92da696ff052bec5815eece9e555
cman-devel-2.0.115-109.el5.4.i386.rpm
12b5444f6282b94c2e5365f5221e51af8b07b2eb2cf97dc737047c43ec96c846
cman-devel-2.0.115-109.el5.4.x86_64.rpm
Source:
ec46fa315a15d6669fa2bb7b31679bc7adf2b93685b3e44bbafc8e4a611647a8
cman-2.0.115-109.el5.4.src.rpm
--
Karanbir Singh
CentOS Project { http://www.centos.org/ }
irc: z00dax, #cen...@irc.freenode.net
--
___
CentOS-announce mailing list
centos-annou...@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 102, Issue 3
***
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ghostscript-8.70-14.el5_8.1.x86_64 & hylafax+
My Centos 6.x use ghostscript.x86_64 8.70-15.el6_4.1 @updates for hylafax/avantfax from epel or rpmforge. I can't determine from which repository it come, yum list return: [root@fax ~]# yum list ghost* Loaded plugins: fastestmirror, priorities, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: centos.digitalnova.at * epel: be.mirror.eurid.eu * extras: centos.digitalnova.at * rpmforge: apt.sw.be * updates: centos.digitalnova.at 1300 packages excluded due to repository priority protections Installed Packages ghostscript.x86_64 8.70-15.el6_4.1 @updates ghostscript-devel.x86_64 8.70-15.el6_4.1 @updates ghostscript-fonts.noarch 5.50-23.1.el6 @anaconda-CentOS-201112091719.x86_64/6.2 ghostscript-gtk.x86_64 8.70-15.el6_4.1 @updates Blaž Bogataj ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run script on cron job only run on first Saturdat every month???
On 07/30/2013 04:58 PM, John R Pierce wrote: > On 7/30/2013 2:32 PM, Keith Keller wrote: >> 15 04 1-7 * 6 /home/app/oracle/backup/monthlybk.sh > > maybe... > > 15 04 * * 6 test $(date +"%d") -le 07 && > /home/app/oracle/backup/monthlybk.sh > > (untested) Definitely untested! You need to escape the "%" sign, since it is special to cron. Plus, you need to prevent the date command from padding its output with a leading zero, since that would result in the illegal octal numbers 08 and 09: 15 04 * * 6 test $(date +"\%_d") -le 7 && /home/app/oracle/backup/monthlybk.sh -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] problem configuring grub for a dual-boot
I have Windows 7 on /dev/sda and CentOS 6.4 on /dev/sdb. Here are the layouts: (parted) select /dev/sda Using /dev/sda (parted) print Model: ATA WDC WD10EZEX-00Z (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End SizeType File system Flags 1 1049kB 374MB 373MB primary ntfs boot 2 374MB 1000GB 1000GB primary ntfs (parted) select /dev/sdb Using /dev/sdb (parted) print Model: ATA ST500DM002-1BD14 (scsi) Disk /dev/sdb: 500GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start EndSize File system Name Flags 1 1049kB 211MB 210MB fat16 boot 2 211MB 735MB 524MB ext4 3 735MB 500GB 499GB lvm /boot/efi/EFI/redhat/grub.conf looks like this: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,1) # kernel /vmlinuz-version ro root=/dev/mapper/vg_amrl01-lv_root # initrd /initrd-[generic-]version.img #boot=/dev/sdb1 device (hd0) HD(1,800,64000,9b55c4a9-fdbe-4fcd-857b-8e7e129e29f9) default=0 timeout=5 splashimage=(hd0,1)/grub/splash.xpm.gz hiddenmenu title CentOS 6 (2.6.32-358.14.1.el6.x86_64) root (hd0,1) kernel /vmlinuz-2.6.32-358.14.1.el6.x86_64 ro root=/dev/mapper/vg_amrl01-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_amrl01/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=128M KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vg_amrl01/lv_root rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-358.14.1.el6.x86_64.img title Windows 7 rootnoverify (hd1,0) chainloader +1 The system boots into CentOS just fine, but selecting the "Windows 7" entry results in invalid EFI file path Error 1: Filename must be either an absolute pathname or blocklist Press any key to continue... By my understanding, since grub is installed on sdb, then sdb becomes hd0 and thus sda would become hd1, and so telling it to boot Windows from hd1,0 makes sense. Also, since anaconda created the Windows entry during the CentOS install, I would have expected this to work. However, as it doesn't work, I'm clearly missing something. Can someome please point me in the right direction as to why this isn't working? Thanks! --- Mike VanHorn Senior Computer Systems Administrator College of Engineering and Computer Science Wright State University 265 Russ Engineering Center 937-775-5157 michael.vanh...@wright.edu http://www.cecs.wright.edu/~mvanhorn/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run script on cron job only run on first Saturdat every month???
On Mon, Aug 5, 2013 at 2:00 AM, Gordon Messmer wrote: > On 08/04/2013 10:17 PM, zGreenfelder wrote: >> or... if it really has to be on the first Saturday and only on the first >> Saturday, >> then running something like >> 15 4 1-7 * * /home/app/oracle/backup/monthlybk.sh >> >> with the top of the monthlybk.sh script doing soemthing like > > No, really. We went over this. You don't have to modify your scripts. > You can put the "test" in the crontab. John's example should work > properly: > > 15 04 * * 6test $(date +"%d") -le 07 && > /home/app/oracle/backup/monthlybk.sh > > Cron will run those commands every Saturday. On the first Saturday in > the month, "test" will succeed and the script will be run. On the other hand, putting the test in the script - perhaps with a command line option to override - would also keep it from doing something wrong even if someone happens to run it manually at the wrong time. If I were doing it, I might touch a file when starting and check the timestamp of that to avoid running more than one even on the right day. Sometimes the most clever way isn't really the best. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] problem configuring grub for a dual-boot
Try telling grub to swap the disks: > title Windows 7 map (hd1) (hd0) map (hd0) (hd1) > rootnoverify (hd1,0) > chainloader +1 Lorenzo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ghostscript-8.70-14.el5_8.1.x86_64 & hylafax+
On 08/05/2013 02:27 PM, Blaž Bogataj wrote: > My Centos 6.x use ghostscript.x86_64 8.70-15.el6_4.1 @updates for > hylafax/avantfax from epel or rpmforge. > I can't determine from which repository it come, yum list return: > [root@fax ~]# yum list ghost* > Loaded plugins: fastestmirror, priorities, refresh-packagekit, security > Loading mirror speeds from cached hostfile > * base: centos.digitalnova.at > * epel: be.mirror.eurid.eu > * extras: centos.digitalnova.at > * rpmforge: apt.sw.be > * updates: centos.digitalnova.at > 1300 packages excluded due to repository priority protections > Installed Packages > ghostscript.x86_64 8.70-15.el6_4.1 @updates > ghostscript-devel.x86_64 8.70-15.el6_4.1 @updates > ghostscript-fonts.noarch 5.50-23.1.el6 > @anaconda-CentOS-201112091719.x86_64/6.2 > ghostscript-gtk.x86_64 8.70-15.el6_4.1 @updates > > Blaž Bogataj Ghostscript is part of CentOS base/original repositories, so "updates" means just that "CentOS update" repository. -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ghostscript-8.70-14.el5_8.1.x86_64 & hylafax+ 5.5.3
On 08/05/2013 12:26 AM, John R Pierce wrote: > On 8/4/2013 3:09 PM, Ljubomir Ljubojevic wrote: >> First try installing compiled rpm on a TEST system, and if that does not >> work you can try recompiling the source rpm, or ask someone to help you, >> maybe maintainer of ghostscript in Fedora. > > if you rebuild it via the RPM, it likely will overwrite the 'stock' > ghostscript. > > a tarball install could be built to run in /usr/local/ghostscript/... or > /opt/mystuff/ghostscript/... or whatever, and not interfere with the > distribution build. > That is true if hylafax can be pointed to use optional version of ghostcript. If that is not the case, then ghostscript has to be replaced. P.S. I am not a hylafax user so I can not determine what should be done. -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] run script on cron job only run on first Saturdat every month???
On 2013/08/05 05:01, Les Mikesell wrote: > On Mon, Aug 5, 2013 at 2:00 AM, Gordon Messmer > wrote: >> On 08/04/2013 10:17 PM, zGreenfelder wrote: >>> or... if it really has to be on the first Saturday and only on the first >>> Saturday, >>> then running something like >>> 15 4 1-7 * * /home/app/oracle/backup/monthlybk.sh >>> >>> with the top of the monthlybk.sh script doing soemthing like >> No, really. We went over this. You don't have to modify your scripts. >>You can put the "test" in the crontab. John's example should work >> properly: >> >> 15 04 * * 6test $(date +"%d") -le 07 && >> /home/app/oracle/backup/monthlybk.sh >> >> Cron will run those commands every Saturday. On the first Saturday in >> the month, "test" will succeed and the script will be run. > On the other hand, putting the test in the script - perhaps with a > command line option to override - would also keep it from doing > something wrong even if someone happens to run it manually at the > wrong time. If I were doing it, I might touch a file when starting > and check the timestamp of that to avoid running more than one even on > the right day. Sometimes the most clever way isn't really the best. > We do what Les is suggesting. Our script runs the second Saturday of the month (just to be difficult), and is broken into two parts. The part called by cron via "0 9 8-14 * *" does the checking and then calls the real script only if all the conditions are met: it's a Saturday, it's not already running, etc etc. The nice thing about this way is that in the unfortunate case that something went wrong with the cron-fire and we have to manually run the script, we can just do that on the command line without worrying about it not running because out of umpteen tests one failed and killed the execution. And, the initial script is tailored to the machine on which it runs, whereas the main script is the same on all the machines where it runs, so that's handy as well. Thanks! Miranda ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ghostscript-8.70-14.el5_8.1.x86_64 & hylafax+ 5.5.3
On 08/05/2013 12:26 AM, John R Pierce wrote: > On 8/4/2013 3:09 PM, Ljubomir Ljubojevic wrote: >> First try installing compiled rpm on a TEST system, and if that does not >> work you can try recompiling the source rpm, or ask someone to help you, >> maybe maintainer of ghostscript in Fedora. > > if you rebuild it via the RPM, it likely will overwrite the 'stock' > ghostscript. > > a tarball install could be built to run in /usr/local/ghostscript/... or > /opt/mystuff/ghostscript/... or whatever, and not interfere with the > distribution build. > That is true if hylafax can be pointed to use optional version of ghostcript. If that is not the case, then ghostscript has to be replaced. P.S. I am not a hylafax user so I can not determine what should be done. -- Everyone, Thanks so much for everyone's help I am a new hylafax+ user and other than the ghostscript problem I am very impressed. Hylafax+ does allow you to control the location of ghostscript so once I get it compiled I should be able to point it to the correct version. Instead of using the Fedora RPM, I am going to compile it and try to route the files to a different location. I really screwed up a different system trying to do an rpm install with a Fedora module with a different piece of software. I am a little gun shy about doing that again. I am using Hylafax+ on CentOS 5.9 to replace a vsifax system installed on SCO. If I can get ghostscript 9.07 installed properly this will be a very good replacement. If any of you have additional suggestions, I sure appreciate your help. Greg ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ghostscript-8.70-14.el5_8.1.x86_64 & hylafax+ 5.5.3
On Mon, Aug 5, 2013 at 5:19 PM, Gregory P. Ennis wrote: > > I am a new hylafax+ user and other than the ghostscript problem I am > very impressed. Hylafax+ does allow you to control the location of > ghostscript so once I get it compiled I should be able to point it to > the correct version. Instead of using the Fedora RPM, I am going to > compile it and try to route the files to a different location. I really > screwed up a different system trying to do an rpm install with a Fedora > module with a different piece of software. I am a little gun shy about > doing that again. > > I am using Hylafax+ on CentOS 5.9 to replace a vsifax system installed > on SCO. If I can get ghostscript 9.07 installed properly this will be a > very good replacement. > > If any of you have additional suggestions, I sure appreciate your help. It doesn't help with this particular problem, but is there some reason for using CentOS 5.x vs. 6.x? -- Les mikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ghostscript-8.70-14.el5_8.1.x86_64 & hylafax+ 5.5.3
Greg, I haven't sent a fax in ages, so my suggestion would be to take a step back and see if you still need to use fax. You may still have a need for it, but I'm just suggesting that you think about it! Cheers, Cliff On Tue, Aug 6, 2013 at 10:19 AM, Gregory P. Ennis wrote: > On 08/05/2013 12:26 AM, John R Pierce wrote: > > On 8/4/2013 3:09 PM, Ljubomir Ljubojevic wrote: > >> First try installing compiled rpm on a TEST system, and if that does not > >> work you can try recompiling the source rpm, or ask someone to help you, > >> maybe maintainer of ghostscript in Fedora. > > > > if you rebuild it via the RPM, it likely will overwrite the 'stock' > > ghostscript. > > > > a tarball install could be built to run in /usr/local/ghostscript/... or > > /opt/mystuff/ghostscript/... or whatever, and not interfere with the > > distribution build. > > > > That is true if hylafax can be pointed to use optional version of > ghostcript. > > If that is not the case, then ghostscript has to be replaced. > > P.S. I am not a hylafax user so I can not determine what should be done. > > -- > > Everyone, > > Thanks so much for everyone's help > > I am a new hylafax+ user and other than the ghostscript problem I am > very impressed. Hylafax+ does allow you to control the location of > ghostscript so once I get it compiled I should be able to point it to > the correct version. Instead of using the Fedora RPM, I am going to > compile it and try to route the files to a different location. I really > screwed up a different system trying to do an rpm install with a Fedora > module with a different piece of software. I am a little gun shy about > doing that again. > > I am using Hylafax+ on CentOS 5.9 to replace a vsifax system installed > on SCO. If I can get ghostscript 9.07 installed properly this will be a > very good replacement. > > If any of you have additional suggestions, I sure appreciate your help. > > Greg > > > > ___ > 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
[CentOS] NFS - No lista dos directorios especificos
Estimados. Actualmente, estoy tirando los backups a un server que comparte por NFS los directorios. Me encuentro con un problema, por ahora en dos servidores, en el cual no puedo ver directorios exportados. Server: LaCie 5Big Network (sistema propietario, sin acceso root. http://www.lacie.com/la/products/product.htm?id=10485) Cliente1: root@server [/home/cpbackuptmp]# uname -a Linux fq.dn.net.ar 2.6.18-348.1.1.el5.centos.plus #1 SMP Tue Jan 22 19:16:31 EST 2013 i686 athlon i386 GNU/Linux El problema, radica en que no puedo ver dos directorios exportados, dejandome medio sin terminar el directorio donde tiro los backups, por lo que estoy pasandolos via ftp Existe algun limite en NFS en cuanto a los directorios a exportar? Alguna otra idea por donde puedo buscar el problema/solucion? La verdad, que reconozco que tengo muy poco conocimento sobre trabajar con NFS. -- root@server [/bkp]# showmount -e aaa.bbb.ccc.110 Export list for aaa.bbb.ccc.110: /shares/a* /shares/b* /shares/c* /shares/d * /shares/f * ... /shares/y* root@server [/bkp]# showmount -e aaa.bbb.ccc.110|wc -l 25 Deberia tener 27 directorios exportados. En el LaCie, los directorios fueron creados de la misma forma. De hecho, he creado otros para otros servidores, y se muestran. Tambien probe cambiando el nombre, eliminandolo y volviendo a crear, etc. Tambien reinicie el LaCie. Solucion bananera y argentina en mente: crear un solo directorio, adecuar todos los otros servers y realizar backup en los directorios especificos La verdad, mucho no me convence trabajar de esta manera, pero bue... Ambos servidores, son CentOS 5.9 final (el 3ro con esta version, lo monta perfectamente) Algun limite de la version? -- Diego - Yo no soy paranoico! (pero que me siguen, me siguen) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Problem with touchpad
Hi there, i recently installed centos 6 64bit version on my HPProBook4530s Laptop. After running full system update and system restarted, my touch pad is not responding any more. How can i fix this problem? Kind Regards ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
