clearing space error codes..optimizing my unix based network, help... 1

[jbay]

hi my name is james...i recently inherited a unix based network of 6 terminals...the system runs only one application and that app is called 'patrol command' are you familiar with ?...this is my 1st exposure to this operating system, unix, i've never used it before now...i'm beyond frustrated and have come here to you for help, assistance and guidance...i'm able to log in at two areas, the root or in the application itself...i could feel that this system is in dire need of diagnostics and plain ol help...after log in it displays that it is -unix system v/88 release r32v3 version 960907 m88100- 1st question what version is this unix...? the app it runs is used by the company for general all around office purposes, scheduling, acctng, report logs, personnel info, and the sort...we are a security firm...the main problem encountered by some all to frequently, is an error message about exceeding space threshhold and certain aspects of the application do not function properly if at all, a 10-07 error...the makers of this application do not offer any tech support what so ever...the previous sysadm suggested that i &quot;shitcan&quot; the whole system and start fresh with a whole new platform and setup...yes thats why i was brought on board here but that wont happen for awhile (budgetting woes)...in anycase i want to maintain this system and setup to one train on unix and for whatever other reason...i've tried every suggestion from some at allexperts.com but to no avail...they werent clear with their suggestions or maybe i just didnt get what they were saying...some commands dont click, it's a mess of a system ...but i truly believe that i can fix it with your help if not get it to run as optimumly as possible...my email at work is <A HREF="mailto:rgscom@aol.com">rgscom@aol.com</A>, work # is 808-536-5765 xt245...if youre in hawaii as i am on oahu you can call...please always send responses to that adress <A HREF="mailto:rgscom@aol.com">rgscom@aol.com</A>, lastly i want to thank you for your time and help with my tasks, i greatly appreciate it and will reasonably at anytime return the favor...i anxiously await your response...take care and mahalos!...james

 

[AndyBo]

James, sounds like you've been dropped in at the very deepest end of the pool! Unix isn't renowned for being the most user friendly OS in the world to pick up, especially if you're used to MS produced OSes. However, once you get into the whole Unix philosophy, and start to learn how to get around, you'll realise how powerful it is.<br>
<br>
However, don't fear, we're here to help! <br>
<br>
First, that Unix version... It's not one that I'm familiar with, but I can take a few stabs in the dark...<br>
<br>
unix system v/88 release r32v3 version 960907 m88100<br>
<br>
The whole version breaks down into a few key components. The first is the &quot;system v/88&quot;. This indicates it's a system V (as in 5) based Unix. The 88 is probably a indicator that it's compiled for Motorola processeors... That's because the &quot;m88100&quot; indicates the CPU - Motorola 88100. The whole thing taken together tells me it's not a common version of Unix, so support would be very difficult to get, I think. What is the hardware platform?<br>
<br>
Second, the error message you get. This looks like it is from the application, and not from Unix. Probably some inbuilt space usage check. IT could be that your filesystems are getting a little full. If you want to check how much space you have free, log in as &quot;<FONT FACE=monospace>root</font>&quot; and type &quot;<FONT FACE=monospace>df -k</font>&quot;. If that doesn't work, try a plain &quot;<FONT FACE=monospace>df</font>&quot;.<br>
<br>
If available space is getting low, you'll need to start removing files, trimming log files, etc. to create some free space. However, don't do this until you are very confident you know what the files you are removing are there for! If you want to check, for example, &quot;I've got 250Mb of files in a directory called /tmp. Is it OK to remove them?&quot; then I'm sure you'd get a good answer here on TT. <br>
<br>
Now, a few general tips to get you started.<br>
<br>
* To see what a command does, type &quot;<FONT FACE=monospace>man <i>command_name</i></font>&quot;. If this doesn't work, try &quot;<FONT FACE=monospace>help <i>command_name</i></font>&quot;, or just plain &quot;<FONT FACE=monospace>help</font>&quot;. (Tip: &quot;<FONT FACE=monospace>man man</font>&quot; will tell you how the man command works <br>
<br>
* Invest in some reading material. I'd recommend <b>any</b> Unix book published by O'Reilly. Head over to <A HREF="

http://unix.oreilly.com"

TARGET="_new">

http://unix.oreilly.com</A>

for a full list, but for a start I'd recommend &quot;Learning the UNIX Operating System&quot;, &quot;Learning the vi Editor&quot;, &quot;UNIX in a Nutshell: System V Edition&quot;, and &quot;UNIX Backup and Recovery&quot;.<br>
<br>
* Check if there is an &quot;adduser&quot; command on your system. If not, then look for &quot;useradd&quot;. Then create yourself a new user, that does not have root privileges. It's extrememly dangerous! (Remind me to tell you about the time I was logged in as root, pwd was &quot;/&quot;, and I <i>thought</i> I'd typed &quot;rm -r /mytempdir&quot;. What I'd actually typed was &quot;rm -r / mytempdir&quot;... Where did I put those backups?...)<br>
<br>
* If you can, get hold of a spare PC (486 or better) and install Linux. Linux is Unix - it's only politics that stops it from using the Unix name. If you do this then you have a modern Unix system that you can learn on. And it's a great way to learn. If you decide to do this then there are &quot;Linux (Server)&quot; and &quot;Linux (client/desktop)&quot; forums here on TT.<br>
<br>
Sorry for going on a little, but it sounds like you're in a bit of a hole at the moment!<br>
<br>
Hope this has helped a little, and good luck!

 

[mrregan]

James,<br>
You may also be experiencing a file size maximum problem which is governed by a parameter called 'ulimit'. You can type in 'ulimit' at the command prompt to see how many 512 char blocks a file can have. For example , if the ulimit is <br>
20,000 the file size maximum is about 10mb. You could go to the root directory and enter <br>
'find . -size +20000000c -print' to see if there are any files over 20mb. The ulimit parameter can be usually be found in the '/etc/profile' and can be changed. Let us know.

 

[MikeLacey]

Andy's comment about the Nutshell books is worth repeating - I've got about 6 of the things now - they're excellent.<br>
<br>
Mike <p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>

 

[jbay]

i ask for a miracle and i get 3...thank you each--andybo-mrregan-mike lacey-- for your input...its fun learning this new stuff...i will be getting linux soon and practicing with it and as for this nightmare of a system i have now i will be implementing all of the suggestions...oreilly and i are great friends already...i'll rport back as to me progress and any further tools and steps to take about this system i have please send them my way...andy, i invite you to go on and on and on and on so long as it pertains to getting this system at optimum level/functionality...keep it comin'....i'll type to you guys in a bit...jamea<br>
<p>james bay<br><a href=mailto:rgscom@aol.com>rgscom@aol.com</a><br><a href= > </a><br>please bare with me with regard to my questions...i'm trying to comprehend the vast concepts as they apply to computers in general and at times forget the KISS philosophy!

 

[jbay]

ok check this out i did a &quot;d&quot; and a &quot;df&quot; at my root prompt...it came back with this set of numbers and foreign language....<br>
<br>
&quot;d&quot;--&gt; / free: 33.1mb, full: 43%, total size: 59mb<br>
/usr &quot; : 0.3mb, &quot; : 99%, &quot; &quot; : 98mb<br>
/bms &quot; : 90.3mb, &quot; : 70%, &quot; &quot; : 308mb<br>
<br>
what in the unix world does the above mean and how do i alleviate some of the noticeable space crunching goin on particularly in /usr and /bms...<br>
<br>
&quot;df&quot;--&gt; / (/dev/dsk/m187m_00so): 67696 blocks 12598i-nodes<br>
/usr (/dev/usr ): 672 blocks 21212 i nodes<br>
/bms (/dev/dsk/m187_00s3): 184880 blocks 62469 i nodes<br>
now...what does this say and is there trouble...<br>
<br>
the hardware is indeed a motorolla tower, got a 25mhz processor and 32 megs of ram..any way of displaying what other hardware i have within this system...<br>
<br>
but 1st things 1st, how do make more space from the &quot;d&quot; info above and how do i recreate a fresh directory of the same name after i delete one to release space...please get back to me as soon as you can...and god only knows how much i appreciate you for taking the time and effort in helping me ....mahalos my friend...james<br>
<p>james bay<br><a href=mailto:rgscom@aol.com>rgscom@aol.com</a><br><a href= > </a><br>please bare with me with regard to my questions...i'm trying to comprehend the vast concepts as they apply to computers in general and at times forget the KISS philosophy!

 

[AndyBo]

Glad to be of help, James <br>
<br>
OK, as you say, first things first - the lack of space reported by &quot;d&quot;...<br>
<br>
Your &quot;/&quot; and &quot;/bms&quot; filesystems look to have plenty of free space. The &quot;/usr&quot; filesystem is way, way, too crowded. This may be causing the &quot;10-07&quot; errors you mentioned in your original post. As a rule of thumb, when a filesystem gets to 10% free, I start to look at it. In your case, 0.3% free, especially on &quot;/usr&quot;, is cause for a little concern. (Don't freak out with worry, though, because Unix is pretty good at handling full filesystems, with a couple of exceptions. eg, filling &quot;/var&quot; on some versions of Unix can cause problems.) Now, not knowing exactly how your system is set up, a quick warning.<br>
<br>
MAKE SURE YOU HAVE VALID BACKUPS BEFORE REMOVING ANYTHING, AND THAT YOU KNOW HOW TO RESTORE THEM!!!<br>
<br>
Just wanted to get that off my chest, cos backups are important... <br>
<br>
OK, now for a couple of places you can look for stuff to remove on &quot;/usr&quot;...<br>
<br>
<FONT FACE=monospace>/usr/lost+found</font>&nbsp;&nbsp;&nbsp;&nbsp;If this directory exists, it's safe to remove anything in it. It's used by the filesystem checking tools (<FONT FACE=monospace>fsck</font>) to store &quot;problem&quot; files in the event of a filesystem problem.<br>
<br>
<FONT FACE=monospace>/usr/tmp</font>&nbsp;&nbsp;&nbsp;&nbsp;Reboot the system. Check if there are any files left in this directory. Use &quot;<FONT FACE=monospace>ls -l</font>&quot; to check the dates of files in this directory. Anything not dated with today's date can be removed.<br>
<br>
<FONT FACE=monospace>/usr/adm/log</font>&nbsp;&nbsp;&nbsp;&nbsp;Log files live here. Look for files with &quot;log&quot; in their name. Use &quot;ls -l&quot; to see how big they are. View them using &quot;view&quot;, &quot;more&quot;, &quot;pg&quot;, or &quot;vi&quot;. If you can live without them, blank them out using &quot;<FONT FACE=monospace>&gt;/usr/adm/log/name_of_log_file</font>&quot;<br>
<br>
Use the &quot;<FONT FACE=monospace>rm</font>&quot; command to remove files. And if you have <b>any</b> doubt about removing a file, don't do it! Better safe than sorry. We don't want you ending up with a system that won't boot because a critical file has been removed...<br>
<br>
As far as the &quot;/bms&quot; filesystem goes, this still has 30% of it's space free - I wouldn't worry about it for now.<br>
<br>
The output from the &quot;<FONT FACE=monospace>df</font>&quot; command is showing information about mounted filesystems. Taking the first line as an example:<br>
<br>
/ (/dev/dsk/m187m_00so): 67696 blocks 12598i-nodes<br>
<br>
This tell us that the root (&quot;/&quot filesystem is the physical disk device /dev/dsk/m187m_00so. This disk partition has 67696 blocks in total, and 12598 i-nodes. Try running &quot;<FONT FACE=monospace>df -k</font>&quot; - this should show similar information to the &quot;<FONT FACE=monospace>d</font>&quot; command you mentioned. If not, then it's probably an old version of &quot;df&quot; on your server.<br>
<br>
Just to go over that output from &quot;d&quot;...<br>
<br>
/ free: 33.1mb, full: 43%, total size: 59mb<br>
<br>
The root filesystem (&quot;/&quot has 59Mb in total, is 43% full, and has 33.1Mb of disk space free.<br>
<br>
Hope this helps a little. <br>