Re: [CentOS] bash variable expansion moment
On 16-Nov-2009 ken wrote:
> On 11/15/2009 06:32 PM Stephen Harris wrote:
>> On Sun, Nov 15, 2009 at 06:21:40PM -0500, ken wrote:
>>
>>
>> echo This is line "${BASH_LINENO[0]}" $@
>>
>>
>
> That's all I needed. Thanks.
You might also want to check out bash's built in `caller` command.
-Philip
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] software raid :: kernel update procedure
On 11-Nov-2009 Adrian Sevcenco wrote: > Hi! I have an software raid installation (md_dX type) and i am wondering > what is the procedure for kernel update... is the initrd auto-magicaly > rebuild? Yes. As part of kernel.rpm 's postinstall script. You can verify the initrd by looking at /boot/initrd-2.6.X-X.img (roughly): gzip -dc initrd.img > /tmp/temp.img mount -o loop /tmp/temp.img /mnt cat /mnt/init umount /mnt -Philip ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Running SSH on a different port
On 24-Oct-2009 Oliver Ransom wrote: > I don't think there are any ramifications/disadvantages of running the > SSH daemon on a non standard port. Running sshd on a non-standard port is highly useful ; I always have 2 seperate sshd instances. One on 22 and one on 222. This way, if I muck up an sshd upgrade, or config change, I can always get in through the other instance on 222. It is important to keep the 2 instances seperate, with serperate startup scripts and binaries (as in, cp /sbin/sshd /sbin/sshd222) -Philip ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] EDAC Kernel Panic 2.6.9-78 and above
On 20-Oct-2009 Michael Schumacher wrote: >> I've got a production system running CentOS 4 that was rock solid >> until I upgraded from 2.6.9-55 to 2.6.9-78.0.13 (now running >> 2.6.9-89.0.11). The system now crashes intermittently after a few >> weeks. I finally caught the panic message : > >> EDAC MC0: INTERNAL ERROR: channel-b out of range (4 >= 4) >> Kernel panic - not syncing: MC0: Uncorrected Error I have also seen this message or something very close. The server is 200 km away and the person who read it to me over the phone wasn't very fluent in English. That server has a ASUS DSBF-D12 motherboard. Kernel was 2.6.9-89.0.11.EL. The crash could happen within hours or even minutes. I downgraded to 2.6.9-55.0.9.EL, which doesn't have the i500_edac module. Now that I have a PDU and remote KVM set up, I'm going to try other kernels tomorrow. -Philip ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] allowing users to issue the "shutdown" command
On 17-Oct-2009 Robert wrote: > > > Buz Davis wrote: >> I am running CentOS 5.3 and have just the two accounts "root" and >> "buz". I would like to be able to issue "shutdown" from the account >> "buz", and thus created >> /etc/shutdown.allow with the single entry "buz" (without any quotes). >> I still >> get the error message "only root can do this" (or something similar) >> even if I include the '-a' option on the shutdown command. What am I >> missing ? >> > I'm not going to verify this right now but I believe "buz" can execute > the command "poweroff" to shutdown -h now > and "reboot" to shutdown -r now. > > [...@mavis rj]$ ls -l `which poweroff` > lrwxrwxrwx 1 root root 13 Apr 2 2009 /usr/bin/poweroff -> > consolehelper > [...@mavis rj]$ ls -l `which reboot` > lrwxrwxrwx 1 root root 13 Apr 2 2009 /usr/bin/reboot -> > consolehelper > [...@mavis rj]$ >From the man page: If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked instead (with the -h or -r flag). For more info see the shutdown(8) manpage. -Philip ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] SATA controler req
Hello, I'm looking for a recomendation for a SATA controlers. In the range of 4-8 ports, either PCI or PCIe (for desktop use) and/or PCI-X, PCIe (for server use). I'd especially like it if the Linux driver was already in CentOS or easily added. Everytime I find something interesting, a google search shows up either the drivers is for 2.6.30 (ie, not CentOS), someone tried it and it was unstable, or it has a proprietary driver. They will be used as JBOD, with mdadm for RAID where I need it. Thank you, -Philip ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
