mirror of
https://github.com/Corsinvest/cv4pve-autosnap.git
synced 2026-04-25 17:05:48 +03:00
[GH-ISSUE #43] Change Timestamp String to be Compatible with Unix date Timestamp #42
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cv4pve-autosnap#42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NicholasRush on GitHub (Dec 13, 2020).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/43
I have setup an SMB fileserver in an LXC container. My problem is that i cannot use these timestamps in the samba vfs shadow_copy2 module, because that need a 4-digit year string with some "_" separators to be compatible.
An example of this is the following: autohourly_20201213_193822
|
| -> name,"" separator, 4-digit year, 2-digit month, 2-digit day, "" separator, 2-digit hour,
2-digit minute, 2-digit second.
@franklupo commented on GitHub (Dec 14, 2020):
Hi
could i create a parameter that accepts a custom format?
TIMESTAMP_FORMAT = "yyMMddHHmmss" default
TIMESTAMP_FORMAT = "_yyyyMMdd_HHmmss" in your case
best regards
@franklupo commented on GitHub (Dec 15, 2020):
Sorry
"could i create a parameter that accepts a custom format?"
@NicholasRush commented on GitHub (Dec 15, 2020):
Yes, a parameter that accept a custom format is better than a predefined one. Thank you very much.
@franklupo commented on GitHub (Dec 16, 2020):
Hi,
the new version is available with the --timestamp-format parameter
Best reagrds
@NicholasRush commented on GitHub (Dec 16, 2020):
Thank you, that was very fast. I will test this version now.
Best Regards
@franklupo commented on GitHub (Jan 5, 2021):
News?
@NicholasRush commented on GitHub (Jan 5, 2021):
It´s running very fine. I think theres a problem in proxmox itself. Sometimes a vm or an lxc container is offline after some snapshots are removed.