search for: hostalias

...Hostname zymurgy.anotherplace.com which is also simple enough, but then each of these has to include all the options that I've specified for *.anotherplace.com too. This is more awkward and messy than I think it should be. Potential solution 1: I'd like a new config directive like "HostAlias X Y" which would be something like this: When I do "ssh z" and it sees the .ssh/config line HostAlias z zymurgy.anotherplace.com then it replaces its idea of the hostname with zymurgy.anotherplace.com and then continues scanning the config file for options pertaining to that. P...

Hi, First things first, sorry for the off-topic, but I've already burned my eyes Googling and couldn't find the answer to what I need and I remembered asking here, because I'm a long time CentOS and its mailing list user. Again, my apologies. I have this command to create an FTP account: # pure-pw useradd mario -u 502 -g 502 -n 1000 -N 200 -d /home/pages/mario This command asks for

...This all works fine, except that every time you connect, it complains that the host key is wrong. I see that there is a configuration option "hostkeyalias" that can be used to circumvent this problem, but that is rather inconvenient, as i now need to type something like 'ssh -o "hostalias=foo.bar.com:4005" foo.bar.com -p 4005' What I think should happen: Connecting on a non-standard port should include the port number in the hostname automatically for hostkey lookup purposes, as in 'foo.bar.com:4005'. It should probably also use the host:port name for host-specific...

...just installed nagios et al[1] in my Centos-5.2 (x86). When I try to test the configuration file it fails[2] with the message "Unexpected token or statement(...)". The line is: command[notify-by-email]=/usr/bin/printf "$OUTPUT$" | /bin/mail -s '$SERVICESTATE$ alert for $HOSTALIAS$/$SERVICEDESC$' $CONTACTEMAIL$ But if I comment this line, then I got the same message in the next line. I changed the path to printf, because I already have installed. Is something missing? Are the rpm's enough? Thanks Marcelo [1] newt (Linux) $rpm -qa | grep nagios nagios-plugins-...

...I fail to see what the harm would be in storing the port number as part of the known hosts database. In the rare cases where there were two ports on the same SSH server that did use the same key, it's not like this would cause the user any problems. Furthermore, it is not clear how to use the HostAlias option in a configuration file to do the right thing. It may well be possible, but the documentation does not explain it adequately. Suppose I have a machine "firewall", and port 1234 on its IP address is mapped to port 22 on an internal host "foo". I tried putting the follow...

Dear Srs, I'm trying to automount an iSCSI device at system startup, this is the configuration: - CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, i686 arch - iscsi-initiator-utils 6.2.0.865-0.8.el5 - iSCSI target is a Infortrend A16E-G2130-4 I have solved the "initial_login_retry_max" problem [1] and Open- iSCSI logs into Infortrend target without problems, with 10 retries in

Dear Srs, I'm trying to monitor CPU temperatures in a PowerEdge 860 server, running CentOS 5.1 with 2.6.18-53.1.6.el5 kernel, using lm-sensors v2.10.0. Running "sensors-detect" I get: ====================================================================== (..) We can start with probing for (PCI) I2C or SMBus adapters. You do not need any special privileges for this. Do you want

Dear Srs, I'm getting this error when trying to connect to a Infortrend A16E- G2130-4 storage v?a iSCSI. > Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP > Apr 29 10:24:41 vz-10 kernel: Vendor: IFT Model: A16E- > G2130-4 Rev: 361F > Apr 29 10:24:41 vz-10 kernel: Type: Direct- > Access ANSI SCSI revision: 04 > Apr

Dear Srs, yum-updatesd-0.9-2.el5 appears that it's not working on freshly installed CentOS 5.2, using: # rpm -qa "yum*" yum-metadata-parser-1.1.2-2.el5 yum-updatesd-0.9-2.el5 yum-3.2.8-9.el5.centos.2.1 yum-fastestmirror-1.1.10-9.el5.centos I see some bugs ([1], [2] and [3]) in the bug tracker, and more info related to other distros like Fedora, etc.. with the same problem.