233 reputation
413
bio website
location
age
visits member for 2 years, 3 months
seen 14 hours ago

May
14
comment Problem setting up iptables (LDAP traffic blocked)
OUTPUT packets are constantly increasing. This may be due to a few ajax checks running in the background.
May
14
comment Problem setting up iptables (LDAP traffic blocked)
I didn't add the RELATED,ESTABLISHED rule till a moment ago. LDAP authentication appears to be working properly now. Getting external data still failing however. Checking packets next.
May
14
comment Problem setting up iptables (LDAP traffic blocked)
Joel if you are still following could you help with the LDAP issue? Confirmed traffic is happening over 636 which I made exception for in my rules.
May
14
revised Problem setting up iptables (LDAP traffic blocked)
deleted 84 characters in body
May
14
comment Problem setting up iptables (LDAP traffic blocked)
Confirmed that the remote LDAP server operates over port 636.
May
14
comment Problem setting up iptables (LDAP traffic blocked)
I added watch -n1 to the netstat command, tried to log in to the app.. and am not seeing any entry for the LDAP server IP (or anything related to LDAP).
May
14
revised Problem setting up iptables (LDAP traffic blocked)
corrected ambiguous title from previous edit.
May
14
comment Problem setting up iptables (LDAP traffic blocked)
Is there a way to log data using the netstat -tlpn command? I ask because the LDAP query takes a microsecond, and if I am off by a little I won't see an LDAP entry in the list of results.
May
14
awarded  Yearling
May
14
asked Problem setting up iptables (LDAP traffic blocked)
Jan
20
awarded  Popular Question
Nov
19
accepted Check for existence of files prior to acting on them
Nov
19
comment Check for existence of files prior to acting on them
@terdon, the question is already updated.
Nov
19
comment Check for existence of files prior to acting on them
@terdon if you can update your answer to fit my question I'll re-accept your answer. Right now the answer doesn't fit on account of my omission of an important detail. (Sorry).
Nov
19
comment Check for existence of files prior to acting on them
ls is not what's in my script. Just used it as an example. I just found a better way of handling the problem: find /my/directory/ -type f \( -name "*.txt" \) -print
Nov
19
revised Check for existence of files prior to acting on them
Important piece of info left out - added now.
Nov
19
comment Check for existence of files prior to acting on them
I left an important detail from my question. It's been updated. My find command actually looks like this: find /my/directory/*txt -mtime +31 -exec ls -l {} \;
Nov
19
asked Check for existence of files prior to acting on them
Nov
7
comment Setting default username and group for files in directory
Ok thanks - I'll handle with groups.
Nov
6
comment Setting default username and group for files in directory
The question is about assigning ownership to newly created files. Group is already correctly assigned.