On 4/14/25 11:51, Pocket wrote:
On 4/14/25 11:04 AM, gene heskett wrote:
On 4/14/25 09:18, Pocket wrote:
On 4/14/25 8:35 AM, gene heskett wrote:
But while there is a call to docker on an ipv4 address starting
with 172 in
the trace output, I don't recall ever setting up docker on this
system.
On 4/14/25 09:18, Pocket wrote:
On 4/14/25 8:35 AM, gene heskett wrote:
But while there is a call to docker on an ipv4 address starting
with 172 in
the trace output, I don't recall ever setting up docker on this
system. So
who can help me check to see if its missing and this freeze is
the ti
On 4/14/25 01:55, Andrew M.A. Cater wrote:
On Sun, Apr 13, 2025 at 05:32:29PM -0400, gene heskett wrote:
On 4/13/25 14:07, Andrew M.A. Cater wrote:
On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:
Hi Gene,
I'm probably going to regret this - let's see if I can help you
fault-find
On Sun, Apr 13, 2025 at 05:32:29PM -0400, gene heskett wrote:
> On 4/13/25 14:07, Andrew M.A. Cater wrote:
> > On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:
> >
> > Hi Gene,
> >
> > I'm probably going to regret this - let's see if I can help you
> > fault-find :)
> >
> > Question
On 4/13/25 14:07, Andrew M.A. Cater wrote:
On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:
Hi Gene,
I'm probably going to regret this - let's see if I can help you
fault-find :)
Questions:
1. Which version of Debian is this?
Give us the output of /etc/os-release and of uname -a
On Sun, Apr 13, 2025 at 12:50:14PM -0400, gene heskett wrote:
Hi Gene,
I'm probably going to regret this - let's see if I can help you
fault-find :)
Questions:
1. Which version of Debian is this?
Give us the output of /etc/os-release and of uname -a on this machine,
please.
2. Do you actually
Using strace, the freeze corresponds to a poll command for fd33, which
appears to be a docker function. In this case the test file is an
AppImage, orcaslicer-2.3.0, but any AppImage will work for this. I have
quite a few, as its the only way to get the latest and greatest given
debians penchant
El jue., 17 ago. 2023 23:34, Javier Barroso
escribió:
>
>
> El jue., 17 ago. 2023 22:49, Ash Joubert escribió:
>
>> Happy Birthday Debian!
>>
>> My open source journey started with Slackware in 1995, then Red Hat from
>> 1996, and then Fedora. I first encountered Debian at a new job in 2007,
>>
El jue., 17 ago. 2023 22:49, Ash Joubert escribió:
> Happy Birthday Debian!
>
> My open source journey started with Slackware in 1995, then Red Hat from
> 1996, and then Fedora. I first encountered Debian at a new job in 2007,
> and switched my desktop to Debian/sid in 2012. I installed my curren
Happy Birthday Debian!
My open source journey started with Slackware in 1995, then Red Hat from
1996, and then Fedora. I first encountered Debian at a new job in 2007,
and switched my desktop to Debian/sid in 2012. I installed my current
Debian/sid desktop in April 2017 and it has been rolling
On Wed, 16 Aug 2023, Luna Jernberg wrote:
Happy Birthday 30 years of the Debian Linux Project
I consider Debian to be a major intellectual achievement, Collective, but still
a major achievement.
My first Linux ran on an IBM PS/2 L40 SX laptop with a monochrome display. I
had to
Luna Jernberg wrote:
> Happy Birthday 30 years of the Debian Linux Project
...
and congrats on surviving and persisting through all
that can happen. :)
songbird
On Thu, Aug 17, 2023 at 07:32:10PM +0200, Martin Petersen wrote:
> happy birthday Debian !
>
> and thanks to all you contributors and nice people in this community.
>
> i chose debian as a noob after my first experiments w. suse around '98/'99
> and never looked back. best os on the planet and s
ation. the whole is indeed greater
than the sum of it parts.
rip ian <3
On 2023-08-16 13:31, Luna Jernberg wrote:
Happy Birthday 30 years of the Debian Linux Project
https://www.gamingonlinux.com/2023/08/happy-debian-day-going-30-years-strong/
https://wiki.debian.org/DebianD
Happy anniversary indeed.
30 years for anything is a significant milestone particularly an all, or
nearly all, volunteer project that doesn't have a single person who is
the benevolent dictator for life but instead has had a number of elected
project leaders over that time. This is very mu
Happy Birthday Debian
By the way, thank you all who put any amount of work on Debian.
Thank you Ian.
On August 16, 2023 11:31:35 AM UTC, Luna Jernberg wrote:
>Happy Birthday 30 years of the Debian Linux Project
>
>https://www.gamingonlinux.com/2023/08/happy-debian-day-going
Happy birthday to all, oh, you lovely people/community, oh, this
lovely OS! <3 ^_^ ^o^
#LongLiveFreeSoftware #CopyLeft
On Wed, Aug 16, 2023, 9:38 AM Marco wrote:
> Am 16.08.2023 um 15:07:35 Uhr schrieb Thomas Schmitt:
>
> > >
> https://wiki.debian.org/DebianHistory?action=AttachFile&do=get&target=Debian-announcement-1993-pic-by-Ian_Murdock.png
>
> Rather interesting that people printed out usenet posts back in th
Am 16.08.2023 um 15:07:35 Uhr schrieb Thomas Schmitt:
> > https://wiki.debian.org/DebianHistory?action=AttachFile&do=get&target=Debian-announcement-1993-pic-by-Ian_Murdock.png
Rather interesting that people printed out usenet posts back in these
days.
Hi,
Luna Jernberg wrote:
> Happy Birthday 30 years of the Debian Linux Project
\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/\o/
> https://wiki.debian.org/DebianHistory?action=AttachFile&do=get&target=Debian-announcement-1993-pic-by-Ian_Murdock.png
Also avai
Happy Birthday 30 years of the Debian Linux Project
https://www.gamingonlinux.com/2023/08/happy-debian-day-going-30-years-strong/
https://wiki.debian.org/DebianDay/2023
https://wiki.debian.org/DebianHistory?action=AttachFile&do=get&target=Debian-announcement-1993-pic-by-Ian_Murdock.png
On Mon, May 02, 2022 at 10:04:00AM -0500, David Wright wrote:
> I'm not very familiar with files' birth as it's a relatively new
> addition to filesystems, particularly how to display it even when
> present. So I looked it up, and the ext4 wiki says it's the time
> at which the inode is created. I
On Mon 02 May 2022 at 01:30:08 (+0200), Vincent Lefevre wrote:
> On 2022-04-30 15:19:21 +0200, Thomas Schmitt wrote:
> > An explanation of the observed problem would need:
> > - a mechanism which delayed the content production of the inode while it
> > was already in u
On Mon, May 02, 2022 at 01:10:04AM +0200, Vincent Lefevre wrote:
> On 2022-04-30 14:06:53 +0200, to...@tuxteam.de wrote:
[...]
> > It sure looks like a bug. But it would be a bug at a spot where one would
> > expect that it should have bitten oodles of other people by now, so t
On Mon, May 02, 2022 at 01:30:08AM +0200, Vincent Lefevre wrote:
> I'm wondering whether the data are transferred from the VFS to ext4
> necessarily within the same openat system call or could just be kept
> in the VFS as long as they are not needed elsewhere, i.e. the VFS
> beha
On 2022-04-30 15:19:21 +0200, Thomas Schmitt wrote:
> An explanation of the observed problem would need:
> - a mechanism which delayed the content production of the inode while it
> was already in use for open and write,
> - or a mechanism which caused ext4 to hide the inode to oth
On 2022-04-30 14:06:53 +0200, to...@tuxteam.de wrote:
> On Sat, Apr 30, 2022 at 10:33:34AM +0200, Thomas Schmitt wrote:
> > I understand that Vincent Lefevre suspects these discrepancies to be a bug
> > in the ext4 driver. I rather suspect that ext4 is ok and that we observe
>
an a lot of weird things.
But the subsequent praragraphs clearly concern the RAM-to-disk migration of
memory pages which are associated to the filesystem's disk storage.
> And the delayed allocation will actually commit the data to disk only after
> 30-150 seconds (it is not very clear on t
On Sat, Apr 30, 2022 at 12:31:07PM -, Curt wrote:
> On 2022-04-30, Thomas Schmitt wrote:
> >
> > Indeed. With normal filesystem operations there should be no need to call
> > something like sync(2) in order to get a consistent representation of the
> > current file
On 2022-04-30, Thomas Schmitt wrote:
>
> Indeed. With normal filesystem operations there should be no need to call
> something like sync(2) in order to get a consistent representation of the
> current filesystem state.
>
What does the following mean, then, in that light:
Bec
On Sat, Apr 30, 2022 at 10:33:34AM +0200, Thomas Schmitt wrote:
> Hi,
>
> sp...@caiway.net wrote:
> > how does one force to refresh this memory with a command?
>
> to...@tuxteam.de wrote:
> > What do you mean by "refresh"? What's in the cache is alwa
o need to call
something like sync(2) in order to get a consistent representation of the
current filesystem state.
That's actually the riddle of this thread:
The filesystem behavior outside the script and the time stamps look like
the file was created 30 seconds after the script began to op
On Fri, Apr 29, 2022 at 09:41:23PM +0200, sp...@caiway.net wrote:
> On Fri, 29 Apr 2022 13:45:15 -0400
>
> > linux caches file system pages in memory
>
> how does one force to refresh this memory with a command?
What do you mean by "refresh"? What's in the cache is always
the "freshest" version:
On Fri, 29 Apr 2022 13:45:15 -0400
> linux caches file system pages in memory
how does one force to refresh this memory with a command?
Thanks!
a hole.
sync isn't about this. linux caches file system pages in memory - both
content and metadata. sync is about forcing the changed pages back to
disk, for example before shutting down. It's done automatically - maybe
every 30 seconds (I'm not sure about linux on this). But
On 4/27/22 11:05 PM, Greg Wooledge wrote:
On Wed, Apr 27, 2022 at 10:45:09PM -0400, Stefan Monnier wrote:
Another option might be that your system's time was "reset".
This shouldn't happen, but it can happen if your NTP was down, the
machine got out-of-sync over time and you restart the NTP se
Hi,
On 2022-04-28 11:26:36 +0200, Thomas Schmitt wrote:
> Vincent Lefevre wrote:
> > and one with
> > openat(AT_FDCWD, "….out", O_WRONLY|O_CREAT|O_APPEND, 0666
> > <... openat resumed>) = 3
> > about 30 seconds later.
>
> Oh. So the script
written back to the
actual FS.
When I did
tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
this had the effect to look at the entries in the current directory.
For some reason (a bug occurring under some particular conditions?),
the dirty state due to the data written above to the VFS was ignor
Hi,
Vincent Lefevre wrote:
> and one with
> openat(AT_FDCWD, "….out", O_WRONLY|O_CREAT|O_APPEND, 0666
> <... openat resumed>) = 3
> about 30 seconds later.
Oh. So the script was still running when the file finally appeared to lt,
tail, and ll ?
Is the text s
ventin.lip.ens-lyon.fr.out doesn't appear in the
first "lt|head" output).
3. To go back after 14:43:42.
And this would not explain the
cventin:~/software/mpfr> tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
zsh: no match
zsh: no match
cventin:~/software/mpfr[1]> tail -n 3
On Wed, Apr 27, 2022 at 10:45:09PM -0400, Stefan Monnier wrote:
> Another option might be that your system's time was "reset".
> This shouldn't happen, but it can happen if your NTP was down, the
> machine got out-of-sync over time and you restart the NTP server at
> which point it may(!) decide to
On 2022-04-27 09:26:50 -0400, Greg Wooledge wrote:
> Are you able to reproduce the issue at all, even like 1% of the time?
In the past 11 years, I may have ran the script (and looked at the
output just after that) hundreds or thousands of times; the commands
to look at the output have been in my s
On Wed, Apr 27, 2022 at 03:11:22PM +0200, Vincent Lefevre wrote:
> So, perhaps there were no issues with openat, but when reading
> the directory, the file could not be found because some internal
> structures might have been incomplete.
If so, this is a bug at the kernel level, perhaps in the VFS
On 2022-04-27 11:39:17 +0200, Thomas Schmitt wrote:
> If it has indeed to do with the CPU cache then a particular cache would have
> delayed its writing to RAM for 30 seconds but would have served its own CPU
> with the full results of file system driver and virtual memory activities
>
Hi,
Vincent Lefevre wrote:
> the issue [...] is probably unlikely to occur again.
In this case we will hardly be able to find an explanation.
> However, there's also the fact that the birth time was 30 seconds
> ahead of the actual file creation, while there was no lock
Hi,
On 2022-04-27 09:07:37 +0200, Thomas Schmitt wrote:
> i wrote:
> > > So if it got created by the script, maybe it was deleted or renamed
> > > shortly afterwards and created again 30 seconds later ?
>
> Vincent Lefevre wrote:
> > The script doesn&#x
Hi,
i wrote:
> > So if it got created by the script, maybe it was deleted or renamed
> > shortly afterwards and created again 30 seconds later ?
Vincent Lefevre wrote:
> The script doesn't do that. The file is created with
> echo "* $fqdn ($(${1:-.}/config.gues
On 2022-04-26 14:18:58 -0400, Stefan Monnier wrote:
> > On an ext4 filesystem, I got a file born 30 seconds after its
> > actual creation. Is this a bug?
>
> I doubt it.
> Note that a file's atime/mtime/ctime is a property of the file itself,
> whereas "appe
On 2022-04-26 12:47:53 -0500, Nicholas Geovanis wrote:
> On Tue, Apr 26, 2022 at 12:37 PM Nicholas Geovanis
> wrote:
>
> > On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre
> > wrote:
> >
> >> On an ext4 filesystem, I got a file born 30 seconds after its
On 2022-04-26 19:01:26 +0200, Thomas Schmitt wrote:
> It looks as if the file indeed does not exist when you inquire it.
> So if it got created by the script, maybe it was deleted or renamed
> shortly afterwards and created again 30 seconds later ?
The script doesn't do that. The f
On Tue, Apr 26, 2022 at 12:37 PM Nicholas Geovanis
wrote:
> On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre
> wrote:
>
>> On an ext4 filesystem, I got a file born 30 seconds after its
>> actual creation. Is this a bug?
>>
>
> Only experimentation can really bac
On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre wrote:
> On an ext4 filesystem, I got a file born 30 seconds after its
> actual creation. Is this a bug?
>
Only experimentation can really back me up on this, but consider the
following:
Every time you use the "|" operator or t
enamed
shortly afterwards and created again 30 seconds later ?
Consider to inquire the file in the script for birth time and inode number
immediately after it was created. Compare these properties with the
properties of the file which you see 30 seconds later.
Have a nice day :)
Thomas
On an ext4 filesystem, I got a file born 30 seconds after its
actual creation. Is this a bug?
I know that such issues can be observed with NFS, but here this
is just a local ext4 filesystem.
Here are the details.
I started a shell script:
cventin:~> ps -p 667828 -o lstart,
@ 0x55c8497eb4c0] Value 160.00 for parameter
'phase_shift' out of range [0 - 30]
That certainly haven't anything to do with the broken dark-theme
(partial dark theme, with grey text on white background in the options
names in prefs), and probably nothing to do with background noise. Bu
On Thu 23 Jul 2020 at 16:52:48 (+1000), Keith bainbridge wrote:
> On 23/7/20 4:23 pm, Andrei POPESCU wrote:
> > On Ma, 21 iul 20, 17:39:09, Keith bainbridge wrote:
>
> I hadn't noticed this before, but where does 'the system' get my name
> from. Everything I can see here says Keith Bainbridge.
Yo
* 2020-07-23T21:47:32+10, David wrote:
> $ date --utc --date='23 Jul 2020 17:30 +1000'
> Thu 23 Jul 07:30:00 UTC 2020
While we are here let's also say this in more international date and
time format ISO 8601:
$ date --rfc-3339=seconds --utc --date="2020-07-23 17:30
On Thu, 23 Jul 2020 at 17:03, Keith bainbridge wrote:
> On 23/7/20 4:23 pm, Andrei POPESCU wrote:
> > For the future you might want to specify the UTC time instead.
> So, UTC 7:30 it is.
Hi Keith,
That is incomplete information, you need to specify the UTC date also.
For your
On Thu, Jul 23, 2020 at 04:45:43PM +1000, Keith bainbridge wrote:
> Probably right, but I wasn't sure if UTC adjusted to daylight saving time,
> and got a couple of conflicting versions when I searched.
It doesn't. If your local time zone does DST, you will notice that
your offset from UTC change
On Thu, Jul 23, 2020 at 04:52:48PM +1000, Keith bainbridge wrote:
> On 23/7/20 4:23 pm, Andrei POPESCU wrote:
> >On Ma, 21 iul 20, 17:39:09, Keith bainbridge wrote:
>
>
> I hadn't noticed this before, but where does 'the system' get my
> name from. Everything I can see here says Keith Bainbridge.
On 23/7/20 4:23 pm, Andrei POPESCU wrote:
On Ma, 21 iul 20, 17:39:09, Keith bainbridge wrote:
I hadn't noticed this before, but where does 'the system' get my name
from. Everything I can see here says Keith Bainbridge.
Email client: Thunderbird 79.0b2 (64-bit) - the beta version; on a mult
x27;t sure if UTC adjusted to daylight saving
time, and got a couple of conflicting versions when I searched.
So, UTC 7:30 it is.
--
Keith Bainbridge
keithr...@gmail.com
0447 667468
On Ma, 21 iul 20, 17:39:09, Keith bainbridge wrote:
>
> To get the timing right as close as possible, it is 17:40 as I send this
> note.
For the future you might want to specify the UTC time instead.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description:
This meet starts about 2hr 25min from now
Good evening All
I couldn't help notice how many of you suggested a Raspberry Pi as a
better alternative to trying to use an old PC, in answer to a recent
question.
I wondered if some of you would care to join a small user group in
regional Austr
Good evening All
I couldn't help notice how many of you suggested a Raspberry Pi as a
better alternative to trying to use an old PC, in answer to a recent
question.
I wondered if some of you would care to join a small user group in
regional Australia, whose prime purpose is using single bo
Le Magnétisme permet par simple imposition des mains de soulager en re-
harmonisant les energies.
Decouvrez les pouvoirs qui sont caches en vous !profitez de notre reduction
exceptionnelle de 35 %
Cette formation de Praticien en Magnetisme vise dans un premier temps, a faire
prendre conscie
messages during the wait.
If you edit /lib/udev/net.agent and change
do_everything > /dev/null 2> /dev/null &
to
( do_everything ) > /dev/null 2> /dev/null &
is the delay gone?
as if by magic, delay gone...
how did you find out?
The 30 second timeout is a udev internal tim
after
>>> that. I get no messages during the wait.
>>
>> If you edit /lib/udev/net.agent and change
>>
>> do_everything > /dev/null 2> /dev/null &
>>
>> to
>>
>> ( do_everything ) > /dev/null 2> /dev/null &
>>
>>
Michael Biebl wrote:
Am 25.07.2014 04:44, schrieb Hugo Vanwoerkom:
Anybody venture a guess as to what is happening? I have a 5 second
rootdelay specified in the kernel parameter list and this happens after
that. I get no messages during the wait.
If you edit /lib/udev/net.agent and change
do
On Fri 25 Jul 2014 at 05:42:38 +0200, Michael Biebl wrote:
> Am 25.07.2014 04:44, schrieb Hugo Vanwoerkom:
>
> >
> > Anybody venture a guess as to what is happening? I have a 5 second
> > rootdelay specified in the kernel parameter list and this happens after
> > that. I get no messages during t
Am 25.07.2014 04:44, schrieb Hugo Vanwoerkom:
>
> Anybody venture a guess as to what is happening? I have a 5 second
> rootdelay specified in the kernel parameter list and this happens after
> that. I get no messages during the wait.
If you edit /lib/udev/net.agent and change
do_everything > /d
Hi,
Running Sid and sysvinit. With the recent kernel upgrade in Sid from
3.14.10-1 to 3.14.12-1 there appeared a 30 second wait in the boot
process. It shows up in kernel.log, like so:
...
Jul 24 21:02:30 hda5 kernel: [ 11.363107] input: HDA NVidia Front Mic
as /devices/pci:00/:00
Zenaan Harkness, 13.01.2014:
> xscreensaver-command -version is getting called every 30 seconds. This
> causes my xscreensaver unlock/password dialog window to open up all
> the time...
>
> Any idea how I can find out what's calling this command every 30 seconds?
Try runnin
On 1/13/14, Chris Bannister wrote:
> On Mon, Jan 13, 2014 at 08:55:51PM +1100, Zenaan Harkness wrote:
>> xscreensaver-command -version is getting called every 30 seconds. This
>> causes my xscreensaver unlock/password dialog window to open up all
>> the time...
>>
>
On Mon, Jan 13, 2014 at 08:55:51PM +1100, Zenaan Harkness wrote:
> xscreensaver-command -version is getting called every 30 seconds. This
> causes my xscreensaver unlock/password dialog window to open up all
> the time...
>
> Any idea how I can find out what's calling t
xscreensaver-command -version is getting called every 30 seconds. This
causes my xscreensaver unlock/password dialog window to open up all
the time...
Any idea how I can find out what's calling this command every 30 seconds?
TIA
Zenaan
--
To UNSUBSCRIBE, email to debian-user
On 06/30/2013 11:38 PM, Andrei POPESCU wrote:
> [JFTR, I hit the same issue a while ago in unstable, and it took a while
> to clean via aptitude's interactive interface]
>
> On Du, 30 iun 13, 17:49:13, Jape Person wrote:
>>
>> So...my problem was that I was
[JFTR, I hit the same issue a while ago in unstable, and it took a while
to clean via aptitude's interactive interface]
On Du, 30 iun 13, 17:49:13, Jape Person wrote:
>
> So...my problem was that I was just using my package manager improperly.
> (Self-inflicted wounds are a
On 06/30/2013 04:01 PM, Jochen Spieker wrote:
> Patrick Wiseman:
>> On Sun, Jun 30, 2013 at 10:06 AM, Jape Person wrote:
>>>
>>> Forgive the facetious thread title, please. I just about got knocked out of
>>> my
>>> socks this morning when I ran my da
Patrick Wiseman:
> On Sun, Jun 30, 2013 at 10:06 AM, Jape Person wrote:
>>
>> Forgive the facetious thread title, please. I just about got knocked out of
>> my
>> socks this morning when I ran my daily upgrade checks in aptitude.
>>
>> I run Debian tes
On 06/30/2013 11:06 AM, Jape Person wrote:
> On 06/30/2013 10:40 AM, Patrick Wiseman wrote:
>> On Sun, Jun 30, 2013 at 10:06 AM, Jape Person wrote:
>>> Hi!
>>>
>>> Forgive the facetious thread title, please. I just about got knocked out of
>>>
On 06/30/2013 10:40 AM, Patrick Wiseman wrote:
> On Sun, Jun 30, 2013 at 10:06 AM, Jape Person wrote:
>> Hi!
>>
>> Forgive the facetious thread title, please. I just about got knocked out of
>> my
>> socks this morning when I ran my daily upgrade checks in apt
On Sun, Jun 30, 2013 at 10:06 AM, Jape Person wrote:
> Hi!
>
> Forgive the facetious thread title, please. I just about got knocked out of my
> socks this morning when I ran my daily upgrade checks in aptitude.
>
> I run Debian testing with Xfce, and I'd like to kee
Hi!
Forgive the facetious thread title, please. I just about got knocked out of my
socks this morning when I ran my daily upgrade checks in aptitude.
I run Debian testing with Xfce, and I'd like to keep it that way.
About a year ago I switched out Wicd for network-manager-gnome so that I could
m
30% Dto. Prueba este menú
I hate to "bump" my own message, but I'm making some progress and I'm
wondering if anyone can help me further debug.
My initial message:
On Mon, Jan 24, 2011 at 10:31 PM, Arturo R. wrote:
> Hi all.
>
> Per the title, I'd love to get your input on how to debug/fix this
> particular issue. A descr
Hi all.
Per the title, I'd love to get your input on how to debug/fix this
particular issue. A description of my setup:
Asus UL30A-X5 Laptop
1.3GHz Intel SU7300 Core 2 Duo
4GB of DDR3 RAM
500GB SATA
Intel GMA 4500MHD
Running Debian sid on a coLinux 0.7.8 (uname -a: "Linux colinux
2.6.33.5-co-0.7
Si vous ne pouvez pas lire cet email, cliquez ici
(http://front.chemise-web.eu/php/emailing/view_mail.php?CODE=50NV244E_66876&HASH=2a54fdef923fe4eeeb5c9db05c74d1cb)
Chemises homme : toutes les dernières tendances de la mode. Chemises 100% coton
cintrées ou coupes classiques, plus de 300 modè
Hi,
On Tue, Dec 29, 2009 at 6:28 AM, Mitchell Laks wrote:
> Hi
> I need to connect via a cisco router from a debian machine to a debian
> machine.
> after i run vpnc and after I am connected,
> suddenlym after about 30 minutes (i think), i find myself disconnected, even
>
Hi
I need to connect via a cisco router from a debian machine to a debian machine.
after i run vpnc and after I am connected,
suddenlym after about 30 minutes (i think), i find myself disconnected, even in
the
middle of active interaction.
I tried including the line
DPD idle timeout (our
On Monday 15 June 2009 08:20:23 debian-user-digest-requ...@lists.debian.org
wrote:
> > Even more. I get a bootup error message failing to set date (and time)
> > to ... the following day + 3 hours!!
>
> You may have a bad system clock. That does happen on some older
> hardware or if a CMOS battery
On Sun, Jun 14, 2009 at 04:50:23PM +0300, David Baron wrote:
> Even more. I get a bootup error message failing to set date (and time)
> to ... the following day + 3 hours!!
You may have a bad system clock. That does happen on some older
hardware or if a CMOS battery goes bad. I'd do the following
>>>Has been happening quite a bit lately:
>>>Problem with ntpdate. If and when it finally works, get a change of 10,800
>seconds ... that is 30 minutes.
>>>The dovecot IMAPd server is unreadable. Restarting it yields a complaint
>>>about 10,800 seconds of
On Thu, Jun 11, 2009 at 04:08:54PM +0300, David Baron wrote:
> >>Has been happening quite a bit lately:
>
> >>Problem with ntpdate. If and when it finally works, get a change of 10,800
> >seconds ... that is 30 minutes.
>
> >>The dovecot IMAPd serve
On Thu,11.Jun.09, 16:08:54, David Baron wrote:
> OK, time to fix this. Since my system comes up with the "correct" time zone
> but three hours later, it must be interpreting the stored (hw) time as GMT
> and
> adding the three hours (gmt+2 + daylight savings).
>
> How to fix this?
If you onl
>>Has been happening quite a bit lately:
>>Problem with ntpdate. If and when it finally works, get a change of 10,800
>seconds ... that is 30 minutes.
>>The dovecot IMAPd server is unreadable. Restarting it yields a complaint
>>about 10,800 seconds of time, killin
>Has been happening quite a bit lately:
>Problem with ntpdate. If and when it finally works, get a change of 10,800
>seconds ... that is 30 minutes.
>The dovecot IMAPd server is unreadable. Restarting it yields a complaint
>about 10,800 seconds of time, killing itself now! Rest
The current chrony initscript looks for a defaultroute at startup. If one
is found it puts chronyd online. The ip-up script is only used with PPP.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@list
On Sun, 7 Jun 2009 10:59:50 -0400
Daryl Styrk wrote:
...
> I've had nothing but great results with chrony. Aside from an issue of
> chrony falling back to 127.127.1.1 when it cannot connect to a ntp server..
> Which happens often with my laptop as I move around during the day.. I
> fixed tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jun 07, 2009 at 05:07:08PM +0300, David Baron wrote:
> Has been happening quite a bit lately:
>
> Problem with ntpdate. If and when it finally works, get a change of 10,800
> seconds ... that is 30 minutes.
>
> The dovec
1 - 100 of 227 matches
Mail list logo
