Got the idea (nft) and thanks for all help.
On 2024-07-03 04:22, Tim Woodall wrote:
On Tue, 2 Jul 2024, Jeff Peng wrote:
Hello gurus,
Is there a tool for maintaining the timeout for iptables rules?
for example, one IP would be blocked by my iptables for 24 hours, and
another IP should be
On Tue, 2 Jul 2024, Jeff Peng wrote:
Hello gurus,
Is there a tool for maintaining the timeout for iptables rules?
for example, one IP would be blocked by my iptables for 24 hours, and another
IP should be blocked for one week.
Off the top of my head I can't think exactly how to do i
Max Nikulin wrote:
> On 02/07/2024 19:28, Dan Ritter wrote:
> > iptables (which are currently implemented in nftables) don't have a native
> > timeout;
>
> nft sets have the timeout option. Isn't it to specify interval of time to
> remove elements?
It works w
On 02/07/2024 19:28, Dan Ritter wrote:
iptables (which are currently implemented in nftables) don't have a native
timeout;
nft sets have the timeout option. Isn't it to specify interval of time
to remove elements?
Jeff Peng wrote:
> Is there a tool for maintaining the timeout for iptables rules?
>
> for example, one IP would be blocked by my iptables for 24 hours, and
> another IP should be blocked for one week.
iptables (which are currently implemented in nftables) don't have a native
Hello gurus,
Is there a tool for maintaining the timeout for iptables rules?
for example, one IP would be blocked by my iptables for 24 hours, and
another IP should be blocked for one week.
Thanks.
On 04/06/2024 07:29, Vincent Lefevre wrote:
On 2024-05-31 19:05:45 +0700, Max Nikulin wrote:
Do you see an attempt to send SIGTERM to mutt before timeout and SIGKILL?
Unfortunately, there was no information from systemd. Some daemons
log a received SIGTERM, but mutt isn't a daemon.
On 2024-05-31 19:05:45 +0700, Max Nikulin wrote:
> Do you see an attempt to send SIGTERM to mutt before timeout and SIGKILL?
Unfortunately, there was no information from systemd. Some daemons
log a received SIGTERM, but mutt isn't a daemon.
> What other processes survived first step
send SIGTERM to mutt before timeout and
SIGKILL? What other processes survived first step? Are there something
suspicious before SIGKILL stage?
hile Mutt
> was still running. But this was the first time it did not exit.
I've tried a shutdown with Mutt still running in GNU Screen
a couple of times, and I got no timeout, i.e. Mutt exited as
expected.
--
Vincent Lefèvre - Web: <https://www.vinc17.net/>
100% accessib
utt:
May 29 01:55:26 qaa systemd[1]: session-2.scope: Stopping timed out. Killing.
May 29 01:55:26 qaa systemd[1]: session-2.scope: Killing process 2990 (mutt)
with signal SIGKILL.
May 29 01:55:26 qaa systemd[1]: session-2.scope: Failed with result 'timeout'.
May 29 01:55:26 qaa systemd
On 30/05/2024 23:19, Vincent Lefevre wrote:
Have you tried to send SIGTERM to mutt?
I didn't. AFAIK, systemd sends a SIGTERM to all the processes of the
session: that's the
Yes, SIGTERM is the default that systemd tries first. There are various
kill modes, another signal may be configured f
On 2024-05-30 00:19:30 +0700, Max Nikulin wrote:
> On 29/05/2024 07:44, Vincent Lefevre wrote:
> > But I don't understand why there was a timeout. Does this mean that
> > mutt didn't react to SIGTERM? Any reason?
>
> Have you tried to send SIGTERM to mutt?
I
1]: session-2.scope: Stopping timed out.
> > Killing.
> > May 29 01:55:26 qaa systemd[1]: session-2.scope: Killing process 2990
> > (mutt) with signal SIGKILL.
> > May 29 01:55:26 qaa systemd[1]: session-2.scope: Failed with result
> > 'timeout'.
> > Ma
On 29/05/2024 07:44, Vincent Lefevre wrote:
But I don't understand why there was a timeout. Does this mean that
mutt didn't react to SIGTERM? Any reason?
Have you tried to send SIGTERM to mutt? If it ignores this signal or the
reaction is some prompt then you need to find another w
systemd[1]: session-2.scope: Killing process 2990 (mutt)
> with signal SIGKILL.
> May 29 01:55:26 qaa systemd[1]: session-2.scope: Failed with result 'timeout'.
> May 29 01:55:26 qaa systemd[1]: Stopped session-2.scope - Session 2 of User
> vinc17.
> May 29 01:55:26 qaa
.
May 29 01:55:26 qaa systemd[1]: session-2.scope: Failed with result 'timeout'.
May 29 01:55:26 qaa systemd[1]: Stopped session-2.scope - Session 2 of User
vinc17.
May 29 01:55:26 qaa systemd[1]: session-2.scope: Consumed 8h 17min 54.832s CPU
time.
May 29 01:55:26 qaa systemd[1]: Stoppi
On a Bullseye host:
- Debootstrap a fresh Bookworm system
- Launch it in systemd-nspawn: sudo systemd-nspawn -b -D bookworm
- Type your login and password
- See the "message of the day"
- Exactly 2 minutes of nothing happening
- See the command prompt: user@machine:~$
The same happens if you log o
Loïc Grenié thanks!! Work well! I was trying to do a script exactly
like your script! Thanks and again thanks!
--- Begin Message ---
Hi,
Le mar. 21 juin 2022 à 10:14, Conti Stefano a écrit :
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in .bashrc
> of my user:
Hi,
Le mar. 21 juin 2022 à 10:14, Conti Stefano a écrit :
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in .bashrc
> of my user: TMOUT=600 to loogut after 10 minutes. Work, of course, but
> close all bash terminal!
>
> This is my sshd_config with i
Le mardi 21 juin 2022 à 23:40 +0200, didier gaumet a écrit :
[...]
> - if you want to restrict the time of ssh connection and are in
> position to modify the ssh command they use (an alias in their bashrc
> for example?), perhaps you can try to force the ssh -o option with
> the ConnectTimeout par
Le mardi 21 juin 2022 à 12:52 +0200, Conti Stefano a écrit :
> If I put ClientAliveCountMax 1 with ClientAliveInterval 600 timeout
> is 1200 inmy Debian 11. I have try all combinations but at the moment
> nothing happen; session stay alive! There is somethng but i don't
> und
On Tue, Jun 21, 2022 at 6:04 AM Greg Wooledge wrote:
> On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote:
> > Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> > .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> > cours
work all well because i
> put ClientAliveInterval 15 and after 15 seconds SSH session closed!
sshd_config(5) says:
ClientAliveInterval
Sets a timeout interval in seconds after which if no data has
been received from the client, sshd(8) will send a message
through
However thanks for your time of course!
On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote:
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> course, but close all bash terminal!
>
On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote:
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> course, but close all bash terminal!
>
> This is my sshd_config with i
If I put ClientAliveCountMax 1 with ClientAliveInterval 600 timeout is
1200 inmy Debian 11. I have try all combinations but at the moment
nothing happen; session stay alive! There is somethng but i don't
understand what keep alive the session...
--- Begin Message ---
Le mardi 21 juin 2022
Le mardi 21 juin 2022 à 10:05 +0200, Conti Stefano a écrit :
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> course, but close all bash terminal!
>
> This is my sshd_config with i
Hello! In My Debian 11 SSH timeout logoff not work! I must put in
.bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
course, but close all bash terminal!
This is my sshd_config with info for timeout:
TCPKeepAlive no
ClientAliveInterval 600
ClientAliveCountMax 0
Any suggest?
On Jo, 09 dec 21, 21:33:29, Tobias Boesch wrote:
> Hello Debian Team,
>
> I would like to report a bug at Debian, but I don't know which package
> I should use for the report. Please help me categorise this problem.
>
> I run Debian 11 with systemd (247.3-6) and I experience services
> timeouts a
20:30:04 tobias-pc systemd[798]:
gnome-session-manager@gnome.service: Killing process 1663 (Lirc) with
signal SIGKILL.
Dez 07 20:30:04 tobias-pc systemd[798]:
gnome-session-manager@gnome.service: Failed with result 'timeout'.
Dez 07 20:30:04 tobias-pc systemd[798]: Stopped GNOME Session Manager
David Wright writes:
> So on the odd occasion, you turn on the machine and, at a mininum, are
> about to type in some commands to boot the machine manually. And then
> you might even log in. Having to type /one/ keystroke at the start is
> just too much.
>
> Is that what you're really saying?
No
On Tuesday, July 13, 2021 06:24:27 PM David Wright wrote:
> On Tue 13 Jul 2021 at 15:43:55 (-0400), rhkra...@gmail.com wrote:
> > I'm not the OP, and I don't boot very often at all -- my machines run
> > 24/7 for months on end, so I don't know / remember what has to be done
> > in GRUB to get to t
On Tue 13 Jul 2021 at 15:43:55 (-0400), rhkra...@gmail.com wrote:
> On Tuesday, July 13, 2021 11:34:48 AM David Wright wrote:
> > So on the odd occasion, you turn on the machine and, at a mininum, are
> > about to type in some commands to boot the machine manually. And then
> > you might even log i
On Tuesday, July 13, 2021 11:34:48 AM David Wright wrote:
> So on the odd occasion, you turn on the machine and, at a mininum, are
> about to type in some commands to boot the machine manually. And then
> you might even log in. Having to type /one/ keystroke at the start is
> just too much.
>
> Is
On Tue 13 Jul 2021 at 10:54:07 (+0200), Steve Keller wrote:
> Brian writes:
>
> > > I'd prefer to be dropped into the GRUB command line instead of that
> > > menu. But still I'd like to have the timeout after which a default
> > > entry is
Brian writes:
> > I'd prefer to be dropped into the GRUB command line instead of that
> > menu. But still I'd like to have the timeout after which a default
> > entry is boot if no command is entered at the prompt.
>
> You want GRUB's normal operation bu
el command lines appears to choose from. If no
> > > selection is made within a few seconds (default is 5s IIRC), the
> > > default entry is booted.
> > > I'd prefer to be dropped into the GRUB command line instead of that
> > > menu. But still I'd like to
ion is made within a few seconds (default is 5s IIRC), the
> > default entry is booted.
>
> Sounds about right.
>
> > I'd prefer to be dropped into the GRUB command line instead of that
> > menu. But still I'd like to have the timeout after which a default
> >
ted.
Sounds about right.
> I'd prefer to be dropped into the GRUB command line instead of that
> menu. But still I'd like to have the timeout after which a default
> entry is boot if no command is entered at the prompt.
You want GRUB's normal operation but, at the same t
ry is booted.
>
> I'd prefer to be dropped into the GRUB command line instead of that
> menu. But still I'd like to have the timeout after which a default
> entry is boot if no command is entered at the prompt.
>
> Can that be configured in GRUB?
‘GRUB_TIMEOUT_STYLE’
menu. But still I'd like to have the timeout after which a default
entry is boot if no command is entered at the prompt.
Can that be configured in GRUB?
Steve
anyway it work fine
except when it can not talk to the dhcp
then it just continues try'n forever to connect to the dhcp
this is where i need a timeout
so it will give up and i can unlock the fs at the console
On Lu, 06 apr 20, 10:33:36, Pierre Frenkiel wrote:
> On Mon, 6 Apr 2020, Andrei POPESCU wrote:
>
> > Long term you might need a hold or pin for that (my preference would be
> > a pin).
>
>hi Andrei,
>I felt that the description of the pinning process is rather
>confusing, either in th
On Mon, 6 Apr 2020, Andrei POPESCU wrote:
Long term you might need a hold or pin for that (my preference would be
a pin).
hi Andrei,
I felt that the description of the pinning process is rather
confusing, either in the apt-get man or the aptitude man.
Can you tell me what whould be
On Du, 05 apr 20, 19:21:31, Pierre Frenkiel wrote:
> On Sun, 5 Apr 2020, Pierre Frenkiel wrote:
>
> > let them remove getmail if thay are not able to support it.
> > As I'm perfectly happy with the present Debian version,
> > I'll just keep it, disabling my upgrade process, until getmail support
>
On 2020-04-04 21:46, Andrei POPESCU wrote:
On Sb, 04 apr 20, 19:30:05, Pierre Frenkiel wrote:
On Sat, 4 Apr 2020, Andrei POPESCU wrote:
> You have to keep also a Python 2 interpreter for it.
same question: why would it disapear ?
Because it's not supported upstream anymore.
https://legacy
On Sun, 5 Apr 2020, Pierre Frenkiel wrote:
let them remove getmail if thay are not able to support it.
As I'm perfectly happy with the present Debian version,
I'll just keep it, disabling my upgrade process, until getmail support
reappears.
actually, I was too drastic: as "apt-get upgrade" g
On Sun, 5 Apr 2020, songbird wrote:
Celejar wrote:
...
https://marc.info/?l=getmail&m=157365887605305&w=2
let them remove getmail if thay are not able to support it.
As I'm perfectly happy with the present Debian version,
I'll just keep it, disabling my upgrade process, until getmail supp
Celejar wrote:
...
> https://marc.info/?l=getmail&m=157365887605305&w=2
well that didn't happen and as soon as anyone
expressed any interest in carrying patches Osamu
pretty much just said take over the package because
he wasn't interested in it any more. and then the
topic dropped because nobo
On Sat, 4 Apr 2020 06:34:41 -0400
songbird wrote:
> Pierre Frenkiel wrote:
> >>>> I have the following problem with fetchmail:
> >>>> fetchmail: timeout after 300 seconds waiting for server
> >>>> imap.gmail.com.
> >
> >hi,
&g
On Sb, 04 apr 20, 19:30:05, Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, Andrei POPESCU wrote:
>
> > You have to keep also a Python 2 interpreter for it.
>
> same question: why would it disapear ?
Because it's not supported upstream anymore.
https://legacy.python.org/dev/peps/pep-0373/
Debia
songbird wrote:
...
> in my nosing around i've found this:
>
> https://gitlab.com/dkg/getmail/commits/python3
i meant that to be:
https://gitlab.com/dkg/getmail
songbird
Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, Andrei POPESCU wrote:
>
>> You have to keep also a Python 2 interpreter for it.
>
>same question: why would it disapear ?
>
> best regards,
because eventually it stops being packaged or kept up
and gets left behind long enough that nobody cares to
On Sat, 4 Apr 2020, Andrei POPESCU wrote:
You have to keep also a Python 2 interpreter for it.
same question: why would it disapear ?
best regards,
--
Pierre Frenkiel
On Sb, 04 apr 20, 12:44:38, Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, songbird wrote:
>
> > yes, but don't get too complacent as eventually
> > getmail goes away if nobody ports it to python3.
> >
>thank you for the advice, but I imagine it will not disappear from my disk,
>even if it
On Sat, 4 Apr 2020, songbird wrote:
yes, but don't get too complacent as eventually
getmail goes away if nobody ports it to python3.
thank you for the advice, but I imagine it will not disappear from my disk,
even if it is no more supported.
best regards,
--
Pierre Frenkiel
Pierre Frenkiel wrote:
>>>> I have the following problem with fetchmail:
>>>> fetchmail: timeout after 300 seconds waiting for server
>>>> imap.gmail.com.
>
>hi,
>the fix I found was to abandon fetchmail. I'm using now getmail, which
I have the following problem with fetchmail:
fetchmail: timeout after 300 seconds waiting for server
imap.gmail.com.
hi,
the fix I found was to abandon fetchmail. I'm using now getmail, which
works perfectly
best regards,
--
Pierre Frenkiel
On 3/29/20, to...@tuxteam.de wrote:
> On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
>> hi,
>> I have the following problem with fetchmail:
>> fetchmail: timeout after 300 seconds waiting for server
>> imap.gmail.com.
>> here is
On 2020-03-29 13:24, Reco wrote:
On Sun, Mar 29, 2020 at 01:46:12PM +0200, Pierre Frenkiel wrote:
Mike fetchmail, getmail gives a Time Out
OP
did you select "allow non-standard email client" or whatever it is at
gmail ?
use SimpleIMAPSSLReciever ?
[retriever]
type=SimpleIMAPSSLRetriever
se
Please CC the list. And please refrain from top posting.
On Sun, Mar 29, 2020 at 01:46:12PM +0200, Pierre Frenkiel wrote:
> Mike fetchmail, getmail gives a Time Out
Two options left.
> >1) Try using POP3 instead of IMAP.
> >
> >3) Make a forward to your gmx mailbox from gmail.
Reco
Hi.
On Sun, Mar 29, 2020 at 10:06:19AM +0200, Pierre Frenkiel wrote:
> as requested, here is the output of fetchmail -v
So, login's good:
> fetchmail: IMAP> A0002 LOGIN "pierre.frenkiel" *
> fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID
> XLIST CHILDREN X-GM-E
> best regards,
Can you use imap with another client? (mutt/thunderbird). It seems, that
gmail let you to logi, get message list, but then is timeout at first
message body. I'd ask gmail help now.
KJ
--
http://wolnelektury.pl/wesprzyj/teraz/
On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc
If I followed correctly, you're trying to ac
On 2020-03-29 09:06, Pierre Frenkiel wrote:
as requested, here is the output of fetchmail -v
you can see at the end "reading message ...", but I can't find it
with gmail you have to select "allow non-conforming clients" or
something.
I had problems with fetchmail and gmail ( forget what exactl
as requested, here is the output of fetchmail -v
you can see at the end "reading message ...", but I can't find it
please reply pierre.frenk...@gmx.com
fetchmail: starting fetchmail 6.4.0.beta4 daemon
fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at Sun 29 Mar
2020 10:00:1
Pierre Frenkiel writes:
> poll imap.gmail.com with proto IMAP auth password
It is just side comments. There is alternative software. The name is
getmail[*]. The getmail supports Gmail's label. It is available to
downloading messages from each Gmail's label. Personaly i use getmail
with Gnus. Alw
Cindy Sue Causey writes:
> ..
> While checking trending one more time to see if there were any current
> references, a new trending topic is that Twitter direct messages are
> taking a hit right now. It all seems an understandable, predictable
> social networking side effect in light of our W
On 3/28/20, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server
> imap.gmail.com.
> here is my .fetchmailrc
Poking my nose in to say that Gmail AND Youtube were down in last
couple days. I
Hi.
On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc
fetchmail -v
Reco
On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc
>
>
> set logfile "/data/home/frenkiel/lo
hi,
I have the following problem with fetchmail:
fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
here is my .fetchmailrc
set logfile "/data/home/frenkiel/log/fetchmail"
set pidfile "/data/home/frenkiel/.fetchmail.pid"
set postmaster "f
Il 28/06/2018 18:52, David Wright ha scritto:
I don't think the presence of the mountpoint itself is a problem.
I can confirm it's not the culprit: I've tried commenting out all
network mountpoints in /etc/fstab but the problem remains.
However there was something in the error message that m
On Wed 27 Jun 2018 at 19:17:51 (+0200), Lucio wrote:
> Il 25/06/2018 16:51, David Wright ha scritto:
> >Do you have a symlink from your home/current working directory
> >pointing to a networked file system (like gvfs, in the light of
> >that error message) which the dialog box is trying to resolve
Il 25/06/2018 16:51, David Wright ha scritto:
Do you have a symlink from your home/current working directory
pointing to a networked file system (like gvfs, in the light of
that error message) which the dialog box is trying to resolve
before it can display itself?
Well, sort of, but probably no
Il 24/06/2018 20:15, bw ha scritto:
I had the same thing happen to me on kde, but only for vlc prog. The
first time I opened a file it took 25 sec for the dialog to pop up. It
drove me crazy.
I eventually solved it, but I can't remember how, sorry. The steps I took
were something like this:
oxy: error calling startservicebyname for
> org.gtk.vfs.GoaVolumeMonitor: timeout was reached (g-io-error-quark,
> 24)
>
> The timeout happens only on the first file dialog opening for each
> program session, subsequent ones show up instantly. If I close the
> program and open it again,
Thunderbird and Google Chrome.
If I run the program in a terminal it's the same, but at least I get an
error in the terminal just after the 25 seconds expire:
Error creating proxy: error calling startservicebyname for
org.gtk.vfs.GoaVolumeMonitor: timeout was reached (g-io-error-quark, 24)
On Wed 16 May 2018 at 14:09:43 (+0200), Sven Joachim wrote:
> On 2018-05-16 06:04 -0500, Dave Sherohman wrote:
>
> > I'm running a galera cluster of three mariadb servers. It's been
> > brought down twice because one node has detected an inconsistency,
> > killed itself, and then systemd automati
On Wed, May 16, 2018 at 02:09:43PM +0200, Sven Joachim wrote:
> Have you tried setting TimeoutStartSec rather than TimeoutStartUSec?
> Though I have to admit that I did not perform a web search but cheated
> by looking at the systemd.service(5) manpage, which mentions the former
> but not the latte
On 2018-05-16, Sven Joachim wrote:
>>
>> # systemctl edit mysql
>>
>> # systemctl show mysql -p TimeoutStartUSec
>> TimeoutStartUSec=1min 30s
>> # systemctl daemon-reload
>> # systemctl show mysql -p TimeoutStartUSec
>> TimeoutStartUSec=1min 30s
>> # systemctl daemon-reexec
>> # systemctl show my
On 2018-05-16 06:04 -0500, Dave Sherohman wrote:
> I'm running a galera cluster of three mariadb servers. It's been
> brought down twice because one node has detected an inconsistency,
> killed itself, and then systemd automatically restarted it. This is all
> good so far.
>
> The problem comes
Short version:
How can I extend (or remove) the startup timeout for a single systemd
service?
Longer version:
I'm running a galera cluster of three mariadb servers. It's been
brought down twice because one node has detected an inconsistency,
killed itself, and then systemd aut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Apr 21, 2018 at 10:50:47AM +0200, Rainer Dorsch wrote:
> Hi Tomás,
>
> many thanks for your response :-)
[...]
> retry temporary address regeneration
> Apr 21 10:36:01 master kernel: [3019221.240105] IPv6: ipv6_create_tempaddr:
[...]
> Al
Hi Tomás,
many thanks for your response :-)
Am Samstag, 21. April 2018, 08:43:20 CEST schrieb to...@tuxteam.de:
> On Fri, Apr 20, 2018 at 10:20:12PM +0200, Rainer Dorsch wrote:
> > Am Freitag, 20. April 2018, 22:13:11 CEST schrieb to...@tuxteam.de:
> > > curl -I http://security.debian.org/debian-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 20, 2018 at 10:20:12PM +0200, Rainer Dorsch wrote:
> Am Freitag, 20. April 2018, 22:13:11 CEST schrieb to...@tuxteam.de:
> > curl -I http://security.debian.org/debian-security/
>
> root@master:~/tmp# curl -I http://ftp.de.debian.org/debian
) ...
Setting up libreoffice-help-en-us (1:5.2.7-1+deb9u4) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Error: Timeout was reached
root@master:~#
Am Freitag, 20. April 2018, 22:41:34 CEST schrieb Michael Lange:
> Hi,
>
> On Fri, 20 Apr 2018 22:20:12 +0200
>
> Raine
ontrib non-free
here the entry in sources.list looks slightly different:
deb http://security.debian.org/ stretch/updates main contrib non-free
I wouldn't think this makes much difference, but just in case the timeout
occurs always with the security mirror it might be worth a try.
> root@mas
Am Freitag, 20. April 2018, 22:13:11 CEST schrieb to...@tuxteam.de:
> curl -I http://security.debian.org/debian-security/
root@master:~/tmp# curl -I http://ftp.de.debian.org/debian/
HTTP/1.1 200 OK
Date: Fri, 20 Apr 2018 20:19:14 GMT
Server: Apache/2.4.10 (Debian)
Content-Type: text/html;charset=U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 20, 2018 at 10:02:40PM +0200, Rainer Dorsch wrote:
> Hi,
>
> I see often the error:
> Error: Timeout was reached
> during an apt-get update.
[...]
> Hit:2 http://ftp.de.debian.org/debi
Hi,
I see often the error:
Error: Timeout was reached
during an apt-get update.
Any idea what could cause this and how to debug it?
The entire configuration is shown below.
root@master:~# apt-get -v
apt 1.4.8 (amd64)
Supported modules:
*Ver: Standard .deb
*Pkg: Debian dpkg interface
List good morning,
I am trying to access our MTA from offsite over an SSH tunnel, but the
MUA (Thunderbird) is reporting a timeout on accessing the MTA.
The server is Wheezy; sshd is running; the tunnel is set up to
terminate on the same server that runs the MTA (exim), as well as
running
On Sun, 2015-06-07 at 19:20 +0800, mudongliang wrote:
> Just as what you said , I should see the boot menu by the setting of
> LinuxMint.
> This setting will wait 10 seconds for me to press key to continue!
> Why I can not see the boot menu? And when I delete the
> GRUB_HIDDEN_TIMEOUT and GRUB_HID
Wait this many seconds before displaying the menu. If is
pressed during that time, display the menu and wait for input
according to `GRUB_TIMEOUT'. If a hotkey associated with a menu
entry is pressed, boot the associated menu entry immediately. If
the timeout expires befor
27;
Wait this many seconds before displaying the menu. If is
pressed during that time, display the menu and wait for input
according to `GRUB_TIMEOUT'. If a hotkey associated with a menu
entry is pressed, boot the associated menu entry immediately. If
the timeout expires
Today I compile the linux kernel 4.0.0 in LinuxMint!When I update grub
and reboot into the system , I can only get into 4.0.0 kernel!
The content of /etc/default/grub is following:
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -
On Jul 28, 2014, at 3:32 AM, Michael Biebl wrote:
> Am 28.07.2014 10:54, schrieb Rick Thomas:
>> In my continuing quest for enough understanding of systemd to be able to
>> actually use it in real-life situations, I’ve set up a VM running the latest
>> Jessie release. In the spirit of experim
Am 28.07.2014 10:54, schrieb Rick Thomas:
> In my continuing quest for enough understanding of systemd to be able to
> actually use it in real-life situations, I’ve set up a VM running the latest
> Jessie release. In the spirit of experimentation, I set it up with root,
> swap and home as LVs o
journal that shows the behavior.
The delay and timeout occur between 18:54:10 to 18:55:39.
NOTE: the root and /home filesystems have already been fsck’ed and mount’ed
*well before* the time-out occurs, so it *is* finding the key file.
Enjoy!
Rick
PS: As always, I’m happy to RTFM — if someone
1 - 100 of 432 matches
Mail list logo
