deletion log

[r][m]

In 236 Log:
Delete is a great addition to the log, but.....
The delete record is displayed in the log window and log file as:
4/28/09 11:16:45 AM user@192.168.1.100:1132{M1 LAN} Deleted files in /Server/Shared_Files/
> Print Screen.txt
> Start-Up.wav
> xld.LastValue.zip
Should be:
4/28/09 11:16:45 AM user@192.168.1.100:1132{M1 LAN} Deleted files in /Server/Shared_Files/ > Print Screen.txt > Start-Up.wav > xld.LastValue.zip
All on one line. Really screws up the log file.

[SilentPliz]

This is a problem of presentation or standard format of log?
For me, to choose, I prefer the multilines solution.

I imagine 60 files on 1 line... 

[r][m]

This is a problem of presentation or standard format of log?
For me, to choose, I prefer the multilines solution.

I imagine 60 files on 1 line... 

I see your point, but it doesn't work with any sort of log analysis as a list.
Recording log data is useless unless you have a way of harvesting the data.
Imagine searching through a 2,000 lines of log to find an entry.
When its all on one line it should just wrap your 60 items, but they will be placed
in the proper section. As a list they fall in the same section as date - big mess.

It could be very useful if archive logged the same way 

[Mars]

This is a problem of presentation or standard format of log?
For me, to choose, I prefer the multilines solution.

I imagine 60 files on 1 line... 

I see your point, but it doesn't work with any sort of log analysis as a list.
Recording log data is useless unless you have a way of harvesting the data.
Imagine searching through a 2,000 lines of log to find an entry.
When its all on one line it should just wrap your 60 items, but they will be placed
in the proper section. As a list they fall in the same section as date - big mess.

It could be very useful if archive logged the same way 

if you use an external software to analyze the log, here is a solution to mark the end of deleted informations

    if logDeletionsChk.checked and assigned(done) then
      add2log('Deleted files in '+url+CRLF+join(CRLF, done)+CRLF+'End of Deleted files in '+url+CRLF), data);
    if logDeletionsChk.checked and assigned(errors) then
      add2log('Failed deletion in '+url+CRLF+join(CRLF, errors)+CRLF+'End of Failed deletion in '+url+CRLF), data);
    end; // deletion

[rejetto]

i splitted this topic so we can discuss it without digging old betas topics.
i will now publish #237 and we'll continue after.

[r][m]

Presently have Delete unchecked in 237
It produces log entrys out of sequence as in SS
attached.

[rejetto]

you had it unchecked, the restarted hfs, and because of a bug, it was enabled again.
it will be fixed in next build.

[rejetto]

I see your point, but it doesn't work with any sort of log analysis as a list.
Recording log data is useless unless you have a way of harvesting the data.
Imagine searching through a 2,000 lines of log to find an entry.
When its all on one line it should just wrap your 60 items, but they will be placed
in the proper section. As a list they fall in the same section as date - big mess.

i can suggest an option to convert all "blue lines" to a single tabbed line in the standard log file.

It could be very useful if archive logged the same way 

would it?

[r][m]

you had it unchecked, the restarted hfs, and because of a bug, it was enabled again.
it will be fixed in next build.

I don't understand what you mean?

i can suggest an option to convert all "blue lines" to a single tabbed line in the standard log file.

I think it would be best to keep the log output in a consistent format.

would it?

The log lists files downloaded one at a time, now delete produces a log list, why not a
list of whats in a down loaded archive? (if its possible?)

[rejetto]

I don't understand what you mean?

there is a bug, but it's not the one i initially deduced by your report.

I think it would be best to keep the log output in a consistent format.

the output you require doesn't seem to be convenient for human reading.
hfs is designed also for transient usage, where only human reading takes place.

The log lists files downloaded one at a time, now delete produces a log list, why not a
list of whats in a down loaded archive? (if its possible?)

reasonable.

[bacter]

perhaps not to complicated:

hfs could use a redefinable macro for delete- and download-log in the format rejetto and most users prefere, and those who want could set the macro with a {.set|deletelog|%timestamp% %ip% %user% deleted $1 $2 $3 $4.. .} or something similar that would be used instead of the default format ?

[r][m]

i can suggest an option to convert all "blue lines" to a single tabbed line in the standard log file.

How could I do this?

[rejetto]

i can suggest an option to convert all "blue lines" to a single tabbed line in the standard log file.

How could I do this?

you can't. i suggested as solution. i would make such option, if it's a good solution.

[r][m]

you can't. i suggested as solution. i would make such option, if it's a good solution.

In events, maybe?
Sounds good to me. 

[rejetto]

no, it would be an option inside the log menu.
like "Tabbed instead of multi-line for the log file".