ok, here’s what is truly suspicious is in there: “/etc/cron.daily/shadow
/etc/cron.daily/makewhatis” - “#!/bin/sh

# Verify integrity of password and group files
/usr/sbin/pwck -r
/usr/sbin/grpck -r” - “#!/bin/sh
exec makewhatis -Tutf8
” “/etc/cron.hourly/0anacron” - "#!/bin/sh
# Check whether 0anacron was run today already
if test -r /var/spool/anacron/cron.daily; then
day=cat /var/spool/anacron/cron.daily
fi
if [ date +%Y%m%d = “day" ]; then
exit 0
fi

# Do not run jobs when on battery power
online=1
for psupply in /sys/class/power_supply/* ; do
if [ `cat "
psupply/type” 2>/dev/nullx = Mainsx ] && [ -f "$psupply/online" ]; then<br/> if [ cat “psupply/online" 2>/dev/null`x = 1x ]; then
online=1
break
else
online=0
fi
fi
done
if [
online = 0 ]; then
exit 0
fi
/usr/sbin/anacron -s”. all other dirs empty.
Thank you for providing the details of the suspicious cron jobs. Let’s analyze the contents of the cron files you mentioned:

1. /etc/cron.daily/shadow:
- This cron file is executing the commands /usr/sbin/pwck -r and /usr/sbin/grpck -r.
- These commands verify the integrity of the password and group files on your system.

2. /etc/cron.daily/makewhatis:
- This cron file has the command exec makewhatis -Tutf8.
- The makewhatis command generates the whatis database used by the man command, providing quick access to manual pages on your system.

3. /etc/cron.hourly/0anacron:
- This cron file contains a script that checks if 0anacron was already run today and exits if it has.
- It also checks if the system is on battery power and exits if it is.
- Finally, it executes the /usr/sbin/anacron -s command, which performs system maintenance tasks.

From the information you’ve provided, these cron jobs seem to be normal system maintenance tasks. The /etc/cron.daily/shadow file verifies the integrity of the password and group files, while /etc/cron.daily/makewhatis updates the whatis database. The /etc/cron.hourly/0anacron file runs anacron to perform various system maintenance tasks.

Given that the rest of the directories are empty, it indicates that other scheduled tasks aren’t present in those directories.

It’s essential to regularly review the contents of cron jobs to ensure they align with the intended actions on your system. If you have any further concerns or need additional analysis, please provide more details, and I’ll be glad to assist you.
but problem with multiple "agetty processes or instances still persist. I tried to fire some commands, but many isn’t working yet.
If you are experiencing issues with multiple “agetty” processes or instances, here are a few steps you can take to troubleshoot the problem:

1. Check if there are any “agetty” processes running:


   ps aux | grep agetty



2. If you find multiple instances of “agetty” processes running, you can try to restart the “agetty” service:


   systemctl restart agetty.service



3. Verify the status of the “agetty” service to ensure it is running without any errors:


   systemctl status agetty.service



4. Check the configuration of the “agetty” service and ensure it is correctly configured:


   cat /etc/systemd/system/getty.target.wants/agetty@.service



5. You can also check the system logs for any error messages related to “agetty”:


   journalctl -u agetty.service



It is important to note that further troubleshooting may require more specific information about your system and any error messages you encounter. If the issue persists or you need more assistance, it may be helpful to provide more details about the commands you have tried and any error messages you receive.

Additionally, you might consider seeking help from your system administrator or consulting relevant documentation or forums specific to your operating system distribution for more targeted troubleshooting steps.

there no any systemctl or service in my linux. also no logs I found through gnome cli commands you provided.
Apologies for the confusion. If your Linux system does not have systemctl or service available, it suggests that you might be using a different init system or a customized setup.

In that case, here are a few alternative methods you can try to troubleshoot the multiple “agetty” processes issue:

1. Identify the “agetty” processes using the following command:


   ps aux | grep agetty



2. Kill the “agetty” processes manually using the kill command and specifying the process IDs (PIDs) of the “agetty” processes. For example:


   kill <pid>



3. Check if the “agetty” processes reappear after killing them. If they do, it might indicate a deeper issue that requires further investigation.

4. Inspect the runlevel configuration to check if the number of “agetty” instances is intentional. The runlevel configuration files can be found in /etc/inittab or /etc/init/ directory. Look for entries related to spawning “agetty” instances and adjust them if needed.

Since different Linux distributions and setups may have variations in how they handle services and process management, it’s crucial to refer to the specific documentation or support channels for your distribution if you’re encountering difficulties or require further assistance with troubleshooting the “agetty” issue.

any way to scan the entire specific directory in “/etc/” for any presense of “agetty” in any files inside or else, by using gnome cli command or through thunar itself under some root?
To scan the entire contents of a specific directory such as /etc/<dirname> for any presence of “agetty” in any files, you can use the grep command in the GNOME CLI. Here’s an example command that you can run:

grep -r “agetty” /etc/<dirname>

Replace &lt;dirname&gt; with the actual name of the directory you want to scan, such as /etc/cron.d or /etc/init.d.

This command will recursively search for the string “agetty” within the files in the specified directory and display any matching lines.

Alternatively, you can also use the Thunar file manager to perform a search within the directory. Open Thunar, navigate to the desired directory (e.g., /etc/&lt;dirname&gt;), then use the search functionality within the file manager to search for the string “agetty” within the files in that directory.

Keep in mind that searching the entire directory structure in /etc or any important system directories may take some time, as these directories can contain a large number of files. Be patient while the search is being performed and review the results carefully.

Please note that performing searches and examining system directories typically require administrative access or superuser (root) privileges.                                                                                                                                                                                there's some strange duplicate commands in each "agetty" init dir as: "/agetty-tty6/" - "#!/bin/sh

tty=${PWD##*-}

[ -r conf ] && . ./conf

if [ -x /sbin/getty -o -x /bin/getty ]; then
	# busybox
	GETTY=getty
elif [ -x /sbin/agetty -o -x /bin/agetty ]; then
	# util-linux
	GETTY=agetty
fi

exec chpst -P ${GETTY} ${GETTY_ARGS} \
	"${tty}" "${BAUD_RATE}" "${TERM_NAME}"" - "#!/bin/sh
tty=${PWD##*-}
exec utmpset -w $tty" - "if [ -x /sbin/agetty -o -x /bin/agetty ]; then
	# util-linux specific settings
	if [ "${tty}" = "tty1" ]; then
		GETTY_ARGS="--noclear"
	fi
fi

BAUD_RATE=38400
TERM_NAME=linux".