Tag Info

Hot answers tagged

3

These two logrotate.conf options might help you: missingok If the log file is missing, go on to the next one without issuing an error message. See also nomissingok. notifempty Do not rotate the log if it is empty (this overrides the ifempty option). For more information, see man logrotate.


2

Couple of tools for you: lsof shows you the open file handles iotop shows the process-wise I/O statistics in the top manner nethogs shows you the per-process network traffic strace allows you to see what a process is doing


2

802.1Q tag is inserted into MAC header, and kernel won't decode it if your interface isn't VLAN tagged. So, even if you could mangle outgoing packets, incoming traffic with VLAN tag would stay ignored. What you need to do is create a VLAN tagged interface, just as you did, and add an IP to it within the same rage the switch IP you're trying to access is in. ...


2

iptables and ebtables can't set VLAN tags on packets. That's what VLAN sub-interfaces are for. There's an article on the Ubunut wiki that discusses VLANs that you should probably review. In summary, though, you want to: Make sure the 802.1q module is loaded with a modprobe 80211q. Create the VLAN sub-interface with vconfig add eth0 444. Add an IP ...


1

In this kind of situation I often found very useful to capture the NFS traffic (e.g., with tcpdump or Wireshark) and have a look at it to see if there is a specific reason for the high load. For example, you can use something like: tcpdump -w filename.cap "port 2049" to save only NFS traffic (being on port 2049) to a capture file, then you can open that ...


1

You are missing a space after apt/: http://apt.postgresql.org/pub/repos/apt/ precise-pgdg


1

I am not a Ubuntu guy, you may want to look into this solution w/ pam_tally2 http://askubuntu.com/questions/338588/limit-user-login-attempts-ubuntu-12-10-pam-tally-so-pam-tally2-so


1

It looks like I needed to specify the backend to get this to working. It was defaulting to gamin whih wasn't working. I changed the configuration to backend = polling and got fail2ban working properly. Haven't received any email notifications of blocking, but I'm close to figuring that out too.


1

I would modify the previous answer from JorSol to sudo cp $WILDFLY_HOME/bin/init.d/wildfly-init-debian.sh /etc/init.d/wildfly because his command would create a security exploit should anyone be able to gain the permissions of wildfly and modify $WILDFLY_HOME/bin/init.d/wildfly-init-debian.sh.



Only top voted, non community-wiki answers of a minimum length are eligible