I am responsible for administering 6 Tru64UX servers.
I need to keep an eye on all the commands executed by all the users.
Is there a way where I can save the commands executed in a seperate folder and then keep checking the list every now and then.
How can do it ? (5 Replies)
Hi!! Experts,
I have a typical scenario here in which several users have access to a particular login .. say "build".
None of the users know the passwd for this login.
The name of some of the user have been to .rhosts file.
The users can connect only by doing a rlogin to this id and then... (4 Replies)
hi,
i need help writing shell scripts to define patterns of user activities on our apache.
i thought about going through logfiles and other places where user activities are stored and use that data to define patterns of action. i want these patterns to be visualized then.
now my... (3 Replies)
Hello,
I'm administrating new installed cluster that runs Legato Networker and Oracle 9. And I want to restrict the use of root to my self and givr the application and DBA the proper and needed privileges to do their duties without hassle in addition I would like to log users activities.
my... (0 Replies)
Hi all,
I want to automate a set of activities i am doing daily.the activities in the order are:
1.loging in to the unix box.
2.sudo su - tsiap, give pwd
3. cd appsrv
4. cd log
5. run the below cmd one by one, if you find any query which has run for more than 5 secs, open the... (1 Reply)
Recently i have attended a telephonic interview. As i dont have work experience in solaris i was not able to deliver correct answer for this question.
Your answer will help for the people like me who is looking to become Solaris System administrator. (4 Replies)
hi I need a shell script which runs perpetually in background and monitors different aspects of different users on different files and their usages
for example say there r 3 users
so i want when they log in i.e. their log in time and their file access, modify and change log of each file of a... (3 Replies)
Greetings to all.
I need help from the experts. I have been given a FTP server script that runs all day, looking for files that are FTP'd to our machines. Its hoaky I know, but there are times that files are sent but somehow get lost. Is there a logfile I can view to see when files are received?
... (1 Reply)
SUSE Linux 11 and 10 SP3.
I am trying to capture some of my activities in SYSLOG file, /var/log/messages.
To do this I created and dropped some test files and directories and users. But these activities are not captured in /var/log/messages. What should I do to make these activities... (7 Replies)
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted entire table .... (1 Reply)
Discussion started by: Perlbaby
1 Replies
LEARN ABOUT NETBSD
compress
COMPRESS(1) BSD General Commands Manual COMPRESS(1)NAME
compress, uncompress -- compress and expand data
SYNOPSIS
compress [-cdfv] [-b bits] [file ...]
uncompress [-cdfv] [file ...]
DESCRIPTION
compress reduces the size of the named files using adaptive Lempel-Ziv coding. Each file is renamed to the same name plus the extension
``.Z''. As many of the modification time, access time, file flags, file mode, user ID, and group ID as allowed by permissions are retained
in the new file. If compression would not reduce the size of a file, the file is ignored.
uncompress restores the compressed files to their original form, renaming the files by deleting the ``.Z'' extension.
If renaming the files would cause files to be overwritten and the standard input device is a terminal, the user is prompted (on the standard
error output) for confirmation. If prompting is not possible or confirmation is not received, the files are not overwritten.
If no files are specified, the standard input is compressed or uncompressed to the standard output. If either the input and output files are
not regular files, the checks for reduction in size and file overwriting are not performed, the input file is not removed, and the attributes
of the input file are not retained.
The options are as follows:
-b Specify the bits code limit (see below).
-c Compressed or uncompressed output is written to the standard output. No files are modified.
-d Force decompression.
-f Force compression of file, even if it is not actually reduced in size. Additionally, files are overwritten without prompting for
confirmation.
-v Print the percentage reduction of each file.
compress uses a modified Lempel-Ziv algorithm. Common substrings in the file are first replaced by 9-bit codes 257 and up. When code 512 is
reached, the algorithm switches to 10-bit codes and continues to use more bits until the limit specified by the -b flag is reached (the
default is 16). Bits must be between 9 and 16.
After the bits limit is reached, compress periodically checks the compression ratio. If it is increasing, compress continues to use the
existing code dictionary. However, if the compression ratio decreases, compress discards the table of substrings and rebuilds it from
scratch. This allows the algorithm to adapt to the next "block" of the file.
The -b flag is omitted for uncompress since the bits parameter specified during compression is encoded within the output, along with a magic
number to ensure that neither decompression of random data nor recompression of compressed data is attempted.
The amount of compression obtained depends on the size of the input, the number of bits per code, and the distribution of common substrings.
Typically, text such as source code or English is reduced by 50-60%. Compression is generally much better than that achieved by Huffman cod-
ing (as used in the historical command pack), or adaptive Huffman coding (as used in the historical command compact), and takes less time to
compute.
The compress utility exits 0 on success, and >0 if an error occurs.
SEE ALSO zcat(1)
Welch, Terry A., "A Technique for High Performance Data Compression", IEEE Computer, 17:6, pp. 8-19, June, 1984.
HISTORY
The compress command appeared in 4.3BSD.
BSD January 23, 2003 BSD