kelnet.net

It seems that all *nix versions do automount and nfs slightly different than each other.  I was setting up a automount on AIX 5.2L and discovered that I needed a nfs.direct file in /etc to mount to a directory.  Anyway, it looks like this:

/etc/nfs.direct

/oracle -rw,hard,intr tulnfs01:/data/oracle

/etc/auto_mount

/-      /etc/nfs.direct

Once those files are created, you can run /etc/rc.nfs and the nfs subsystem along with automount will start.

Good simple instructions for upgrading a cisco 2950 switch in four steps.

Cisco escape sequence: Ctrl + Shift + 6

Ok, I always forget and have to google it so here it is….

http://perl.about.com/od/packagesmodules/qt/perlcpan.htm

There are several ways to get Perl modules from CPAN installed on your unix-based system. Keep in mind that there is always more than one way to do it with Perl, and this is no different. Before embarking upon any installation, it’s a good idea to download the module, unzip it and check out the documentation. In general, though, most modules are installed in the same method.
The simplest way to get Perl modules installed is to use the CPAN module itself. If you are the system administrator and want to install the module system-wide, you’ll need to switch to your root user. To fire up the CPAN module, just get to your command line and run this:

perl -MCPAN -e shell

If this is the first time you’ve run CPAN, it’s going to ask you a series of questions - in most cases the default answer is fine. Once you find yourself staring at the cpan> command prompt, installing a module is as easy as install MODULE::NAME - for example, to install the HTML::Template module you’d type:

cpan> install HTML::Template

CPAN should take it from there and you’ll wind up with the module installed into your Perl library.
Let’s say you’re on your system command line and you just want to install a module as quickly as possible - you can run the Perl CPAN module via command line perl and get it installed in a single line:

perl -MCPAN -e ‘install HTML::Template’

As I mentioned earlier, it’s always advisable to download a module yourself, especially if you’re having problems installing with CPAN. If you’re on the command line, you can use something like wget to grab the file. Next you’ll want to unzip it with something like:

tar -zxvf HTML-Template-2.8.tar.gz

This will unzip the module into a directory, then you can move in and poke around - look for the README or INSTALL files. In most cases, installing a module by hand is still pretty easy, though (although not as easy as CPAN). Once you’ve switched into the base directory for the module, you should be able to get it installed by typing:

perl Makefile.PL
make
make test
make install

Working with windows 2003 can be somewhat awkward when running jobs via the scheduler so I was wondering if cygwin cron can be installed.  Sure enough, good old google came through with the following:

http://www.mail-archive.com/cygwin@cygwin.com/msg31579.html

The easiest way is to follow the ssh-host-config script in
creating a special account:

  net user cron_server <passwd> /add /yes
  net localgroup <administrators_group_name> cron_server /add
  editrights -a SeAssignPrimaryTokenPrivilege -u cron_server
  editrights -a SeCreateTokenPrivilege -u cron_server
  editrights -a SeIncreaseQuotaPrivilege -u cron_server
  editrights -a SeServiceLogonRight -u cron_server
  mkpasswd -l -u cron_server >> /etc/passwd

For security reasons:
  editrights -a SeDenyInteractiveLogonRight -u cron_server
  editrights -a SeDenyNetworkLogonRight -u cron_server
  editrights -a SeDenyRemoteInteractiveLogonRight -u cron_server

And then create a cron service using that account:
  cygrunsrv -I cron -p /usr/sbin/cron -a -D -u cron_server -w <passwd>

Just installed Fedora Core 9 and discovered the method I had been using to setup a tty console has changed.  Originally, I would add the following to the /etc/inittab file:

co:2345:respawn:/sbin/agetty -t 60 19200 ttyS0 vt102

After adding this line I would then issue the command init q to re-read the inittab file and start the agetty session.

Well, I see that there is now a /etc/events.d directory which contains various script files for configuring various things including the serial console via the file serial.  At first I thought I would need to create a file ttyS0 which would then be added to the run list by issuing the command initctl start ttyS0.  I was partially correct by doing this, and it seemed to work, but I kept getting a login screen after logging in.  As it turns out, the existing file ’serial’ is already setup for tty access to a console.  So, I just had to stop and remove the ttyS0 process.

Upon further investigation, I see that this new init process is called upstart which is a replacement for the Sys V init process and is published by Ubunto.

This brings up an interesting thought concerning qmail.  Most qmail installs use the daemontools to start and stop processes.  This new method for starting and stopping processes in FC9 is very similar to daemontools.