Sponsored Content
Top Forums Shell Programming and Scripting Extracting and comparing values Post 303019708 by RudiC on Wednesday 4th of July 2018 09:08:14 AM
Old 07-04-2018
Try (p+0 < g+0 ? ...
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

comparing two float values

I am trying to compare 2 float values using if the foll code does not work a=1.4 b=1.6 if test $a -gt $b then echo "$a is max" else echo "$b is max" fi does -gt work for floating point numbers, if not how do go about for my requirement? can i use bc ? pls help thanks in advance... (2 Replies)
Discussion started by: kavitha
2 Replies

2. Shell Programming and Scripting

Extracting values from files

Im trying to create a utility that can do unit conversions using a seperate formula file(one which i can add conversions to at a later date). however i'm stuck when it comes to pulling the formulas out of the formula file for use in the script. heres a rundown of what the script does. The... (4 Replies)
Discussion started by: Master Error
4 Replies

3. Shell Programming and Scripting

comparing values of same variable

Hello all while writing a small script , i got stuck with this simple thing.Hope you guyz can help. Iam trying to read password echo"enter password" read $pwd now i have to check this echo"enter password to proceed" read $pwd now i have to check both the values of the... (2 Replies)
Discussion started by: coolkid
2 Replies

4. Shell Programming and Scripting

comparing values

i have two file and i am comparing both.. in cmp1 ,the content is : the nu of file is : <some integer value> in cmp2 ,the content is : the nu of file is : so want a script which will take value (2) when cmp1 is compared with cmp2.. i mean cmp cmp1 cmp2 the the output will be he nu of... (1 Reply)
Discussion started by: Aditya.Gurgaon
1 Replies

5. Shell Programming and Scripting

Comparing values in column 1

Hi to all, I have the following text within inputfile data1,value1,value2 data1,value3,value2 data1,value5,value6 data2,value1,value2 data2,value3,value4 data3,value1,value2 data3,value3,value4 data4,value1,value2 data4,value3,value4 data4,value5,value6 I would like to... (4 Replies)
Discussion started by: cgkmal
4 Replies

6. Shell Programming and Scripting

Extracting dynamic values

Hi, I am stuck with extracting values by combining 2 dynamically extracted values. The code goes like this #!/usr/bin/ksh ID1="abcd" i=1 #this is a dynamic value and keeps on changing b="ID" #this is static now i want the value of ID1 variable. like echo $b$i But echo... (1 Reply)
Discussion started by: chaitanyapn
1 Replies

7. Shell Programming and Scripting

awk script doubt in extracting and comparing uid

Hi, I need to get the value of 'uid' from a line in file f1. For example, in the line below, I need to get the value '150', from the 'anonuid=150' key, and I need to verify that this is a valid uid by checking it against /etc/passwd (i.e) I want to compare this uid, 150 (or more if there are any... (2 Replies)
Discussion started by: royalibrahim
2 Replies

8. Shell Programming and Scripting

Extracting a portion of the string and comparing

I have 2 text files say file1.txt and file2.txt . Some of the sample records for file1.txt were shown below: XXXXX12345XXXXXXX12 3456789YYYYY XXXXXXXXXX12345XX123457485YYYYY XX12345XXXXXXXXXX123454658YYYYY for file2.txt, some of the sample records were shown below: ... (5 Replies)
Discussion started by: bobby1015
5 Replies

9. Shell Programming and Scripting

Comparing the values of two files

Hi Am trying to compare the values of two files.. One is a big file that has many values and the other is a small file.. The big file has all values present in small file.. # cat SmallFile 4456602 22347881 7471282 15859891 8257690 21954701 7078068 18219229 2883826 6094959 100000 ... (3 Replies)
Discussion started by: Priya Amaresh
3 Replies

10. Shell Programming and Scripting

Taking key values from one file and extracting values from another file

Hi, I have two files with values in both. File1: cat 2 3 dog 4 5 elephant 6 7 camel 2 3 File2: ----+--gkf;ajf= ---+---- +----- cat -------=----+ 3 | 4 ----- dog ------++-- 5 | 9 ----++-- elephant | 5 | 7 ---++ camel ------ ++++_---- || 8 | 9 I want the final file as: cat 4... (1 Reply)
Discussion started by: npatwardhan
1 Replies
UNHIDE(8)						      System Manager's Manual							 UNHIDE(8)

NAME
unhide -- forensic tool to find hidden processes SYNOPSIS
unhide [OPTIONS] TEST_LIST DESCRIPTION
unhide is a forensic tool to find processes hidden by rootkits, Linux kernel modules or by other techniques. It detects hidden processes using six techniques. OPTIONS
-f Write a log file (unhide.log) in the current directory. -h Display help -m Do more checks. As of 2010-11-21 version, this option has only effect for the procfs, procall, checkopendir and checkchdir tests. Implies -v -r Use alternate version of sysinfo check in standard tests -V Show version and exit -v Be verbose, display warning message (default : don't display). This option may be repeated more than once. TEST_LIST The checks to do consist of one or more of the following tests. The standard tests are the aggregation of one or more elementary test(s). Standard tests : The brute technique consists of bruteforcing the all process IDs. This technique is only available on Linux 2.6 kernels. The proc technique consists of comparing /proc with the output of /bin/ps. The procall technique combinates proc and procfs tests. This technique is only available on Linux 2.6 kernels. The procfs technique consists of comparing information gathered from /bin/ps with information gathered by walking in the procfs. With -m option, this test makes more checks, see checkchdir test. This technique is only available on Linux 2.6 kernels. The quick technique combines the proc, procfs and sys techniques in a quick way. It's about 20 times faster but may give more false posi- tives. This technique is only available on Linux 2.6 kernels. The reverse technique consists of verifying that all threads seen by ps are also seen in procfs and by system calls. It is intended to ver- ify that a rootkit has not killed a security tool (IDS or other) and make ps showing a fake process instead. This technique is only available on Linux 2.6 kernels. The sys technique consists of comparing information gathered from /bin/ps with information gathered from system calls. Elementary tests : The checkbrute technique consists of bruteforcing the all process IDs. This technique is only available on Linux 2.6 kernels. The checkchdir technique consists of comparing information gathered from /bin/ps with information gathered by making chdir() in the procfs. With the -m option, it also verify that the thread appears in its "leader process" threads list. This technique is only available on Linux 2.6 kernels. The checkgetaffinity technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getaffinity() system function. This technique is only available on Linux 2.6 kernels. The checkgetparam technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getparam() system function. This technique is only available on Linux 2.6 kernels. The checkgetpgid technique consists of comparing information gathered from /bin/ps with the result of call to the getpgid() system func- tion. This technique is only available on Linux 2.6 kernels. The checkgetprio technique consists of comparing information gathered from /bin/ps with the result of call to the getpriority() system function. This technique is only available on Linux 2.6 kernels. The checkRRgetinterval technique consists of comparing information gathered from /bin/ps with the result of call to the sched_rr_get_inter- val() system function. This technique is only available on Linux 2.6 kernels. The checkgetsched technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getscheduler() system function. This technique is only available on Linux 2.6 kernels. The checkgetsid technique consists of comparing information gathered from /bin/ps with the result of call to the getsid() system function. This technique is only available on Linux 2.6 kernels. The checkkill technique consists of comparing information gathered from /bin/ps with the result of call to the kill() system function. Note : no process is really killed by this test. This technique is only available on Linux 2.6 kernels. The checknoprocps technique consists of comparing the result of the call to each of the system functions. No comparison is done against /proc or the output of ps. This technique is only available on Linux 2.6 kernels. The checkopendir technique consists of comparing information gathered from /bin/ps with information gathered by making opendir() in the procfs. This technique is only available on Linux 2.6 kernels. The checkproc technique consists of comparing /proc with the output of /bin/ps. This technique is only available on Linux 2.6 kernels. The checkquick technique combines the proc, procfs and sys techniques in a quick way. It's about 20 times faster but may give more false positives. This technique is only available on Linux 2.6 kernels. The checkreaddir technique consists of comparing information gathered from /bin/ps with information gathered by making readdir() in /proc and /proc/pid/task. This technique is only available on Linux 2.6 kernels. The checkreverse technique consists of verifying that all threads seen by ps are also seen in procfs and by system calls. It is intended to verify that a rootkit has not killed a security tool (IDS or other) and make ps showing a fake process instead. This technique is only available on Linux 2.6 kernels. The checksysinfo technique consists of comparing the number of process seen by /bin/ps with information obtained from sysinfo() system call. This technique is only available on Linux 2.6 kernels. The checksysinfo2 technique is an alternate version of checksysinfo test. It might (or not) work better on kernel patched for RT, preempt or latency and with kernel that don't use the standard scheduler. It's also invoked by standard tests when using the -r option This technique is only available on Linux 2.6 kernels. Exit status: 0 if OK, 1 if a hidden or fake thread is found. BUGS
Report unhide bugs on the bug tracker on sourceforge (http://sourceforge.net/projects/unhide/) SEE ALSO
unhide-tcp (8). AUTHOR
This manual page was written by Francois Marier francois@debian.org and Patrick Gouin. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foun- dation. LICENSE
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Administration commands October 2010 UNHIDE(8)
All times are GMT -4. The time now is 04:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy