freshclam ClamAV update process started at Sun Mar 20 00:30:50 2022 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.100.3 Recommended version: 0.103.5 DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav main.cld is up to date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) WARNING: getpatch: Can't download daily-26337.cdiff from db.local.clamav.net WARNING:........

#!/bin/bash sshcommand="ssh -N -R 20000:localhost:22 user@8.8.8.8" result=`ps aux|grep $sshcommand"|grep -v grep` if [ -z "$result" ]; then echo "we are going to connect" $sshcommand else echo "we are already connected" fi This is a handy script you can use and then add it to cron. Save........

< a href="/Products/MX72244"> < span class="c-shca-icon-item__body-name-brand"> ADATA < / span> &nbs........

freshclam ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!). ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log). Tue Oct 13 13:49:35 2015 -> WARNING: Incremental update failed, trying to download daily.cvd Tue Oct 13 13:49:35 2015 -> WARNING: Can't download daily.cvd from db.local.clamav.net Tue Oct 13 13:49:35 2015 -> Trying again in 5 secs...........

I had a system running a 128MB live CD image with 2.8 gigs of available RAM and the OOM kernel killer went crazy when using dd for more than 8 minutes and kept killing everything. I've read that this is due to a low-memory issue and paging in the kernel and 32-bit systems with lots of RAM. I even enabled swapspace on my LiveCD and the issue happened 25 minutes into dd rather than 8 minutes, so what gives? Also no swap space was ever used! cat /proc/s........

http://www.datsi.fi.upm.es/~frosal/ SHC is a program written by the author above that does just that, it's a great little tool to have. Some have said it isn't exactly encrypting the code but just making it hard to read by obfuscating the code. There was also a good discussion about that here:........

CPU/Kernel/MB/RAID problem? Jan 5 12:45:05 testbox kernel: [653298.890004] BUG: soft lockup - CPU#0 stuck for 61s! [hal-acl-tool:4168] Jan 5 12:45:05 testbox kernel: [653298.890005] Modules linked in: vmnet vmci vmmon binfmt_misc drbd video output input_polldev ocfs2_stackglue ocfs2_dlmfs ocfs2_dlm ocfs2_nodemanager configfs k8temp hwmon_vid lp snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi........

This is obviously a bug in the r8169 kernel module and it seems to affect a lot of people. I upgraded to the latest kernel and hope this won't happen anymore, as it is a very serious error. This is especially serious for those who are running servers with this chipset, who can afford for the NIC to randomly go off-line for no apparent reason? [655548.189113] type=1505 audit(1277067560.902:5): operation="profile_load" name="/usr/bin/freshclam&q........

When trying to even cd or ls the mounted OCFS2 partition it crashes. Ithink this is a combination of VMWare Server's problem and the way I mounted and symlinked to it. More than anything this shows the problem and lack of forsight with VMWare, but also that OCFS2 is easily crashed if you do strange things. Output of /var/log/messages for OCFS2 Apr 10 15:57:45 localhost kernel: [84331.691258] Modules linked in: vmnet vmci vmmon ocfs2_stac........