It recently came up that it would be helpful if we had a cheat sheet to find out the machine names for any given UNIX. I knew these off the top of my head but it would be great if people added more as comments.
HP/HP-UX: /bin/uname -i
IBM/AIX: /bin/uname -m
SGI/IRIX: /sbin/sysinfo -s
Sun/Solaris: /usr/ucb/hostid
Just recently I seem to have noticed an increased number of mysterious crashes and terminations of applications. This is generally on brand new systems that I’m setting up, or on existing systems where I’m setting up a new or duplicate account.
Initially everything is fine, but then all of a sudden as I start syncing over my files, shell profile and so on applications will stop working. I’ve experienced it in MySQL, and more recently when starting up Gnome on Solaris 10 9/07.
Sometimes the problem is obvious, other times it takes me a while
to realize what is happening and causing the problem. But in all
cases it’s the same problem - my TMPDIR environment
variable points to a directory that doesn't exist. That's because
for historical reasons (mostly related to HP-UX, bad permissions
and global tmp directories) I've always set TMPDIR to a directory
within my home directory. It's just a one of those things I've
had in …
Recently I had some trouble with the server where all of my websites are hosted. Business site, various blogs, there is lots of stuff on there, not to mention backups of work, email, and all sorts of things I do not really want to lose.
I first noticed the trouble when I couldn’t login through the command line. Strangely the websites were still running. I called the hosting company, and after talking with them for a while, managed to login as root. That was working. But it was acting quite odd. There were some errors in the /var/log/messages about ssh not being able to set uid 10003, the uid of my login, shull. I pondered. I thought. I sat circumspect.
I investigated for a while, and called up 1 & 1 again. I have a root server, but they’re not really supposed to support maintaining the machine itself. Then I got to thinking, I could spend hours diagnosing …
[Read more]Beta or not, here we come. Yea, you'd think I'd learn to check out the known bugs list before letting developers/qa have at the new database servers running in the lab with MySQL 5.1.21-b . I mean, how bad could beta really be?Well, as we should all know, beta is called beta for a reason, but sometimes we open source fanatics tend to jump on board, dealing with issues along the way. This
Recently I've spent hours compiling MySQL 5.1.22 and trying to get my cent0s configured for innodb and partitioning. I tried every imaginable way to run configure, use different plugins, etc.I messed with this forever, then finally looked at the config options, and sure enough, the ./configure expects innobase, not innodb as the plugin name: from: http://www.innodb.com/support/tips On MySQL
So if you like to try out new things, and you're not using VMWare yet, get with the program!Really, though - it's so easy now (and the VMServer is free) . Just download and install.VMWare lets you run mini virtualized server environments within your current operating system. Yea, there is a little overhead, but for testing and trying out new databases, configurations, applications, it's