Diego de Lima <[EMAIL PROTECTED]> wrote:
> The touch command sets timestamps terminated in 1, 3, 5, 7 or 9 incorrectly!
>
> # touch -t "200404231712.27" /mnt/autobk/portal/public.tgz
> # ls --time-style=full-iso -l /mnt/autobk/portal/public.tgz
> -rwxr-xr-x1 roo
The touch command sets timestamps terminated in 1, 3, 5, 7 or 9 incorrectly!
# touch -t "200404231712.27" /mnt/autobk/portal/public.tgz
# ls --time-style=full-iso -l /mnt/autobk/portal/public.tgz
-rwxr-xr-x1 root root 778240 2004-04-23 17:12:26.0 -
0400 /mnt/aut
I need all files in all sub-directories to have today's timestamp.
find . -type f -exec touch {} \;
Should do the trick.
___
Bug-fileutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-fileutils
Roy Finke wrote:
> Are there any plans to add the -R (recursive) option to the touch command?
> I need all files in all sub-directories to have today's timestamp.
I can't speak for the maintainers but I can't see any reason to add
'find' capability to the utilities.
Are there any plans to add the -R (recursive) option to the touch command?
I need all files in all sub-directories to have today's timestamp.
Roy Finke
CSP/FSP Test
(507) 253-5412
___
Bug-fileutils mailing list
[EMAIL PROTECTED]
http://mail.gn
dlaczego komenda
touch -acm -t 200205060800 too.sh nie powoduje zmiany czasu pliku?
według manuala powinna to zrobić...
Krzysztof Borecki (proszę odpowiedzieć na [EMAIL PROTECTED])
___
Bug-fileutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org
A Ottenheimer <[EMAIL PROTECTED]> wrote:
> From "man touch"
>
>>DESCRIPTION
>> or : ../src/touch [-acm] MMDDhhmm[YY] FILE...
>> (obsolescent)
>
>
> should be
>
>>DESCRIPTION
>>
From "man touch"
>DESCRIPTION
> or : ../src/touch [-acm] MMDDhhmm[YY] FILE...
> (obsolescent)
should be
>DESCRIPTION
> or : ../src/touch [-acm] [CC][YY]MMDDhhmm FILE...
TAKAI Kousuke <[EMAIL PROTECTED]> wrote:
> I have found a bug in `touch' command from fileutils 4.1.8
> that `touch -c' wrongly reports an error for non-existent file.
> (At least) SUSv2 seems to say `touch -c FILE' should not write any
> diagnostic
Hello,
I have found a bug in `touch' command from fileutils 4.1.8
that `touch -c' wrongly reports an error for non-existent file.
(At least) SUSv2 seems to say `touch -c FILE' should not write any
diagnostic messages when FILE does not exist.
% touch --version
touch (f
n the source or
should I just drop it only sourceforge? I guess I'd have to convince ppl
to accept the kernel patches as well, but that's probably do-able.
Jason
[EMAIL PROTECTED]
On Fri, 1 Mar 2002, Bob Proulx wrote:
>
> > This really isn't a bug, but it looks like
> This really isn't a bug, but it looks like there isn't a way to touch a
> symbolic link.
That is generally true of BSD like systems which implement symbolic
links. Actions upon symlinks pass through the symlink and act upon
the target of the symlink.
> If you do a
>
This really isn't a bug, but it looks like there isn't a way to touch a
symbolic link.
If you do a
ln -s foo.tgz foo
touch foo
it update the date on foo.tgz. Is there a work around?
Jason
[EMAIL PROTECTED]
___
Bug-fileutils mailing l
> I just noticed that in 4.0, I can no longer do a transerver touch on all
> child directories. I want to touch a directory and all the files in it and
> in its sub-directories.
>
> Should it be "touch -R *" ?
>
> Is the functionality removed or am i just not
Title: touch transverse all dirs
To whom it may concern:
I just noticed that in 4.0, I can no longer do a transerver touch on all child directories. I want to touch a directory and all the files in it and in its sub-directories.
Should it be "touch -R *" ?
Is the functionali
> The documentation states that the GNU FileUtils package handles long
> filenames. However, when I execute the following in a DOS box:
>
> cp a.txt "This is a long filename"
>
> The result is a file named "This is". I have also tried this with
> touch.exe and it too fails.
Thank you
The documentation states that the GNU FileUtils package handles long
filenames. However, when I execute the following in a DOS box:
cp a.txt "This is a long filename"
The result is a file named "This is". I have also tried this with
touch.exe and it too fails.
Can you help?
Thanks,
Bob Proulx wrote:
> The usage string
> is already so long that some users complain that it is way too long
> and scrolls off of the page.
> Bob
I always liked how pkunzip had three pages for usage,
and you hit '1', '2', or '3' to get the first,
second, or third page. If you hit any other ke
at there are too many really.
It can't be fully documented in the usage message. The usage string
is already so long that some users complain that it is way too long
and scrolls off of the page. And sure you can pipe it through a
pager but users that know that don't need the help message
Hi Folks,
When you do "touch.exe --help" , two of the lines output are these:
-d, --date=STRING parse STRING and use it instead of current time
-t STAMP use MMDDhhmm[[CC]YY][.ss] instead of current time
Question 1: Is "STRING" the same as "STAMP" above ?
Question 2: How
[more touch ctime doc gripes:]
$ touch --help
Update the access and modification times of each FILE to the current time.
***but it also modifies the 'ctime'... you didn't say that.
-a change only the access time
***but it also modifies the 'ctime
* doc/fileutils.texi: Warn that touch DATE FILE will be withdrawn.
===
RCS file: doc/fileutils.texi,v
retrieving revision 4.0.39.3
retrieving revision 4.0.39.5
diff -pu -r4.0.39.3 -r4.0.39.5
--- doc/fileutils.texi 2001/02/
Hello,
I got version 3.16 of your touch application running under win2k (an unfortunate thing
I know). Whenever I try to run
touch -a -m directory_name
I get a "Permission denied" message. The -a -m flags are the default.
It's possible that it is a windows problem (i
> I found a behaviour of touch that I don't understand (It seems to me a
> bug, at least a bug for the documentation) regarding the access,
> modifications and change times attributes of a file.
The touch info page could be more explicit about this. Right now it
only says
Hi,
I found a behaviour of touch that I don't understand (It seems to me a
bug, at least a bug for the documentation) regarding the access,
modifications and change times attributes of a file.
I'm using a Debian GNU/Linux 2.2r2, linux 2.2.18, glibc 2.1 and the
problem is that if
- the following command does not work properly
$ touch
touch: file arguments missing
Try `touch --help' for more information.
- the following command is OK
$ touch ./
- system info
$ uname -a
Linux jewel 2.2.15 #1 Sat Jun 3 02:39:56 PDT 2000 i686 unknown
Thanks,
W
Dear folks,
Today I found an interesting problem.
I have a Debian i386 Linux. I've issued the following commands:
$ touch --date=1970-01-01 lgconfig.h
$ make -n lgconfig.h
Make has complained:
make: *** Warning: File `lgconfig.h' has modification time in the future
(1970-01-01 00:00
hi
I am using Redhat 6.2 and I am having some strange problem
with the dates on the files created.
blr:mahesh(4)% date
Tue Sep 5 21:57:50 IST 2000
blr:mahesh(5)% touch hello
blr:mahesh(6)% l hello
-rw-r--r-- 1 mahesh mahesh 0 Sep 5 16:27 hello
blr:mahesh(7)% touch --v
touch
Hi,
I had sent this message once before but I was not receiving email
messages back due to network problems at my end. Could you please respond
to the following question again. Sorry!!
Hello,
Touch.exe does not seem to work for windows 2000. Any Ideas?
Steve Parrish
I am running RedHat 6.1 on a Pentium III box.
The "touch" command does not work right.
[root@webquote mbeffa]# date
Sat Feb 12 19:01:12 PST 2000
[root@webquote mbeffa]# touch temp
[root@webquote mbeffa]# ls -l temp
-rw-r--r-- 1 root root
0 Feb 13 03:01 temp
Paul Eggert <[EMAIL PROTECTED]> writes:
>Date: Thu, 28 Oct 1999 09:49:07 +0200
>From: "Gabor Z. Papp" <[EMAIL PROTECTED]>
>I would like, that touch modify also the date of the link
>itself, not just the linked file's date.
> It can&#x
31 matches
Mail list logo
