Re: tar and --include

2010-05-19 Thread Tim Kientzle

b. f. wrote:

Martin McCormick wrote:

   What I discovered was that --include doesn't appear to
do anything at all. The example in the man page shows using it
to filter an existing archive ...  I never
tried that since that is not what was needed here.


The --include directive was designed to support the
case of filtering an existing archive.  GNU tar has
no equivalent to bsdtar's @archive feature and hence
has no real need for --include.

If you really need detailed control over which
files get archived, I do recommend learning how
to use find(1) in conjunction with tar.  (Just remember
to use tar's -n option!)


There certainly seems to be a bug here, either in the documentation or
the implementation.  The example you mention works as expected for me
on 9-CURRENT, but the --include option fails on, for example:

tar -cvf new.tar --include='baz'  foo/bar


In your example here, the first item
tar inspects is foo/bar, which does not match
the pattern and therefore is not included.
Excluding a directory excludes everything
in the directory.

The net result is the same as if you had specified:
   tar -cvf new.tar --exclude='foo/bar' foo/bar

Cheers,

Tim

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: pkgtools and xz compressor

2010-01-11 Thread Tim Kientzle

b. f. wrote:

I notice FreeBSD 7.2's pkg_add, pkg_create, etc don't have support for
the xz compressor, evidently due to lack of support for the xz format
in bsdtar.  Does bsdtar support xz in FreeBSD 8.0?


If you have the xz port installed, yes.  If you have liblzma
installed, you can even recompile libarchive with native
xz support by following the comments in lib/libarchive/Makefile.


Failing that, is
xz support for the pkgtools something being looked at in future?


Yes, xz support is being looked at.

Lzma-family compression has been of interest for some
time but there have been a number of technical issues.
The xz format seems to address those but the software
is still in beta.  Once a final production version of
the xz software is available, I expect it to be imported
into FreeBSD-CURRENT fairly quickly.

Cheers,

Tim

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: single SATA disk and yet identified as 'ad4'

2009-05-11 Thread Tim Kientzle

Saifi Khan wrote:


The system has just one SATA disk and yet bootloader process
identified it as 'ad4'. Ideally, it should be ad1.

00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller 
(rev 01)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI 
Controller (rev 01)


The ide interface gets ad0, ad1, ad2, ad3,
the sata controller numbering starts with ad4.

Tim
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: firefox3 with high latencies when acting with mouse or keyboard and graphics refresh

2009-04-08 Thread Tim Kientzle

I saw something similar recently due to a mismatch
between hald and the xorg server.  In my case, it
affected all applications, not just firefox.
* Are you running hald?
* Do you have AllowEmptyInput set in /etc/X11/xorg.conf?
* Are you starting xdm, kdm, or gdm from /etc/ttys?

Tim

O. Hartmann wrote:

Hello,
got a problem since yesterday after having done a lot of updates 
(ports): on all of my FreeBSD 8.0-CURRENT/amd64 boxes firefox does have 
enormous high latencies when typing in or moving the mouse or popping up 
the window icon or down. Since this happens on all of 8.0-CUR/amd boxes, 
I guess it has something to do with an upgrade of the ports.


I reinstalled firefox twice, but without success, so I want to ask for 
some hints..


Regards,
Oliver
___
freebsd-curr...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: tar: Unrecognised archive format: Inappropriate file type or format

2007-06-05 Thread Tim Kientzle

Robert,

I recently saw your message on freebsd-questions.

Can you give me any more details?

Tim Kientzle



List:   freebsd-questions
Subject:tar: Unrecognised archive format: Inappropriate file type or format
From:   Robert Davison rob_27_preston () yahoo ! co ! uk
Date:   2007-03-20 22:27:20
Message-ID: 923906.54344.qm () web25007 ! mail ! ukl ! yahoo ! com
[Download message RAW]

I've been using tar to back-up my file system to my tape drive using the 
following command
   
  tar -cvf /dev/sa0 /home /etc
   
  which works fine.
   
  Whenever i run the command
   
  tar -tvf /dev/sa0
   
  the system usualy lists a few file then stops with the error
   
  tar: Unrecognised archive format: Inappropriate file type or format
   
  I'm using the latest RC6.2
   
  I've never had this problem before...

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: tar -u adds all files regardless of mod date

2005-09-27 Thread Tim Kientzle

Thanks, Gareth.

I'm hoping to get some time this week to backport a lot of changes from
bsdtar/libarchive in -CURRENT back to 5-STABLE.  I'll let you know when
I get that done.

Tim

Gareth Bailey wrote:

Just to add, I seem to be experiencing similar behaviour using the -P option:

# tar -P -cvf archive.tar /usr/archive/Pimani/
.. files get added
# tar -P -uvf archive.tar /usr/archive/Pimani/
a /usr/archive/Pimani/Pimani Presentation/multimedia/August
2005/LM_001_PRINT_050119/Thumbs.db
a /usr/archive/Pimani/Pimani Presentation/multimedia/August 2005/26
August/t-shirtlogomany.gif

Result: Directory structure was static but two files were added again.

The non-absolute path workaround worked fine:

# cd /
# tar -cvf archive.tar usr/archive/Pimani/
.. files added
# tar -uvf archive.tar usr/archive/Pimani/

Result: No files were added again (good).

Just to bring to your attention.

Gareth Bailey

On 9/27/05, Gareth Bailey [EMAIL PROTECTED] wrote:


Hi Tim,



5-STABLE is sufficiently different that the patch doesn't apply,
unfortunately.  It will take me a few days to figure out whether
it's best to work up a different patch for 5-STABLE or whether
I should MFC a lot of work from 6-STABLE to 5-STABLE.


Unfortunately our server is also on the 5 stable branch.



Please check that the following does work (without the leading '/'):

 tar -cf foo.tar usr/dir_a/dir_b
 tar -uvf foo.tar usr/dir_a/dir_b


This works just fine. Thank you for response and suggested workarounds.

Gareth Bailey









___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: tar -u adds all files regardless of mod date

2005-09-21 Thread Tim Kientzle

Gareth Bailey [EMAIL PROTECTED] writes:


I have a directory I want to backup at /usr/dir_a/dir_b.
I want to back the content of this dir to /usr/backups/dir_b
so I tried the following:


Lowell Gilbert clarified:


[This essentially adds up to doing 
 # tar -cf foo.tar $target_path
and then immediately 
 # tar -uvf foo.tar $target_path

shows an update.]


Hrrmph.  Looks like the pathname rewrite (stripping leading '/')
is getting done too late, so that the wrong filenames are
being compared.

Please check that the following does work (without the leading '/'):

   tar -cf foo.tar usr/dir_a/dir_b
   tar -uvf foo.tar usr/dir_a/dir_b

Assuming that works correctly, I know where the mistake is;
I'll have a tentative patch for you to try in a couple of hours.

Tim Kientzle

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: tar -u adds all files regardless of mod date

2005-09-21 Thread Tim Kientzle

Lowell Gilbert wrote:

Gareth Bailey [EMAIL PROTECTED] writes:


... If i then try to update modified files by doing this:

# tar -uf dir_b.tar /usr/dir_a/dir_b

and I end up with dir_b.tar being 130MB (double size) which
should not be the case since no files have been modified in
/usr/dir_a/dir_b.


The attached patch should fix this problem for 6-STABLE and 7-CURRENT
systems.  If someone could try it for me and let me know if
it works for them, I'd greatly appreciate it.

5-STABLE is sufficiently different that the patch doesn't apply,
unfortunately.  It will take me a few days to figure out whether
it's best to work up a different patch for 5-STABLE or whether
I should MFC a lot of work from 6-STABLE to 5-STABLE.

The crux of the problem is that bsdtar compares files on disk
to files in the archive by pathname before it strips leading '/'
characters.  As a result, it tries to compare /usr/dir_a on disk
to usr/dir_a in the archive, which fails.

A temporary workaround is to not use absolute pathnames:

   cd / ; tar -uf dir_b.tar usr/dir_a/dir_b

Another workaround is to use -P both when creating and when
updating the archive.

The attached patch causes bsdtar to do all pathname editing
before it does the time comparison for -u.  I think that
correctly fixes this problem.

Tim

P.S. If you're testing this, do not use touch to update
timestamps.  If you do, you will get some very confusing
results because touch updates high-precision timestamps,
but the default tar format only stores whole seconds.
This seems hard to fix.
Index: write.c
===
RCS file: /home/ncvs/src/usr.bin/tar/write.c,v
retrieving revision 1.41
diff -u -r1.41 write.c
--- write.c 8 May 2005 06:25:15 -   1.41
+++ write.c 22 Sep 2005 04:46:00 -
@@ -643,15 +643,12 @@
tree_descend(tree);
 
/*
-* In -u mode, we need to check whether this
-* is newer than what's already in the archive.
-* In all modes, we need to obey --newerXXX flags.
+* Write the entry.  Note that write_entry() handles
+* pathname editing and newness testing.
 */
-   if (new_enough(bsdtar, name, lst)) {
-   write_entry(bsdtar, a, lst, name,
-   tree_current_pathlen(tree),
-   tree_current_access_path(tree));
-   }
+   write_entry(bsdtar, a, lst, name,
+   tree_current_pathlen(tree),
+   tree_current_access_path(tree));
}
tree_close(tree);
 }
@@ -686,6 +683,13 @@
if (edit_pathname(bsdtar, entry))
goto abort;
 
+   /*
+* In -u mode, check that the file is newer than what's
+* already in the archive; in all modes, obey --newerXXX flags.
+*/
+   if (!new_enough(bsdtar, archive_entry_pathname(entry), st))
+   goto abort;
+
if (!S_ISDIR(st-st_mode)  (st-st_nlink  1))
lookup_hardlink(bsdtar, entry, st);
 
@@ -1235,10 +1239,6 @@
 */
if (bsdtar-archive_dir != NULL 
bsdtar-archive_dir-head != NULL) {
-   /* Ignore leading './' when comparing names. */
-   if (path[0] == '.'  path[1] == '/'  path[2] != '\0')
-   path += 2;
-
for (p = bsdtar-archive_dir-head; p != NULL; p = p-next) {
if (strcmp(path, p-name)==0)
return (p-mtime_sec  st-st_mtime ||
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: cpio and tar are loosing flags (and a panic message without trace)

2005-09-20 Thread Tim Kientzle

Matthew Dillon wrote:

:
:I guess cpio and tar really should take care about flags. Am I wrong?

cpio won't do it, tar won't do it, dump only does whole partitions,
cpdup is not an archiver.  Hmm.


Actually:

  * Joerg Schilling's star has done this for many years.

  * bsdtar has likewise supported it for a long time (apart from recent 
breakage sigh).



There's very little precedent for flags support in cpio format, though a 
cpio that supported modern tar formats should be able to support it.


Pax should support it (though ours does not currently).

Tim

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cpio and tar are loosing flags (and a panic message without trace)

2005-09-05 Thread Tim Kientzle

Emanuel Strobl wrote:

Am Montag, 29. August 2005 12:37 CEST schrieb Yar Tikhiy:


On Fri, Aug 26, 2005 at 08:04:45PM +0200, Emanuel Strobl wrote:


Then I remember Tim Kienzles great work for bsdtar and all the ACL
stuff, but unfortunately a cvPPzf  xvpPfz also looses the arch flag
:(


Would you mind sending a PR on this issue with [EMAIL PROTECTED]
in Cc:?  I believe Tim will be interested in it.  I've just confirmed
myself using not-too-old CURRENT that bsdtar won't restore file
flags stored in its own archive:


Thanks for the report.  I've just committed a fix to -CURRENT
for this issue.

Let me know if this addresses the problem for you.

Cheers,

Tim



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: bsdtar '--exclude pattern' problems

2004-11-30 Thread Tim Kientzle
Karol Kwiatkowski wrote:
Lowell Gilbert wrote:
According to the tar(1) manual, the file parameters are supposed to
come after all of the option parameters.
Ah, of course! I don't know why I wrote it wrong (some months ago
probably). Thank you.
gtar and bsdtar do parse options a little
differently, so a few people may need to
adjust their scripts.
Rationale: gtar requires the GNU
getopt library and exploits a few special
features of that library. bsdtar is designed
to work with several different getopt
libraries, so restricts itself to
somewhat more generic behavior.
Tim Kientzle
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Logging packets dropped by IPFW

2003-07-07 Thread Tim Kientzle
Is there any way to generate log information
about the packets dropped by IPFW?  The 'log'
modifier doesn't seem to do anything on my
system right now sigh, though from what I can tell,
it's supposed to only log the rule that was
triggered, which isn't the same thing at all.
In particular, I'd like to know the protocol
(TCP/UPD/ICMP) and port number for dropped packets.
Tim Kientzle

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Logging packets dropped by IPFW

2003-07-07 Thread Tim Kientzle
Micheal Patterson wrote:
- Original Message - 
From: Tim Kientzle [EMAIL PROTECTED]
Subject: Logging packets dropped by IPFW

Is there any way to generate log information
about the packets dropped by IPFW?  The 'log'
modifier doesn't seem to do anything ...

options IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
optionsIPFIREWALL_VERBOSE_LIMIT=100#limit verbosity
Thanks, Micheal.  The manpage didn't
mention that logging was a compile-time
option; I'm recompiling now...
Tim

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Logging packets dropped by IPFW

2003-07-07 Thread Tim Kientzle
Tim Kientzle wrote:
Micheal Patterson wrote:
- Original Message -
 From: Tim Kientzle [EMAIL PROTECTED]
Subject: Logging packets dropped by IPFW

Is there any way to generate log information
about the packets dropped by IPFW?  The 'log'
modifier doesn't seem to do anything ...

options IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
optionsIPFIREWALL_VERBOSE_LIMIT=100#limit verbosity 
Thanks, Micheal.  The manpage didn't
mention that logging was a compile-time
option; I'm recompiling now...
Took another very careful look at the manpage,
and discovered that recompiling wasn't necessary
after all:
# sysctl net.inet.ip.fw.verbose=1

suffices to turn it on.  The IPFIREWALL_VERBOSE
compile option just changes the default for this sysctl.
Make this permanent by adding the line:
net.inet.ip.fw.verbose=1

to /etc/sysctl.conf.

Tim

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Changes in /bin/sh between 4.6.2 and 4.7

2003-01-24 Thread Tim Kientzle
Murat Bicer wrote:


  killall freevrrpd  /dev/null 21   echo -n 'freevrrpd'



The construction 'a   b' has always been
complete nonsense and the shell no longer accepts it.
(The '' means check the output of the
preceding command, which isn't possible
with 'a ' being run in the background.)

If you mean to wait until 'killall' finishes,
use just ''.  If not, use just ''.

Tim Kientzle


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Update and mailforward.

2003-01-24 Thread Tim Kientzle
Gannater Jnos wrote:


How can I update my program's on the 
computer and in the fututre the whole system? I have only a 90Mhz 
pentium processor. So downloading the source and installing the 
program from it would be a very hard thing for me.


Two choices:

1) Buy new CDs when they come out.
2) Download the source and upgrade that way.
   (Just plan to wait a couple of days for it to compile! ;-)

If you're not having any problems, option 1 is probably
the best one for you.



I use sendmail. How can I forward my messages?



One option is to not forward your messages.  Rather,
install 'qpopper' or 'popper' from the ports and
let your users access their mailbox using any POP3-capable
email client (e.g., Outlook Express, Netscape Mail, Eudora, etc.)

Tim Kientzle




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: differentiating apache children from parents ?

2003-01-24 Thread Tim Kientzle
Josh Brooks wrote:


I want to kill apache children that exceed a certain memory size - but I
want to make sure only to kill children.



If you're having memory problems with Apache,
this is not the way to solve it.

Rather, limit the number of children
using 'MaxClients' or 'ServerLimit'.
That will restrict your total memory
usage.  (Note that restricting the number
of children can considerably improve overall
performance, especially if it prevents
the system from swapping.)

There's also a setting that limits the
total number of requests handled by a
particular child before that child
exits on its own.  That can be useful
for limiting the damage from memory
leaks, for example.

Using some of the newer MPMs, it's
also possible to designate certain children
to process memory-hungry requests and
manage overall memory usage that way.

Probably the most important point, though, is
to carefully evaluate your design choices.
mod_perl, for instance, is a notorious
memory pig.  (It's possible to limit
memory usage with mod_perl, but it requires
a great deal of care.)

Trying to kill children is just a bad
idea.  In particular, there's no way
to ensure that you kill a child between
requests, so you're gauranteed to lose
some requests if you go this way
(and quite possibly hang a few TCP
connections along the way).  Don't
do it.


Tim Kientzle



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Update and mailforward.

2003-01-24 Thread Tim Kientzle
Gannater Jnos wrote:


   I use sendmail. How can I forward my messages?


One option is to not forward your messages.  Rather,
install 'qpopper' or 'popper' from the ports and
let your users access their mailbox using any POP3-capable
email client (e.g., Outlook Express, Netscape Mail,


Eudora, etc.)

For Qpopper:
Is it enought to install qpopper and enable it in the
inetd.conf file?



Unless you have a pretty heavily-loaded server, this
should be enough



Mailforward:
And how can I forward the messages? Except /etc/aliases file...



/etc/aliases works.  You can also allow users to place
.forward files in their individual home directories.

Tim Kientzle





To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: back up Win2k workstations?

2003-01-23 Thread Tim Kientzle
On Thu, 23 Jan 2003, P. U. Kruppa wrote:

I am looking for a concept to back up some Win2k workstations on
a FreeBSD machine. Can this be done and how?



The approach I use here is to set up
Samba on FreeBSD and run Microsoft Backup
on Windows to backup to a file on the server.
Other Windows backup programs (e.g., Dantz
Retrospect) can also write to files on
a Samba server.

A couple of caveats:

* Use a recent version of Samba.  Prior to 2.0.8,
  Samba did not support files 4GB, and some
  later versions got very slow with large files.
  I'm playing with the beta of 3.0 which
  is very fast with large files.

* Microsoft Backup does no compression.
  You can either use very large hard disks on
  your server (which is what I'm doing now)
  or periodically run a script on the server
  to gzip the backup files.

* You should probably tune the disk for large
  files; read 'man newfs' for details.

Using this setup with 100Mbps Ethernet,
I can backup a Windows workstation with
60GB of data in about 3 1/2 hours over
the network, resulting in a single 60GB
file on the server.  Fortunately, not all
of my Windows machines are this large.  ;-)

Tim Kientzle



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message