Discuss

discuss@lists.centos.org

34753 discussions

CentOS 5.3 cron / crontab missing?
by Rudi Ahlers 10 Jun '09

10 Jun '09

Hi On 6/10/09, James Bensley <jwbensley(a)gmail.com> Hi all, I don't know what exactly is causing this, but I can't find cron / crontab on my CentOS 5.3 machine. Yes, I know, it's an obvious one, install it. But, it is, according to rpm: [root@zaxen01 ~]# rpm -aq | grep cron anacron-2.3-45.el5.centos crontabs-1.10-8 I have tried yum update crontabs, and then it said there was no updates. yum update all also said there's no updates. Yet, when I run cron or crontab it doesn't work: [root@zaxen01 ~]# crontab -bash: crontab: command not found [root@zaxen01 ~]# which cron /usr/bin/which: no cron in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@zaxen01 ~]# which crontab /usr/bin/which: no crontab in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@zaxen01 ~]# ll /etc/cron cron.d/ cron.hourly/ crontab cron.daily/ cron.monthly/ cron.weekly/ Am I missing something here? Any pointers on this would be appreciated :) _____________ Kind Regards Rudi Ahlers CEO, SoftDux Hosting Web: http://www.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532

3 3

Crontabs
by James Bensley 10 Jun '09

10 Jun '09

Hey list, I have several crontabs set up to run at night and I'm not convinced they are running but of course, I'm not here to see for sure! The crontabs are like the following example; 30 20 * * * sh /home/a_user/nightlyscrips/nightly_script_1 > /home/a_user/nightlyscripts/`date +%d-%m-%Y--%H-%M-%S`.log However, if this would have successfully ran last night I would surely expect to see 09-06-2009--20-30-00.log in the nightlyscripts directory? But its not there, this goes for all my cron jobs. I have three scripts running at different times in the night all echoing out to a log file like above so I can see how they did but a week after setting them up and no log files exist. The crontabs are running under root and if I copy the command and paste it in terminal and run that from root it runs fine? I set a cron tab up this morning just to see what happens; 35 08 * * * touch /home/a_user/test_file This worked fine, the file was created. Whats happening to my other cron tabs? How can I diagnose the problem? Any help is greatly appreciated. Thanks for reading! Regards, James ;) -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT/MU/U dpu s: a--> C++>$ U+> L++> B-> P+> E?> W+++>$ N K W++ O M++>$ V- PS+++ PE++ Y+ PGP t 5 X+ R- tv+ b+> DI D+++ G+ e(+++++) h--(++) r++ z++ ------END GEEK CODE BLOCK------

4 4

KDE and mounting CD's / DVD's without noexec
by Clint Dilks 10 Jun '09

10 Jun '09

Hi e, I am normally use gnome and would do the following to make my CD / DVD mount with exec gnome-mount --write-settings --device /dev/sdc0 -o exec What is the equivalent in KDE ? My initial research suggests that I actually have to write a custom udev rule to achieve this. This has led me as far as running udevinfo -q path -n /dev/scd0 udevtest /block/sr0 (the output is below) My question is which of these commands is actually doing the mount as all I want to change is the exec flag rather that how the device is labeled. main: looking at device '/block/sr0' from subsystem 'block' run_program: '/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'' run_program: '/bin/bash' (stdout) 'dm_multipath 55257 0 ' run_program: '/bin/bash' returned with status 0 udev_rules_get_name: add symlink 'cdrom' udev_rules_get_name: add symlink 'cdrom-sr0' run_program: 'check-cdrom.sh sr0 DVD' run_program: '/lib/udev/check-cdrom.sh' returned with status 0 udev_rules_get_name: add symlink 'dvd' udev_rules_get_name: add symlink 'dvd-sr0' run_program: 'check-cdrom.sh sr0 CD-R' run_program: '/lib/udev/check-cdrom.sh' returned with status 0 udev_rules_get_name: add symlink 'cdwriter' udev_rules_get_name: add symlink 'cdwriter-sr0' udev_rules_get_name: add symlink 'cdrw' udev_rules_get_name: add symlink 'cdrw-sr0' run_program: 'check-cdrom.sh sr0 DVD-R' run_program: '/lib/udev/check-cdrom.sh' returned with status 0 udev_rules_get_name: add symlink 'dvdwriter' udev_rules_get_name: add symlink 'dvdwriter-sr0' udev_rules_get_name: add symlink 'dvdrw' udev_rules_get_name: add symlink 'dvdrw-sr0' udev_rules_get_name: rule applied, 'sr0' becomes 'scd0' run_program: '/lib/udev/usb_id -x' run_program: '/lib/udev/usb_id' returned with status 1 run_program: '/lib/udev/scsi_id -g -x -s /block/sr0 -d /dev/.tmp-11-0' run_program: '/lib/udev/scsi_id' returned with status 1 run_program: '/lib/udev/scsi_id -g -x -a -s /block/sr0 -d /dev/.tmp-11-0' run_program: '/lib/udev/scsi_id' (stdout) 'ID_VENDOR=TSSTcorp' run_program: '/lib/udev/scsi_id' (stdout) 'ID_MODEL=DVD+-RW_TS-H653F' run_program: '/lib/udev/scsi_id' (stdout) 'ID_REVISION=D200' run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=' run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=cd' run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' run_program: '/lib/udev/scsi_id' returned with status 0 run_program: '/lib/udev/path_id /block/sr0' run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:00:1f.2-scsi-1:0:0:0' run_program: '/lib/udev/path_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0' udev_device_event: device '/block/sr0' already in database, validate currently present symlinks udev_node_add: creating device node '/dev/scd0', major = '11', minor = '0', mode = '0640', uid = '0', gid = '6' udev_node_add: creating symlink '/dev/cdrom' to 'scd0' udev_node_add: creating symlink '/dev/cdrom-sr0' to 'scd0' udev_node_add: creating symlink '/dev/dvd' to 'scd0' udev_node_add: creating symlink '/dev/dvd-sr0' to 'scd0' udev_node_add: creating symlink '/dev/cdwriter' to 'scd0' udev_node_add: creating symlink '/dev/cdwriter-sr0' to 'scd0' udev_node_add: creating symlink '/dev/cdrw' to 'scd0' udev_node_add: creating symlink '/dev/cdrw-sr0' to 'scd0' udev_node_add: creating symlink '/dev/dvdwriter' to 'scd0' udev_node_add: creating symlink '/dev/dvdwriter-sr0' to 'scd0' udev_node_add: creating symlink '/dev/dvdrw' to 'scd0' udev_node_add: creating symlink '/dev/dvdrw-sr0' to 'scd0' udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0' to '../../scd0' main: run: '/sbin/multipath -v0 11:0' main: run: 'socket:/org/kernel/udev/monitor' main: run: '/lib/udev/udev_run_devd' main: run: 'socket:/org/freedesktop/hal/udev_event' main: run: '/sbin/pam_console_apply /dev/scd0 /dev/cdrom /dev/cdrom-sr0 /dev/dvd /dev/dvd-sr0 /dev/cdwriter /dev/cdwriter-sr0 /dev/cdrw /dev/cdrw-sr0 /dev/dvdwriter /dev/dvdwriter-sr0 /dev/dvdrw /dev/dvdrw-sr0 /dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0'

1 0

PPPoE/ADSL configuration questions.
by Bill Campbell 10 Jun '09

10 Jun '09

I am building a CentOS 5 box to ship to Houston which will be a gateway system on an SBC DSL connection for a while until the client gets a T1 installed. I have read up on using adsl-setup and related software, but never done PPPoE on anything but LinkSys commodity boxes. I have examined the adsl-setup script, and I think I understand how this works, but want to be sure I understand things first. The box has dual 10/100/1000 NICs, eth0 for the internal LAN, and eth1 for the PPPoE interface, and later the T1. After running the adsl-setup script, answering the prompts, it appears that it will create an ifcfg-ppp0 interface which will take care of handling the eth1 interface. It also should handle default route setting when the system boots, and do the initial setting of the /etc/resolv.conf file. We will not be using the adsl package firewalling/NAT as we have our own procedures for this. This seems reasonably straightforward, but I know Murphy is always ready to pounce as soon as I assume anything. Is adsl-setup and its associated programs the best way to handle this on a CentOS box? I think that the WAN interface will appear as ppp0 when the system is running. When we move the system to the T1, is it sufficient to edit the ifcfg-ppp0 script setting ONBOOT=no, then do a normal configuration of eth1 using system-config-network? This is something I will have to talk somebody through over the phone unless it would work to connect the DSL modem and T1 router to a network hub/switch with eth1 so that I could configure eth1 while logged in via the DSL connection, the restart the networking to have it bring down the DSL connection, then bring up the T1. What am I forgetting? Thanks. Bill -- INTERNET: bill(a)celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax: (206) 232-9186 Skype: jwccsllc (206) 855-5792 Lord, the money we do spend on Government and it's not one bit better than the government we got for one third the money twenty years ago. Will Rogers

2 1

Re: [CentOS] Networking Issue
by Dave Jones 09 Jun '09

09 Jun '09

>Joseph L. Casale wrote: > >> Now it seems there is still one last hurdle, when the connection is yanked >> to simulate a complete outage, asterisk still goes down. I can only assume >> this happens now as a result of no default gateway? > >check the logs? run strace on the process? run tcpdump on >the interface(s) to see what traffic it is trying to transmit? > >> >> Would setting up a silly route for 0.0.0.0/0 to say 127.0.0.1 for the >> internal >> nic in /etc/sysconfig/network-scripts/route-eth1 with a metric higher than >> what the ISP's dhcp servers default gw would be possibly cure this? My hope >> is that when the wan nic goes down, a route is still available. > >Last I checked the 'metric' number in the linux routing table is >really only used when your using a routing daemon. as far as >default routes go, it should not have any impact. > >I suspect the route is not the issue, I suspect that the app is >trying to talk to something external and then fails, it will fail >the same if you try to point it to a router that goes nowhere. > >tcpdump should be able to tell you who the host is trying to talk >to. strace might reveal why. > >nate I have almost this same setup running with no problems. Make sure you have only one default gateway on your server defined on your Internet facing interface. This should be getting assigned from the DHCP request to your ISP so make sure you don't have a gateway in your internal interface. As far as Asterisk crashing, that sounds like application problem (like Nate said) trying to communicate over the connection that was pulled out. However, make sure it's listening on all interfaces (0.0.0.0), or just the internal static IP, so it's not specifically listening on the DHCP IP that could change or go away when the network cable is yanked. A local tcpdump or wireshark should shed some light on this problem if the above doesn't change anything. -- Dave Jones

2 1

GIMP 2.3.15 for EL5, no newer libs required
by Radu-Cristian FOTESCU 09 Jun '09

09 Jun '09

Folks, I've build a tiny repo to provide GIMP 2.3.15 (and 2.3.14 as a possible fallback) for EL5. GIMP 2.3.15 is the last version of GIMP that builds with no errors with the GTK+ version that ships with EL. 2.3.15 is "almost GIMP 2.4", as 2.3.19 was the last development release prior to 2.4.0. To the extent of my knowledge, Akkana Peck wrote the first edition of her book on GIMP 2.4 using a development edition 2.3.something, where "something" was not newer than 13. I therefore hope that most of the features and improvements brought by 2.4 over 2.2 are already present in 2.3.15 (or 2.3.14). These builds are obviously not as stable as 2.2.13, nor are they patched against bugs or newer vulnerabilities. I have adapted (from Mandriva's 2.3.14 as of 2007.1) the patches for CVE-2006-4519, CVE-2007-2949 and CVE-2007-3741. To get these builds (RPMs and SRPMs), use the repo file: http://odiecolon.lastdot.org/el5/odiecolon.repo The site is not browsable, because I can't make it so (Lucian, any help?). Still, the repo should work (it worked for me). A *few* more details here: http://beranger.org/v3/wordpress/?p=3325 Please test and report if it works for you or not -- I only use a limited set of features from what GIMP can do. Note that I have not tested any plugins, and I don't even know if xsane-gimp still works with this build. Disclaimer: You should never use this on a production system, or else all the kittens within a range of 2 miles might die. Thank you, R-C __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/

2 1

Public key for freetype-2.2.1-21.el5_3.i386.rpm is not installed
by Jay 09 Jun '09

09 Jun '09

Greetings Where can I the public key for freetype ? Thanks! -Jay

2 2

RealTek 8168B (Rev 02) Issue
by Ben Mohilef 09 Jun '09

09 Jun '09

The 8168B (02) NIC works well except that it does not go into promiscuous mode despite advertising itself in that mode after being so directed with ifconfig. Unfortunately, the little box is destined to be an IDS monitor, so that function is essential. The board is an Intel Atom 330 run as x86_64, the nic is internal. We tried three drivers: the one in the 2.6.18-128.1.10.el5 kernel yields a high count of dropped packets (known problem), and the drivers from Realtek and El Repo. None solve the promiscuous problem (although they fix the funny dropped counter issue). Apparently the chip has no MII capability either. Anyone have any idea as how to make this chip do the promiscuous mode thing other than adding another nic card ?

2 4

PAE or use 64-bit?
by Matt Arnilo S. Baluyos (Mailing Lists) 09 Jun '09

09 Jun '09

Hi all, Which would you recommend for a 4GB+ machine? A 32-bit install with PAE-enabled kernel or just use 64-bit? Regards, Matt -- Stand before it and there is no beginning. Follow it and there is no end. Stay with the ancient Tao, Move with the present.

6 6

Intel Graphics support in future releases
by Ron Blizzard 09 Jun '09

09 Jun '09

Since my computers use built-in Intel graphics chips (which work great with CentOS 5.3), I've been worrying about Ubuntu's (and other "cutting edge" distributions) problems with these. It appears to be an Xorg problem. What I don't understand is why Xorg would release something that only half worked with a large segment of the computers out there. I'm also wondering how Red Hat / CentOS will handle such a problem -- or have they already addressed it? Probably shouldn't worry about a "possible" problem, but I do anyhow. -- RonB -- Using CentOS 5.3

5 8

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss