Sponsored Content
Operating Systems Linux Learning scrapers, webcrawlers, search engines and CURL Post 303022711 by TBotNik on Wednesday 5th of September 2018 03:12:33 PM
Old 09-05-2018
Neo,


Think you're right about not re-inventing the wheel! Looking for code now!


Cheers!


PS


Did you get my email?
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

I dont want to know any search engines

I just want to know where I can download it on this website plz (1 Reply)
Discussion started by: memattmyself
1 Replies

2. UNIX for Dummies Questions & Answers

Using cURL to save online search results

Hi, I'm attacking this from ignorance because I am not sure how to even ask the question. Here is the mission: I have a list of about 4,000 telephone numbers for past customers. I need to determine how many of these customers are still in business. Obviously, I could call all the numbers.... (0 Replies)
Discussion started by: jccbin
0 Replies

3. Shell Programming and Scripting

Checking status of engines using C-shell

I am relatively new to scripting. I am trying to develop a script that will 1. Source an executable file as an argument to the script that sets up the environment 2. Run a command "stat" that gives the status of 5 Engines running on the system 3. Check the status of the 5 Engines as either... (0 Replies)
Discussion started by: paslas
0 Replies
SXID(1) 						      General Commands Manual							   SXID(1)

NAME
sxid - check for changes in s[ug]id files and directories SYNOPSIS
sxid [ --config <file> ] [ --nomail ] [ --spotcheck ] [ --listall ] DESCRIPTION
Sxid checks for changes in suid and sgid files and directories based on its last check. Logs are stored by default in /var/log/sxid.log. The changes are then emailed to the address specified in the configuration file. The default location for the config file is /etc/sxid.conf but this can be overridden with the --config option and specifying an alternate location. OUTPUT
The program outputs several different checks concerning the current status of the suid and sgid files and directories on the system on which it was run. This is a basic overview of the format. In the add remove section, new files are preceded by a '+', old ones are preceded by a '-' NOTE: that removed does not mean gone from the filesystem, just that it is no longer sgid or suid. Most of it is pretty easy to understand. On the sections that show changes in the file's info (uid, gid, modes...) the format is old->new. So if the old owner was 'mail' and it is now 'root' then it shows it as mail->root. The list of files in the checks is in the following format: /full/path *user.group MODE (MODE is the 4 digit mode, as in 4755) In the changes section, if the line is preceded by an 'i' then that item has changed inodes since the last check (regardless of any s[ug]id change), if there is an 'm' then the md5sum has changed. If a user or group entry is preceded by a '*' then it's execution bit is set (ie. *root.wheel is suid, root.*wheel is sgid, *root.*wheel is +s). On the forbidden directories, if ENFORCE is enabled an 'r' will precede forbidden items that were succesfully -s'd, and an '!' will show that it was unsuccesfully -s'd (for what ever reason). OPTIONS
-c, --config <file> specifies an alternate configuration file -n, --nomail sends output to stdout instead of emailing, useful for spot checks -k, --spotcheck Checks for changes by recursing the current working directory. Log files will not be rotated and no email sent. All output will go to stdout. -l, --listall Useful when doing --spotcheck or --nomail to list all files that are logged, regardless of changes. AUTHOR
Ben Collins <bcollins@debian.org> REPORTING BUGS
Report bugs to current maintainer Timur Birsh <taem@linukz.org>. SEE ALSO
sxid.conf(5) sXid 4.0.5 January 2002 SXID(1)
All times are GMT -4. The time now is 03:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy