Re: 5.9: tar core dumps extracting a tar created on 4.8

2016-06-22 Thread Listas IT
> On Wed, Jun 22, 2016 at 12:14 PM, Listas IT <listas...@dna.uba.ar> wrote: >> When I try to extract a tar created by 4.8 base tar on a fresh installed >> 5.9 it dies with core dump and this message on syslog: >> >> Jun 22 16:08:52 un1 /bsd: tar(9316): syscall

5.9: tar core dumps extracting a tar created on 4.8

2016-06-22 Thread Listas IT
Hello When I try to extract a tar created by 4.8 base tar on a fresh installed 5.9 it dies with core dump and this message on syslog: Jun 22 16:08:52 un1 /bsd: tar(9316): syscall 14 "dpath" Jun 22 16:09:11 un1 /bsd: tar(19504): syscall 14 "dpath" Jun 22 16:10:55 un1 /bsd: tar(22328): syscall 14

Show us your /etc/profile

2015-07-31 Thread listas-it
Hello everybody How do you customize your environment? What aliases or custom functions do you use? Here's my /etc/profile I think you can find one or two interesting things in it. Show us yours! (in case wordwrapping breaks long lines: http://pastie.org/10322761)

5.7: dhclient ignoring routers option

2015-06-19 Thread listas-it
Hello dhclient on 5.7 won't set the client default gateway if other static routes are present (same problem exists on 5.6, at least). dhcpd server is running 5.6 stable with aprox 400 workstations and appliances/printers with mixed OSs and versions all working fine. At least both -windows and

Re: 5.7: dhclient ignoring routers option (SOLVED?)

2015-06-19 Thread listas-it
According to this: http://undeadly.org/cgi?action=articlesid=20140204080515mode=expanded This is expected behaviour as: Note that classless-static-routes overrides the router option, and that a default route must always be specified! There's no such warning in the man pages for dhclient or

How pf chooses nics on bridges?

2015-04-28 Thread Listas IT
Hello We have a 5.6-stable box doing transparent filtering with pf. blog log all is default on ruleset. The bridge is composed of fxp0 and vether0 on int net 192.168.192/23 and xl0 (internet). While doing normal work pflog0 shows this: 06:19:08.497855 rule 17/(match) block in on vether0:

Re: How pf chooses nics on bridges?

2015-04-28 Thread Listas IT
06:19:08.497855 rule 17/(match) block in on vether0: 192.168.193.41.3138 77.234.44.65.80: tcp 0 (DF) 06:19:08.546275 rule 17/(match) block in on fxp0: 192.168.193.28.59751 77.234.44.76.443: tcp 0 (DF) 06:19:08.582708 rule 17/(match) block in on fxp0: 192.168.192.146.61276