similar to: odd line in current CVS for firewall

I think you can change the existing firewall logging code for log_rule_limit (where you have one case for for LOGRULENUMBERS and another almost identical case without) down to this slightly shorter version with no duplication (excerpt): if [ -n "$LOGRULENUMBERS" ]; then eval rulenum=\$${chain}_logrules [ -z "$rulenum" ] && rulenum=1 fi case

rsync-2.4.6-2mdk I ran an rsync into a file system that filled up. I got no error message out of rsync - it just stopped and exited sliently. I stuck an fprintf into the receiving code and verified that the proper error was being generated - it just never gets printed by the rsync sending process. I submitted a bug report about it; but, I can't believe that other people haven't had

I want to use --min-size to copy just large files (and their necessary parent directories), but everything I've tried copies *all* the source directories, and creates them empty on the destination even if they don't have any big files in them. I only want the minimal directory hierarchies that contain the big files. This doesn't work: $ rm -rf /tmp/foo $ rsync -ai --min-size

I''m re-reading the section on dns names in the shorewall docs: "I personally recommend strongly against using DNS names in Shorewall configuration files. If you use DNS names and you are called out of bed at 2:00AM because Shorewall won''t start as a result of DNS problems then don''t say that you were not forewarned." Having been stung by this a few times

This rule with a long name and logging: AllowInternetPrintingProtocol:debug causes this iptables error: Processing /etc/shorewall/rules... Rule "AllowSSH:info net fw" added. Rule "AllowPing:info net fw" added. Rule "AllowWeb:debug net fw" added. iptables v1.2.9: Maximum prefix length 29 for --log-prefix Try `iptables

I almost always use "-u" with rsync so that I don't overwrite remote files that have changed. The only way to get rsync to tell me which remote files are "newer" is to use a double-v (-vv), which produces way more output than I care to see. (In true Unix fashion, I don't care to see what was done successfully; I only want to see what failed.) I've always had to

I have some pictures that I unload from the camera into: dir/tmp and at night I automatically rsync all of dir/ to some remote:dir/ Then days or weeks later I do some local sorting, and I make lots of image moves of the sort where image dir/tmp/bar goes to to dir/category1/bar, possibly linked also into dir/category2/bar. Then rsync runs the next night, notices the "new" image

These two small changes enable 3.0.6 to compile and link on AIX 3.2: diff -r rsync-3.0.6/lib/getaddrinfo.c rsync-3.0.6-new/lib/getaddrinfo.c 298c298 < if (!inet_aton(node, &ip)) { --- > if (!inet_pton(AF_INET, node, &ip)) { diff -r rsync-3.0.6/lib/sysacls.c rsync-3.0.6-new/lib/sysacls.c 1817a1818 > #if defined(ENOTSUP) 1818a1820,1822

Rsync version: rsync-2.5.6-3mdk (Mandrake 9.2) I see from the CVS log that some of the following awkwardness may be fixed (or at least different) in the next public release. I'm looking forward to that. In the interim, here are some problems: --------- Problem 1 - unexpected consequence of replacing / with ** --------- The following exclude works because the explicit slash causes a match

Ian has proposed that we change the way that logging interacts with defined actions. Currently, if logging is specified on the invocation of an action (e.g., "AllowFTP:info all all"), all traffic sent to the AllowFTP chain is logged. In most cases, this isn''t what the user intended and other people have expressed surprise about this behavior in the past. The way I see this

The params file appears to be simply "sourced" by the firewall script, which means one can put any Bourne shell code into it and it will execute it. This feature isn''t documented, so I''m wondering if it can be documented and thus guaranteed to always work. I''d like to dig out the IP parameters of my interface cards from the ifcfg-eth? files and set shorewall

My Linux workstation (Mandrake 10.1 kernel 2.6.8.1) is dual-homed to two ADSL Internet providers. Card eth0 (192.168.9.250) is the default route and leads to an SMC router (192.168.9.254). Card eth1 (192.168.1.250) leads to a Linksys router (192.168.1.1). I''m not doing any NAT or PPPoE in the workstation - the SMC and Linksys handle it all. I know four commands that let you set an IP

What I want is a client-side log file itemized list of *all* the changes that rsync did on the remote machine. Using "--log-file" doesn't show everything. In particular, --log-file says nothing if the remote directory was populated using hard links from a --link-dest source. Any number of remote links and directories can be created, with no mention of any of it in the log file.

Hi, it seems not to be possible to add more than one host at once to a zone. So shorewall add br0:eth0:192.168.2.10,eth0:192.168.2.11 work fails, since "br0:eth0:192.168.2.10,eth0" is interpreted as one interface. --snip -- iptables v1.2.9: interface name `eth0:192.168.2.10,eth0'' must be shorter than IFNAMSIZ (15) Try `iptables -h'' or ''iptables

My Linux workstation (Mandrake 10.1 kernel 2.6.8.1) is dual-homed to two ADSL Internet providers. Card eth0 (192.168.9.250) is the default route and leads to an SMC router (192.168.9.254). Card eth1 (192.168.1.250) leads to a Linksys router (192.168.1.1). I''m not doing any NAT or PPPoE in the workstation - the SMC and Linksys handle it all. If I remove all general default routes from

Hello ext3-users, We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25. I noticed many of these errors in our logs. EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884828: directory entry across blocks - offset=0, inode=404600689, rec_len=23080, name_len=59 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #966714: rec_len % 4 != 0 -

I've not been happy with the stories about the "stable" 2.4.x kernels. Everywhere I read people saying "not for production use". Would you recommend adding ext3 to 2.2.19 (ext3-0.0.7a) or moving to 2.4.1x and using ext3 there (ext3-0.9.12)? -- -IAN! Ian! D. Allen Ottawa, Ontario, Canada idallen@ncf.ca Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

I'm getting only partial iso8859-1 translation from an smbfs mount from my Win98SE machine. The smbfs mounted file system shows most lower-case accented characters fine; but, it substitutes underscores for most of the upper-case accented characters (and a few lower-case ones too): # uname -a Linux elm 2.4.18-8.1mdkian3 #7 Sat Aug 17 15:19:44 EDT 2002 i686 unknown (Mandrake 8.2 Linux with all

Hi RedHat 7.2, ext3 on /, kernel 2.4.18p1. whilst updatedb was running, i had these messages appear... Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 - offset=0, inode=1651076143, rec_len=19527, name_len=85 Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory