All the best
Keith Bainbridge
keithr...@gmail.com
keith.bainbridge.3...@gmail.com
+61 (0)447 667 468
UTC + 10:00
Forwarded Message
Subject: test sent date details
Date: Tue, 18 Jun 2024 17:56:41 +1000
From: Keith Bainbridge
To: keithr...@gmail.com
All the best
Keith
It has worked
All the best
Keith Bainbridge
keithr...@gmail.com
keith.bainbridge.3...@gmail.com
+61 (0)447 667 468
UTC + 10:00
On 18/6/24 17:56, Keith Bainbridge wrote:
All the best
Keith Bainbridge
keith.bainbridge.3...@gmail.com
+61 (0)447 667 468
UTC + 10:00
On Tue, Jun 11, 2024 at 11:22:17PM +0700, Max Nikulin wrote:
> On 11/06/2024 06:45, Greg Wooledge wrote:
> > Should you ever feel a need to read the longer version of the
> > documentation, it's in GNU info pages. So you would need to type
> > the command "i
On 11/06/2024 06:45, Greg Wooledge wrote:
Should you ever feel a need to read the longer version of the
documentation, it's in GNU info pages. So you would need to type
the command "info coreutils date" to get to it. And then you'd need
to figure out the user interface of the &quo
thanks roberto. that's exactly what i am looking for.
$ date +%a
On Tue, Jun 11, 2024 at 07:19:42AM +0800, Jeff Peng wrote:
> While I expect the output should be:
>
> $ date +%such_a_option
> Tuesday
>
> or
> $ date +%such_a_option
> Tue
>
> does date command has this option?
You can run the command "man date" to rea
All the format codes are documented in the man page for date.
in particular:
+%a gives a short form, such as Mon
+%A gives full name, e.g. Monday
+%^a and +%^A as above, but all capital letters.
- Original Message -
From: "Jeff Peng"
To: "debian-user"
> Wh
On Tue, Jun 11, 2024 at 07:19:42AM +0800, Jeff Peng wrote:
> Hello,
>
> I run the folllowing command,
>
> $ date +%w
> 2
>
>
> While I expect the output should be:
>
> $ date +%such_a_option
> Tuesday
>
> or
> $ date +%such_a_option
> Tue
>
Hello,
I run the folllowing command,
$ date +%w
2
While I expect the output should be:
$ date +%such_a_option
Tuesday
or
$ date +%such_a_option
Tue
does date command has this option?
Thanks.
On Tue, Apr 16, 2024 at 01:39:34PM -, Curt wrote:
[...]
> It would've been clearer to have advised using another mail application,
> period [...]
> But no harm, no foul, and all is well. The only real mystery is how
> Tomas resisted getting yet another lick in against Gmail and Google, et
>
On 2024-04-16, John Crawley wrote:
>
> If you do not trust Gmail as a web application, use a mail application
> that supports IMAP.
>
Gmail supports IMAP since more or less forever.
>>>
>>> AIUI the OP's problem was not when reading mail, but with mail
>>> submission of
On 2024-04-16, Max Nikulin wrote:
>
> If you do not trust Gmail as a web application, use a mail application
> that supports IMAP.
Gmail supports IMAP since more or less forever.
>>>
>>> AIUI the OP's problem was not when reading mail, but with mail
>>> submission of
On Mon 15 Apr 2024 at 18:52:33 (-), Curt wrote:
> On 2024-04-15, David Wright wrote:
> > On Sun 14 Apr 2024 at 14:24:29 (-), Curt wrote:
> >> On 2024-04-04, Max Nikulin wrote:
> >> >
> >> > If you do not trust Gmail as a web application, use a mail application
> >> > that supports IMAP.
On 16/04/2024 01:52, Curt wrote:
On 2024-04-15, David Wright wrote:
On Sun 14 Apr 2024 at 14:24:29 (-), Curt wrote:
On 2024-04-04, Max Nikulin wrote:
If you do not trust Gmail as a web application, use a mail application
that supports IMAP.
Gmail supports IMAP since more or less
On 16/04/2024 03:52, Curt wrote:
On 2024-04-15, David Wright wrote:
On Sun 14 Apr 2024 at 14:24:29 (-), Curt wrote:
On 2024-04-04, Max Nikulin wrote:
If you do not trust Gmail as a web application, use a mail application
that supports IMAP.
Gmail supports IMAP since more or less
On 2024-04-15, David Wright wrote:
> On Sun 14 Apr 2024 at 14:24:29 (-), Curt wrote:
>> On 2024-04-04, Max Nikulin wrote:
>> >
>> > If you do not trust Gmail as a web application, use a mail application
>> > that supports IMAP.
>> >
>>
>> Gmail supports IMAP since more or less forever.
>
>
On Sun 14 Apr 2024 at 14:24:29 (-), Curt wrote:
> On 2024-04-04, Max Nikulin wrote:
> >
> > If you do not trust Gmail as a web application, use a mail application
> > that supports IMAP.
> >
>
> Gmail supports IMAP since more or less forever.
AIUI the OP's problem was not when reading
On 2024-04-04, Max Nikulin wrote:
>
> If you do not trust Gmail as a web application, use a mail application
> that supports IMAP.
>
Gmail supports IMAP since more or less forever.
On 31/03/2024 22:35, David Wright wrote:
On Sun 31 Mar 2024 at 09:42:37 (+0300), Antti-Pekka Känsälä wrote:
But I'm worried my Gmail in Firefox is capable of stealing
files off my USB stick.
I've no answer for that, particularly in view of Max's reply
to my previous post.
I've always copied
I filed bug report 1068122. I feel fine, despite my concern over my data.
Heartfelt thanks for all the advice!
On Sun 31 Mar 2024 at 09:42:37 (+0300), Antti-Pekka Känsälä wrote:
> I'm mounting and unmounting through the stick icon's menu on Xfce desktop.
> Maybe a fancy file chooser dialogue stays around analyzing the directory,
> as you suspect? But I'm worried my Gmail in Firefox is capable of stealing
>
I'm mounting and unmounting through the stick icon's menu on Xfce desktop.
Maybe a fancy file chooser dialogue stays around analyzing the directory,
as you suspect? But I'm worried my Gmail in Firefox is capable of stealing
files off my USB stick.
On 31/03/2024 11:46, David Wright wrote:
Double-clicking on the directory
mounts it and displays the files in it. Opening a text file
displays it. At least for a small file, FF does not hold the
file open, so I can immediately unmount the stick.
Gmail may do something more fancy
-
On Sat 30 Mar 2024 at 21:06:27 (+0200), Antti-Pekka Känsälä wrote:
> I was able to replicate this, by trying to send gmail to myself in Firefox,
> attaching a binary on a mounted USB stick.
Did you mount the stick yourself as a user (ie there's an
fstab entry for it), or as root, or does an
On 3/30/24 08:17, Antti-Pekka Känsälä wrote:
What could be the deal, when Firefox tries to stop me from unmounting a
stick, after I've accessed files on it through Firefox? I worry about my
stick security. Thanks.
Linux knows what files are open on each file system. If you try to
unmount
I'd just like to add that I have seen the problem despite reinstalls with
Debian stable minor versions. Thanks!
On Sat, Mar 30, 2024 at 07:32:16PM +0200, Antti-Pekka Känsälä wrote:
> Yes, closing Firefox does allow the stick to unmount cleanly, but I still
> worry.
To get an idea of what's going on, you can use "lsof":
tomas@trotzki:~$ lsof /dev/sda1
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE
I can replicate this, by trying to send Gmail to myself in Firefox,
attaching a binary on a mounted USB stick. After the attachment supposedly
was uploaded, I tried to unmount the stick, but it blocked. "lsof | grep -i
KINGSTON" then shows a total of 129 lines from "x-www-browser". This lasted
for
I was able to replicate this, by trying to send gmail to myself in Firefox,
attaching a binary on a mounted USB stick. After the attachment supposedly
was uploaded, I tried to unmount the stick, but it blocks. "lsof | grep -i
KINGSTON" then shows a total of 129 lines from "x-www-browser". This
On Sat, 30 Mar 2024 17:17:52 +0200
Antti-Pekka Känsälä wrote:
> What could be the deal, when Firefox tries to stop me from unmounting
> a stick, after I've accessed files on it through Firefox? I worry
> about my stick security. Thanks.
It sounds like Firefox has a file open on the stick. To
On Sat, Mar 30, 2024 at 1:19 PM gene heskett wrote:
>
> On 3/30/24 11:36, Antti-Pekka Känsälä wrote:
> > What could be the deal, when Firefox tries to stop me from unmounting a
> > stick, after I've accessed files on it through Firefox? I worry about
> > my stick security. Thanks.
>
> Since
Yes, closing Firefox does allow the stick to unmount cleanly, but I still
worry.
On 3/30/24 11:36, Antti-Pekka Känsälä wrote:
What could be the deal, when Firefox tries to stop me from unmounting a
stick, after I've accessed files on it through Firefox? I worry about
my stick security. Thanks.
Since this is normally a root operation, I'm confused. Likely what it
means
What could be the deal, when Firefox tries to stop me from unmounting a
stick, after I've accessed files on it through Firefox? I worry about my
stick security. Thanks.
On 1/31/24 21:50, Max Nikulin wrote:
On 31/01/2024 20:24, didar wrote:
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
How do I setup /etc/chrony/chrony.conf so it slams the system clock
to the
current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate
On 31/01/2024 20:24, didar wrote:
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.
You can
Darac Marjal wrote:
>
>The script works like this: if the root device is specified on the
>kernel command line AND the word "fixrtc" is specified, then get the
>time that the root file system was last mounted. The script then uses
>"date" to set the cl
On Wed, 2024-01-31 at 12:56 -0500, gene heskett wrote:
> [...]
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: No suitable source for initstepslew
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec
On 1/31/24 13:19, Greg Wooledge wrote:
On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
# Stop bad estimates upsetting machine clock.
maxupdateskew 10.0
initstepslew 30 192.168.71.3
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time
uot;fixrtc" is specified, then get the
time that the root file system was last mounted. The script then uses
"date" to set the clock to that date stamp.
I assume that the idea is that, rather than having the clock start at
1970, it's better to start it at, say, yesterday. You've
On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
> # Stop bad estimates upsetting machine clock.
> maxupdateskew 10.0
> initstepslew 30 192.168.71.3
> # This directive enables kernel synchronisation (every 11 minutes) of the
> # real-time clock. Note that it can’t be used
c 30 03:15:44 bpi51e5p systemd[1]: Failed to start chrony, an NTP
client/server.
What output did you get?
The time as reported by "date":
gene@bpi51e5p:~$ date
Sat Dec 30 05:30:58 AM EST 2023
gene@bpi51e5p:~$
gene@coyote:~$ date
Wed Jan 31 12:38:16 EST 2024
gene@coyote:~$
What
On Wed, Jan 31, 2024 at 10:25:40AM -0500, gene heskett wrote:
> On 1/31/24 08:53, John Hasler wrote:
> > Gene writes:
> > > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > > the current time on the first cycle as its rebooting?
> >
> > initstepslew
> >
> > man
On 1/31/24 08:53, John Hasler wrote:
Gene writes:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
initstepslew
man chrony.conf
deprecated in favor of makestep, and did not work, John.
Thanks, John
Cheers, Gene
Max Nikulin wrote:
> I think, the problem is no RTC on some *pi board, certainly chrony out of
> box setup is not ready to such environment and its solution is not
> maxstep.
That's what makestep (initstepslew now being deprecated) is for.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 1/31/24 07:13, Max Nikulin wrote:
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
Well, I do have other probs with that machine, mostly with the
On Wed, Jan 31, 2024 at 07:53:01AM -0600, John Hasler wrote:
> Gene writes:
> > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > the current time on the first cycle as its rebooting?
>
> initstepslew
>
> man chrony.conf
Debian 12 has chrony 4.3, and in *that* version
Gene writes:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> the current time on the first cycle as its rebooting?
initstepslew
man chrony.conf
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
I think, the problem is no RTC on some *pi board, certainly chrony out
of box setup is not ready to
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.
Now it appears to conflict with the other client/servers
Thanks
Cheers, Gene Heskett, CET.
--
"There are
On Mon, Dec 18, 2023 at 08:17:21AM -0500, Greg Wooledge wrote:
> On Mon, Dec 18, 2023 at 02:07:14PM +0100, to...@tuxteam.de wrote:
> > I'm still amazed the OP hasn't understood that "date" can output
> > custom formats -- and that it's not always possible to parse back
On Sun, Oct 22, 2023 at 01:51:41PM +0200, Thomas Schmitt wrote:
[...]
> Originally it did only put out text in an xterm, but then i shamelessly
> exploited code from the exploitation chain xpppload <- xisdnload <- xload
> to give it a histogram in ain additional separate window.
Now this one
rently have a laptop, so the
> battery-status part wouldn't currently apply, but this sounds like
> something I might like to try when that changes; any chance of sharing
> the specific details?
Glad to oblige.
The date part is the smallest, dow
On 2023-10-22 at 07:24, to...@tuxteam.de wrote:
> I better not tell. My clock is a... shell script in a tiny Xterm
> which also shows my battery status.
Ooo, that sounds interesting. I don't currently have a laptop, so the
battery-status part wouldn't currently apply, but this sounds like
Hi,
to...@tuxteam.de wrote:
> My clock is a... shell script in a tiny Xterm which
> also shows my battery status.
My digital clock with date display is a C program which mainly watches the
network traffic. It even has an own date format ("A0" = 2000, now is "C3"
10 years ago.
I came back to it some time last century, after a very instructive
travel which encompassed Gnome (Metacity), Xfce, Awesome and other
exotica (olwm, GWM...)
> My clock is FvwmXclock. It's an analog-style 12 hours without date
> display.
I better not tell. My clock is a... shel
t century. It's configured by a ~/.fvwm2rc
which is at least 20 years old with minor changes to adapt to changed
paths and to avoid some unwanted behavior from 10 years ago.
My clock is FvwmXclock. It's an analog-style 12 hours without date
display.
Have a nice day :)
Thomas
On Sun, 22 Oct 2023 10:13:59 +0200
"Thomas Schmitt" wrote:
> Hi,
>
> Charlie wrote:
> > The date on that system is one day in advance and one hour late. Not
> > terrible,
> > However after a short period 100% of one of the CPU cores is used,
> > noisy
Hi,
Charlie wrote:
> The date on that system is one day in advance and one hour late. Not
> terrible,
> However after a short period 100% of one of the CPU cores is used,
> noisy running, and top -c shows this as the user:
> /usr/libexe/fvwm2/2.7.0/FvwmScript 17 4 none 0 8 Fvwm
Hello All,
Have a a Dell Vostro laptop: Bookworm up to date and
upgraded operating system to that state. Using FVWM window
manager.
The date on that system is one day in advance and one hour late. Not
terrible,
However after a short period 100% of one
Le lundi 1 mai 2023 à 15:44, ajh-valmer a écrit :
> Si c'est un bug, il sera corrigé à un moment.
> C'est pourquoi j'attends toujours quelques semaines
> avant de migrer, avec cette précaution de l'installer sur
> une autre partition pour le tester.
Je ne crois pas que c'est un bug dans la
Merci pour l'info!
J'en prend bonne note pour le prochain essai.
Roger
Le 2023-05-01 à 11 h 58, steve a écrit :
Le 01-05-2023, à 11:26:33 -0400, Ro Bou a écrit :
Pour ce problème, il faut cette entrée
GRUB_DISABLE_OS_PROBER=false
dans /etc/default/grub
puis lancer, en root
update-grub2
Le 05/05/2023 à 14:00, Erwann Le Bras a écrit :
[...]
* si c'est le système qui démarre X et ensuite tu t'identifies sur la
mire X11, c'est forcément root le propriétaire.
[...]
En fait ton exemple illustre le fait que lightdm, bien que pas si vieux,
a une gestion à l'ancienne et ne
bonjour
Pour moi, ça dépend :
* si tu t'identifie sur la console texte pour lancer l'interface
graphique là oui, elle est lancée avec ton ID
* si c'est le système qui démarre X et ensuite tu t'identifies sur la
mire X11, c'est forcément root le propriétaire.
Chez moi j'ai :
root
Le 04/05/2023 à 09:04, Michel Verdier a écrit :
Ça dépend comment tu lance X. Xorg est toujours lancé en root, c'est
normal pour éviter les failles de sécurité. J'ai eu ce problème sur
Bullseye. Je lance Xorg via startx. J'ai manipé pour que
/tmp/serverauth... soit créé avec l'uid de mon user.
Le 1 mai 2023 benoit a écrit :
> J'ai essayé 2x de passer en Bookworm, mais après la mise à jour, X ne veut
> plus se lancer, car il n'a pas le droit d'écrire dans /tmp:LOCKMACHIN BIDULE
> (G pas noté le message d'erreur)
>
> Seul root peut lancer x
Ça dépend comment tu lance X. Xorg est
Le Mon, 01 May 2023 12:34:35 +,
benoit a écrit :
> J'ai essayé 2x de passer en Bookworm, mais après la mise à jour, X ne
> veut plus se lancer, car il n'a pas le droit d'écrire dans
> /tmp:LOCKMACHIN BIDULE (G pas noté le message d'erreur)
>
> Seul root peut lancer x
>
> Du coup j'ai
Le lundi 01 mai 2023 à 12:34 +, benoit a écrit :
>
> J'ai essayé 2x de passer en Bookworm, mais après la mise à jour, X ne
> veut plus se lancer, car il n'a pas le droit d'écrire dans
> /tmp:LOCKMACHIN BIDULE (G pas noté le message d'erreur)
>
> Seul root peut lancer x
>
> Du coup j'ai
Le 01-05-2023, à 11:26:33 -0400, Ro Bou a écrit :
Bonjour!
J'ai aussi fait l'essai de bookworm. Résultat pas concluant dans mon cas.
Je suis en multi boot avec le windows 10 pré-installé, une
debian-facile et un disque usb externe de 4 tb pour des sauvegardes.
Au redémarrage de
vendredi 28 avril 2023 à 10:18, didier gaumet a
écrit :
date de sortie prévisionnelle de Debian 12 Bookworm: le 10 juin 2023.
le message annoçant la nouvelle sur la liste Devel:
https://lists.debian.org/debian-devel-announce/2023/04/msg7.html
On Monday 01 May 2023 14:34:35 benoit wrote:
> J'ai essayé 2x de passer en Bookworm, mais après la mise à jour,
> X ne veut plus se lancer, car il n'a pas le droit d'écrire
> dans /tmp:LOCKMACHIN BIDULE (G pas noté le message d'erreur)
> Seul root peut lancer x
> Du coup j'ai restauré mon
Bookworm
--
Benoît
Envoyé avec la messagerie sécurisée Proton Mail.
--- Original Message ---
Le vendredi 28 avril 2023 à 10:18, didier gaumet a
écrit :
> date de sortie prévisionnelle de Debian 12 Bookworm: le 10 juin 2023.
>
> le message annoçant la nouvelle sur la liste Devel
date de sortie prévisionnelle de Debian 12 Bookworm: le 10 juin 2023.
le message annoçant la nouvelle sur la liste Devel:
https://lists.debian.org/debian-devel-announce/2023/04/msg7.html
On 25/03/2023 10:39, Albretch Mueller wrote:
You can't physically alter a DVD[+|-]R once it is burned ...
Do you customize images to change preferences, e.g. to make OS aware
that hardware clock is set to local time? If you do not than OS almost
certainly assumes that system time is in
On 25/03/2023 10:39, Albretch Mueller wrote:
On 3/25/23, Max Nikulin wrote:
- Both Debian and Windows installed on the hard drive ...
Thank you for the steps and the logical elucidations that may
certainly help someone else, but I can't do that "because" all
electronic devices which I use
David Wright composed on 2023-03-24 23:20 (UTC-0500):
> BTW I've only really trusted reading or setting the RTC by means of
> the CMOS screens, and treat it as a one-time only process (upon
> acquisition), assuming the coin-cell battery never needs replacing.
Lucky you. I can only dream of going
On Fri 24 Mar 2023 at 19:10:49 (-0400), Stefan Monnier wrote:
> > That works great for the Live OS, but not for the fixed-disk OS. If
> > the Live OS sets the HW clock to local upon shutdown, but the fixed-disk
> > OS expects the HW clock to be UTC, then the fixed-disk OS is wrong
> > every time
, it is 5 hours ahead.
> I used logs which names a time a la:
>
> _DT=$(date +%Y%m%d%H%M%S)
> _BN=$(basename "${_SDIR}")
> _LOG_FL="${_BN}_${_DT}.log"
> ...
> If anything, timing is one of the aspects of reality which should be
> coordinated.
Hence t
On 3/25/23, Max Nikulin wrote:
> - Both Debian and Windows installed on the hard drive ...
Thank you for the steps and the logical elucidations that may
certainly help someone else, but I can't do that "because" all
electronic devices which I use are being kept.
You can't physically alter a
On 25/03/2023 07:07, Albretch Mueller wrote:
I am using right now a DELL laptop which had Windows 11 installed but
I expect that the following should work smoothly enough:
- Hardware clock is in UTC
- Both Debian and Windows installed on the hard drive are configured to
your local time zone
I am using right now a DELL laptop which had Windows 11 installed but
started to give me sh!t which I totally ignored and started to use my
good old friend Debian in order to "keep moving".
By the way, after a while as if for a magical reason the hw time
changed and now it is showing to me the
> That works great for the Live OS, but not for the fixed-disk OS. If
> the Live OS sets the HW clock to local upon shutdown, but the fixed-disk
> OS expects the HW clock to be UTC, then the fixed-disk OS is wrong
> every time it boots after the Live OS.
AFAIK the Linux kernel is pretty careful
On Fri, Mar 24, 2023 at 05:51:30PM -0400, Stefan Monnier wrote:
> > If your policy choice ends up being "set HW clock to local", then you
> > also have to make sure the correct time zone is set on each operating
> > system, each time it boots. I have no idea how one does that on Debian
> > Live,
> If your policy choice ends up being "set HW clock to local", then you
> also have to make sure the correct time zone is set on each operating
> system, each time it boots. I have no idea how one does that on Debian
> Live, since I've never used Debian Live. So, I can hope for your sake
> that
On Fri, Mar 24, 2023 at 05:13:31PM +, Albretch Mueller wrote:
> I should have pointed out that I always go into exposed mode (use the
> Internet) with a live DVD. My laptop was always 6 hours ahead and now
> that they changed to summer time, it is 5 hours ahead.
So, you have at least two
I should have pointed out that I always go into exposed mode (use the
Internet) with a live DVD. My laptop was always 6 hours ahead and now
that they changed to summer time, it is 5 hours ahead.
I used logs which names a time a la:
_DT=$(date +%Y%m%d%H%M%S)
_BN=$(basename "${_S
Hello,
On Thu, Mar 23, 2023 at 09:41:40PM +, Albretch Mueller wrote:
> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
> the time 5 hours. hwclock tells me it worked fine but the terminal
> windows opened before and after running hwclock still give me the
> "old" time
On Thu 23 Mar 2023 at 21:41:40 (+), Albretch Mueller wrote:
> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
> the time 5 hours. hwclock tells me it worked fine but the terminal
> windows opened before and after running hwclock still give me the
> "old" time setting?
On 3/23/23, Cindy Sue Causey wrote:
> On 3/23/23, Albretch Mueller wrote:
>> I am using this (yes, visually cr@ppy ;-)) code snippet to set back
>> the time 5 hours. hwclock tells me it worked fine but the terminal
>> windows opened before and after running hwclock still give me the
>> "old"
etting?
>
> _HRS_PM=-5
>
> ###
> #
> https://stackoverflow.com/questions/1092631/get-current-time-in-seconds-since-the-epoch-on-linux-bash
> _DTS=$(date +%s)
> echo "// __ \$_DTS: |${_DTS}|";
> _DTF=$(date --date @${_DTS})
> echo "// __ \$_DTF: |${_DTF}|";
&
want to change the system's time, then change the system's time,
not the hardware clock.
To change the system's time, use `date` (see `man date` for the format
of its arguments).
But changing the system's time is very rarely a good idea.
If you want to change the time based on timezone issues, t
et-current-time-in-seconds-since-the-epoch-on-linux-bash
_DTS=$(date +%s)
echo "// __ \$_DTS: |${_DTS}|";
_DTF=$(date --date @${_DTS})
echo "// __ \$_DTF: |${_DTF}|";
_NEW_DTS=$((_DTS+3600*_HRS_PM))
echo "// __ \$_NEW_DTS: |${_NEW_DTS}|";
# Convert the number
Le 2022-11-07 17:22, Francois Mescam a écrit :
Il y a une option de rsyslog qui joue la-dessus :
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
Il me semble que récemment sa
(malgré les filtres "standards").
En fait, il semblerait que ceci soit lié au format de la date dans mes
logs.
Ainsi, ces derniers sont écrits sous la forme suivante :
"2022-11-07T14:02:20.160314+01:00 mamachine event[4999]:"
Or, les expressions régulières visant à filtrer
ton problème.
Francois Mescam
Le 07/11/2022 à 15:32, David BERCOT a écrit :
Bonjour,
J'utilise Logcheck sur plusieurs systèmes et je me suis rendu compte que
tous les logs remontaient (malgré les filtres "standards").
En fait, il semblerait que ceci soit lié au format de la date dans
Bonjour,
J'utilise Logcheck sur plusieurs systèmes et je me suis rendu compte que
tous les logs remontaient (malgré les filtres "standards").
En fait, il semblerait que ceci soit lié au format de la date dans mes logs.
Ainsi, ces derniers sont écrits sous la forme suivante :
"2
On Sat, Nov 05, 2022 at 05:12:40PM +0100, local10 wrote:
> Nov 5, 2022, 15:30 by g...@wooledge.org:
>
> >> > > local10 wrote:
> >> > >
> >> > > > Any ideas as to get the old syslog date format back?
> >>
> >
> > What
Nov 5, 2022, 14:53 by j...@k4vqc.com:
> On Sat, 2022-11-05 at 11:34 +0100, local10 wrote:
>
>> Nov 5, 2022, 09:55 by scdbac...@gmx.net:
>>
>> > Hi,
>> >
>> > local10 wrote:
>> >
>> > > Any ideas as to get the old syslo
1 - 100 of 1814 matches
Mail list logo
