On Wed, 31 Jul 2013 09:59:56 PM Chris Samuel wrote: > I've noticed that our authorized_keys file had a leading blank line for > some reason, so perhaps that was confusing the SSH implementation > on the MIC? I've removed that and will rebuild the image and try again.
Sadly no such luck. :-( One thing that would be a useful addition would be to add a script to start up the BusyBox syslogd with remote syslog back to the MN, that should be possible with somehow running: /sbin/syslogd -R [MN IP] I tried adding to the overlay an /etc/rc3.d/S01syslogd file that would run it, but it doesn't seem to work for me (again I see it end up in the filesystem on the node, but no syslog messages are reported on the MN). It is possible it's already running I guess, but I can't tell without being able to login. All the best, Chris -- Christopher Samuel - Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.unimelb.edu.au/ ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
