Sponsored Content
Full Discussion: Our system was hacked
Special Forums Cybersecurity Our system was hacked Post 303037153 by Neo on Wednesday 24th of July 2019 10:51:59 PM
Old 07-24-2019
Turn on logging including router logging and closely monitor the logs.

Create a honeypot to lure the hackers into your logging traps, if you are interested to discover who is responsible.

Good job on keeping your backups up to date!
This User Gave Thanks to Neo For This Post:
 

3 More Discussions You Might Find Interesting

1. Linux

pc hacked

Hi, i think someone has hacked my server, the following rules used to come which i haven't put. Please help me i couldnt find out how this rules are apply, i think someone has put an script which generates enables the rules. But after restarting the iptables everything seems to be working... (0 Replies)
Discussion started by: naik_mit
0 Replies

2. Cybersecurity

How to know when you've been hacked

One of the most important ways to keep tou machine secure is to know when it has been broken into. The less time hackers have on your system, the less they can do to it, and the greater you chancens of kicking them off and repairing the damage. The more sophisticated the hacker, the less likely... (8 Replies)
Discussion started by: binhnx2000
8 Replies

3. Cybersecurity

Server hacked on known port

Hi, There is a recent case whereby it was reported that one of the production servers was hacked on port 1521. However, I am not sure how this was possible, as I checked that the OS firewall (iptables) is on : # /etc/init.d/iptables status Table: nat Chain PREROUTING (policy ACCEPT) num ... (7 Replies)
Discussion started by: anaigini45
7 Replies
vollogcnvt(8)						      System Manager's Manual						     vollogcnvt(8)

NAME
vollogcnvt - Logical Storage Manager BCL-to-DRL logging conversion utility SYNOPSIS
/usr/sbin/vollogcnvt [-g diskgroup] OPTIONS
Limits the conversion of logging subdisks to volumes in the specified disk group. DESCRIPTION
The vollogcnvt script is a migration tool for Logical Storage Manager (LSM) administrators who are currently using the block-change logging (BCL) feature. Beginning with the Version 5.0 release of Tru64 UNIX, the BCL feature of LSM is being replaced with the dirty-region logging (DRL) feature. The vollogcnvt script attempts to convert volumes with BCL enabled to volumes with DRL enabled. If called without specifying a disk group, vollogcnvt attempts the BCL-to-DRL conversion for all volumes across all disk groups. If logging cannot be re-enabled in the DRL scheme, a warning is sent to the console. For volumes whose BCL subdisks will not work in the DRL scheme, logging is disabled. Log subdisks that cannot be converted to DRL will be disassociated from its volume only if at least one of the log subdisks for that volume could be converted. Otherwise, the configuration will not change and logging will be disabled. Those volumes that could not be converted, for example all of its log subdisks are too small, will have logging disabled. At system startup, the vollogcnvt script runs automatically and logs such errors to binlog and sends mail to root. This happens at each reboot until the DRL is manually converted or when logging is disabled. If the script runs at startup or manually, warnings are sent to the console. For details and guidelines on using DRL, refer to the Logical Storage Manager guide. SEE ALSO
binlogd(8), dia(8), volintro(8) vollogcnvt(8)
All times are GMT -4. The time now is 03:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy