Search results for query: *

Go into /etc/security/login.cfg and change the herald statement in the default stanza to something a bit less specific. An example would be:&nbsp;&nbsp;<br><br>default:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;herald = &quot;\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nUnix Support...

Did you use crontab -e to edit the crontab file? If so this will automatically read in the new commands. As you stated that you have little or no unix experience I'd guess that you just edited the crontab file. To get cron to re-read the crontab file find the process number of cron and do a kill...

Put all you application and database shutdown scripts in /etc/rc.shutdown. Make sure it's executable then all your stuff will shutdown cleanly.<br><br>Dave <p>Dave Hamilton<br><a href=mailto:dhamilton@gio.com.au>dhamilton@gio.com.au</a><br><a href= > </a><br>

I assume you're in ftp. If so then before doing your mput use the command prompt. This will stop ftp asking you for confirmation before each file is sent.<br><br>Dave <p>Dave Hamilton<br><a href=mailto:dhamilton@gio.com.au>dhamilton@gio.com.au</a><br><a href= > </a><br>

Another option is to use timed <p>Dave Hamilton<br><a href=mailto:dhamilton@gio.com.au>dhamilton@gio.com.au</a><br><a href= > </a><br>

I've had narrow tape drives on wide SCSI buses for a while. My understanding is that the whole bus will now only work to the speed of the slowest devices, which is now the tape drive. I haven't had any tape drive errors like yours so I'd actually look into servicing the drives themselves...

I think you're out of luck. Something I learnt a long time ago was that if it's important back it up, if it's not important back it up anyway as someone else will need it when it's gone........ <p>Dave Hamilton<br><a href=mailto:dhamilton@gio.com.au>dhamilton@gio.com.au</a><br><a href= > </a><br>

Check in /etc/security/limits. You've probably got fsize in the default stanza set to 2GB. Change it to -1 and then you've got unlimited file sizes.<br><br>Hope this fixes your problem <p>Dave Hamilton<br><a href=mailto:dhamilton@gio.com.au>dhamilton@gio.com.au</a><br><a href= > </a><br>

Working with &quot;Large File Enabled&quot; filesystems is really no different than working with &quot;normal&quot; filesystems. When I build my filesystems as large file enabled I always increase the number of bytes per inode which gives you more usable space in the filesystems which can come...

I've had something similar on AIX. It was a corrupted client index and to resolve it I had to delete the client which then allowed me to manually remove the bad index file. I could then recreate the client and recover the indexes from a previous backup. <p>Dave Hamilton<br><a...

I've seen this exact meeage on a model 250. To get around it you need to turn the key from service to normal, then when the number has changed to c45 you turn it back to service. This will bypass the error and allow you to continue on with the upgrade. <p>Dave Hamilton<br><a...

The other thing you can try when terminals play up like that is to type in stty sane. <p>Dave Hamilton<br><a href=mailto:dhamilton@gio.com.au>dhamilton@gio.com.au</a><br><a href= > </a><br>

We use a DLT7000's in a Storage Tek 9710 silo plus a few stand alone DLT7000's. We haven't had a problem with the drives or media in terms of stability. They are very slow to load up before you can start writing to them, up to 45 seconds, but with Legato Networker we are streaming 4 filesystems...

Another free one you could try is "top".