Hi there,
I'm using busybox-syslogd. I'm trying to make it log to remote system
and to memory buffer. According to manual I should use -R 192.168.1.1
for remote logging and -C128 option for memory buffer. Unfortunately,
when used together logs are only sent to remote server. On Bookworm
On 10/08/2023 16:53, gene heskett wrote:
On 8/9/23 21:15, Max Nikulin wrote:
On 08/08/2023 09:57, gene heskett wrote:
dbus-update-activation-environment: error: unable to connect to
D-Bus: Failed to connect to socket /run/user/1000/bus: Connection
refused
...
Try to figure out at which
On 8/9/23 21:24, Max Nikulin wrote:
On 08/08/2023 19:07, gene heskett wrote:
digikam for example, does report what I assume is the package name,
just running it, reports a couple screens full of Exiv2 errors, but
Exiv2 is installed.
I have an impression that properly built AppImage should
On 8/9/23 21:15, Max Nikulin wrote:
On 08/08/2023 09:57, gene heskett wrote:
Xsession: X session started for gene at Tue 27 Jun 2023 02:58:23 PM EDT
^^^
dbus-update-activation-environment: error: unable to connect to D-Bus:
Failed to
On 08/08/2023 19:07, gene heskett wrote:
digikam for example, does report what I assume is the package name, just
running it, reports a couple screens full of Exiv2 errors, but Exiv2 is
installed.
I have an impression that properly built AppImage should come with all
necessary libraries
On 08/08/2023 09:57, gene heskett wrote:
Xsession: X session started for gene at Tue 27 Jun 2023 02:58:23 PM EDT
^^^
dbus-update-activation-environment: error: unable to connect to D-Bus:
Failed to connect to socket /run/user/1000/bus:
On 8/9/23 10:47, debian-u...@howorth.org.uk wrote:
gene heskett wrote:
Someplace where an AppImage looking for a missing dependency might
express its displeasure at not finding everything it needs?
I've always thought that was a main advantage of starting anything from
the command line -
gene heskett wrote:
> Someplace where an AppImage looking for a missing dependency might
> express its displeasure at not finding everything it needs?
I've always thought that was a main advantage of starting anything from
the command line - there's an obvious place for the output - the
gene heskett wrote:
>songbird wrote:
...
>>man journald.conf...
>
> I've looked at that, even looked at the file. It is all systemd
> related, no mention of user stuffs. Its as if a 3 meter tall board
> fence has been built around the systemd stuff that user apps can't get thru.
no, i
On Tue, Aug 08, 2023 at 10:33:04AM -0400, gene heskett wrote:
> On 8/8/23 00:51, to...@tuxteam.de wrote:
[...]
> > See, if you "do" AppImages you are multiplying your system's complexity.
[...]
> And that's sad, Tomas. The current, nominally 7 day old AppImage of
> OpenSCAD can load and
let's be scientific: what evidence makes you assume that there's anything
in the logs you are not shown?
see gigabytes of stuff from kwin etc, but nary a syllable from what isn't
working because something blocks it.
Perhaps "what isn't working" isn't logging to the syslogs at all? (this
ith something called an "AppImage", whatever the hell that is, the
details are not likely to show up in system logs.
If you don't like journalctl and related things, install rsyslog. It
will take less than a minute, and then your system logging will be back
to normal. You can read the files
On Mon, Aug 07, 2023 at 05:32:03PM -0400, gene heskett wrote:
> On 8/7/23 13:23, Henning Follmann wrote:
> > On Mon, Aug 07, 2023 at 09:41:11AM -0400, gene heskett wrote:
> > > On 8/7/23 07:50, Henning Follmann wrote:
> > > > On Sat, Aug 05, 2023 at 03:12:39PM -0400, Greg Wooledge wrote:
> > > > >
makes you assume that there's anything
in the logs you are not shown?
> see gigabytes of stuff from kwin etc, but nary a syllable from what isn't
> working because something blocks it.
Perhaps "what isn't working" isn't logging to the syslogs at all? (this
hunch has come up
blem
with something called an "AppImage", whatever the hell that is, the
details are not likely to show up in system logs.
If you don't like journalctl and related things, install rsyslog. It
will take less than a minute, and then your system logging will be back
to normal. You can re
On 8/7/23 22:08, Max Nikulin wrote:
On 08/08/2023 00:35, gene heskett wrote:
There is not a way to have it start doing the trace when I click on
the save to disk button.
Really? And certainly --attach/-p option is not a rescue.
Sending output to a file, filtering specific calls, increasing
On 08/08/2023 00:35, gene heskett wrote:
There is not a way to have it start doing the trace when I click on the
save to disk button.
Really? And certainly --attach/-p option is not a rescue.
Sending output to a file, filtering specific calls, increasing per line
size limit are useless
On 8/7/23 20:00, songbird wrote:
gene heskett wrote:
...
I believe konsole is unlimited by default. On checking in settings, its
not listed. Scrollback is from my /tmp, which would be on my raid10, so
maybe that something else that is blocked from useing my raid10. IDK.
ulimit reports
gene heskett wrote:
...
> I believe konsole is unlimited by default. On checking in settings, its
> not listed. Scrollback is from my /tmp, which would be on my raid10, so
> maybe that something else that is blocked from useing my raid10. IDK.
> ulimit reports unlimited. And there is 32G of
On 8/7/23 16:16, songbird wrote:
gene heskett wrote:
...
Many times over the last 25 years. However this problem occurs when it
has already output several gigabytes of previous data the shell has
scrolled off the end of th buffer.. There is not a way to have it start
doing the trace when I
On 8/7/23 13:23, Henning Follmann wrote:
On Mon, Aug 07, 2023 at 09:41:11AM -0400, gene heskett wrote:
On 8/7/23 07:50, Henning Follmann wrote:
On Sat, Aug 05, 2023 at 03:12:39PM -0400, Greg Wooledge wrote:
On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
On Sat, 5 Aug 2023 15:09:41
gene heskett wrote:
...
> Many times over the last 25 years. However this problem occurs when it
> has already output several gigabytes of previous data the shell has
> scrolled off the end of th buffer.. There is not a way to have it start
> doing the trace when I click on the save to disk
On 8/7/23 12:19, songbird wrote:
gene heskett wrote:
...
Absolutely none of that makes it to the log I can read with sudo.
This causes me to ask about any new ACL's bookworm might have put in
place, but questions about that have so far been totally ignored. I
according to an ls -lR, own that
On Mon, Aug 07, 2023 at 09:41:11AM -0400, gene heskett wrote:
> On 8/7/23 07:50, Henning Follmann wrote:
> > On Sat, Aug 05, 2023 at 03:12:39PM -0400, Greg Wooledge wrote:
> > > On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> > > > On Sat, 5 Aug 2023 15:09:41 +
> > > > Andy Smith
gene heskett wrote:
...
> Absolutely none of that makes it to the log I can read with sudo.
>
> This causes me to ask about any new ACL's bookworm might have put in
> place, but questions about that have so far been totally ignored. I
> according to an ls -lR, own that raid10 lock, stock and
to normal.
err,
"how to get back."
Normal is the new systemd
And the new logging is journal.d or some such. And I so far have not
been able to detect from reading its tail equ, what port of which card
is WHICH PHYSICAL DRIVE? Logging is IMO incomplete until I can easily
locate the dri
On Sat, Aug 05, 2023 at 03:12:39PM -0400, Greg Wooledge wrote:
> On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> > On Sat, 5 Aug 2023 15:09:41 +
> > Andy Smith wrote:
>
[...]
> In some cases, the release notes actually do tell you how to get back
> to normal.
err,
"how to get back."
On 06/08/2023 02:03, Joe wrote:
I use 'tail -f ' at least
once a week
journalctl -f
ular packages, that does not seem likely.
I suppose it could happen though, if journald got all the features
of every syslogd. Still one of the design goals of journald was the
structured (binary format) logging whereas plain text logging is a
very popular syslog feature, so that still doesn't seem lik
On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> On Sat, 5 Aug 2023 15:09:41 +
> Andy Smith wrote:
> > The release notes in particular are essential reading since
> > otherwise a person won't know about major components that have
> > changed, been replaced etc.
>
> Indeed, but they
On Sat, 5 Aug 2023 15:09:41 +
Andy Smith wrote:
> Hello,
>
> On Sat, Aug 05, 2023 at 09:23:25AM -0400, Greg Wooledge wrote:
> > In any case, this is not a popular change.
>
> I don't think that's clear. I think that amongst a population of
> people who care d
Hello,
On Sat, Aug 05, 2023 at 09:23:25AM -0400, Greg Wooledge wrote:
> In any case, this is not a popular change.
I don't think that's clear. I think that amongst a population of
people who care deeply about logging it's generally unfavourable,
and I myself don't particularly enjoy us
Hello,
On Sat, Aug 05, 2023 at 08:56:36AM -0400, Carl Fink wrote:
> It is highly probable that I'm being grumpy because Debian changed
> something that I was used to for decades, without my realizing it.
…because you didn't read the release notes that are absolutely
required reading to
* 2023-08-05 09:23:25-0400, Greg Wooledge wrote:
> In any case, this [systemd journal] is not a popular change. I don't
> remember ever hearing a single person say "Wow, I'm so glad they did
> this!" I've seen many complaints. Most often, people just (re)install
> rsyslog and move on with their
in
*using* my
computer than learning whole new paradigms about, say, logging. Changing things
will *always* be perceived as friction unless someone explains clearly why it
makes
sense, to me personally.
-Carl Fink
I have syslog, and journald.
about having syslog, it is probably because I install
On Sat, Aug 05, 2023 at 02:12:31PM +0100, Brian wrote:
> Does this clarify?
>
> https://wiki.debian.org/Rsyslog#Deprecation_in_Bookworm
Ah, I didn't know about that page. It links to bug #1018788 which
says, among other things,
The main reason here is, that I want to avoid that log data
igms about, say, logging. Changing
> things
> will *always* be perceived as friction unless someone explains clearly why
> it makes
> sense, to me personally.
You're unlikely to get a satisfactory explanation. My best guess is they
(the Debian developers in question) think systemd
highly probable that I'm being grumpy because Debian changed something
> that
> I was used to for decades, without my realizing it. I'm more interested in
> *using* my
> computer than learning whole new paradigms about, say, logging. Changing
> things
> will *always* be pe
whole new paradigms about, say, logging. Changing
things
will *always* be perceived as friction unless someone explains clearly
why it makes
sense, to me personally.
-Carl Fink
On 2023-08-04, Carl Fink wrote:
> Today, on my Bullseye system, X crashed and restarted. Naturally, I thought
> I'd check my logs to see if I could find out why.
>
> Well, no ... because syslog does not exist.
If you don't have syslog your logs will be on journald.
But X logs could be in
On Fri, Aug 04, 2023 at 10:40:37PM -0400, Carl Fink wrote:
> Today, on my Bullseye system, X crashed and restarted. Naturally, I thought
> I'd check my logs to see if I could find out why.
>
> Well, no ... because syslog does not exist.
>
> Is it really the default to have no/v
Today, on my Bullseye system, X crashed and restarted. Naturally, I
thought I'd check my logs to see if I could find out why.
Well, no ... because syslog does not exist.
Is it really the default to have no/very little logging when using
mostly the default install? (I just installed syslog-ng
On 2023-05-10 09:28:51 -0400, Greg Wooledge wrote:
> On Wed, May 10, 2023 at 03:19:31PM +0200, Vincent Lefevre wrote:
> > On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> > > Note: if you play with .ssh/rc, be careful as there is a risk
> > > that you may not log in any more with ssh in case
On Wed, May 10, 2023 at 03:19:31PM +0200, Vincent Lefevre wrote:
> On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> > Note: if you play with .ssh/rc, be careful as there is a risk
> > that you may not log in any more with ssh in case of mistake
> > (I'm wondering whether there is an
On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> Note: if you play with .ssh/rc, be careful as there is a risk
> that you may not log in any more with ssh in case of mistake
> (I'm wondering whether there is an undocumented way to skip it).
For this point, there are solutions there:
On 2023-05-10 14:36:25 +0200, Vincent Lefevre wrote:
[...]
> zira:~> ssh cventin xterm
> Connected to cventin (from 140.77.51.8)
> OS: Debian GNU/Linux 12 (bookworm) [x86_64]
> DISPLAY: localhost:11.0
>
> and xterm is started as expected. FYI, some data, like DISPLAY, are
> output by my .ssh/rc
On 2023-05-09 20:07:26 +0200, zithro wrote:
> On 09 May 2023 18:06, Vincent Lefevre wrote:
> > On 2023-05-05 15:04:27 +0200, zithro wrote:
> > >
> > > journalctl after GUI LOGOFF
> > >
On 2023-05-09 14:17:14 -0400, Dan Ritter wrote:
> zithro wrote:
> > On 09 May 2023 17:47, Vincent Lefevre wrote:
> > > BTW, you should also try GNU Screen to see if you have the same issue
> > > with it (this could help debugging).
> >
> > Do you mean trying "ssh u@h screen" ?
> > Never tried
On 2023-05-09 19:44:48 +0200, zithro wrote:
> On 09 May 2023 17:47, Vincent Lefevre wrote:
> > Hi,
> >
> > On 2023-05-04 21:07:17 +0200, zithro wrote:
> > > Here is what happens chronologically :
> > >
> > > 1. I start various SSH connections to a host, some normal, some with X
> > > forwarding,
zithro wrote:
> On 09 May 2023 17:47, Vincent Lefevre wrote:
> > BTW, you should also try GNU Screen to see if you have the same issue
> > with it (this could help debugging).
>
> Do you mean trying "ssh u@h screen" ?
> Never tried screen with GUI apps, does that work ?
Not in a useful way. For
On Tue, May 09, 2023 at 08:07:26PM +0200, zithro wrote:
> I use Ctrl-D to close ssh sessions, "~." does not work, I get "bash: command
> not found".
To use the tilde commands in the ssh client, they have to be at the
"beginning of a line", which means you have to press Enter first. Or
at least
On 09 May 2023 18:06, Vincent Lefevre wrote:
On 2023-05-05 15:04:27 +0200, zithro wrote:
journalctl after GUI LOGOFF
[...]
May 05 14:09:14 debzit
On 09 May 2023 17:47, Vincent Lefevre wrote:
Hi,
On 2023-05-04 21:07:17 +0200, zithro wrote:
Here is what happens chronologically :
1. I start various SSH connections to a host, some normal, some with X
forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP"
(like firejail
On 2023-05-05 15:04:27 +0200, zithro wrote:
>
> journalctl after GUI LOGOFF
>
[...]
> May 05 14:09:14 debzit sshd[14246]: Received disconnect from IP.IP.IP.IP
>
Hi,
On 2023-05-04 21:07:17 +0200, zithro wrote:
> Here is what happens chronologically :
>
> 1. I start various SSH connections to a host, some normal, some with X
> forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP"
> (like firejail firefox, firejail thunderbird, etc).
On 06 May 2023 07:07, to...@tuxteam.de wrote:
On Sat, May 06, 2023 at 10:24:52AM +0700, Max Nikulin wrote:
Thanks both for the pointers, will report back with results
On 05 May 2023 19:14, Max Nikulin wrote:
Does it happen for newly created user with no customization?
Never tried !
I recommended to do it just for a case that you added something to init
files for the "zithro" user.
AFAIK I didn't customize a lot, as I'm rarely logging to X.
Bu
keep the X login open till I close all ssh
sessions, but it's using ressources for nothing.
Except NOT logging in X (which I rarely do), the quickest fix would be
to remove systemd altogether, it's only there because it's Debian's
defaults.
I just dunno if it's as easy on my setup than on non-X+DE
On 05/05/2023 12:33, David wrote:
That sounds like what is documented here, with the solution at the end:
$ apt show dbus-user-session
I have tried quite similar steps, it seems the cause is not
dbus-user-session per se.
I have a laptop with Debian 11 bullseye and "minimalistic" KDE
of dbus
are running once you have started all your processes *and* logged
in to the DE session?
If it's only one user dbus, then logging out is taking that one away.
Perhaps this would be an interesting data point:
1 ps wwaux | grep dbus; keep the result
2 start all your programs; don't log i
On Fri 05 May 2023 at 13:59:37 (+0200), zithro wrote:
> On 05 May 2023 07:33, David wrote:
> > On Thu, 4 May 2023 at 19:07, zithro wrote:
> >
> > > this is a rather strange problem, I hope the title is explicit enough.
> >
> > Subject: Logging off an X s
On Sat 06 May 2023 at 09:57:30 (+0700), Max Nikulin wrote:
> On 05/05/2023 10:30, David Wright wrote:
> > On Fri 05 May 2023 at 09:13:04 (+0700), Max Nikulin wrote:
> > > On 05/05/2023 02:07, zithro wrote:
> > > > 2. using VNC or rdesktop, I then log on to X on the machine, do
> > > > some stuff,
On 05/05/2023 20:04, zithro wrote:
journalctl after GUI LOGOFF
I do not see obvious problems. What might be inspected more closely:
May 05 14:09:14 debzit systemd[711]: Stopping D-Bus User Message Bus...
^^^
If it is the bus
On 05/05/2023 10:30, David Wright wrote:
On Fri 05 May 2023 at 09:13:04 (+0700), Max Nikulin wrote:
On 05/05/2023 02:07, zithro wrote:
2. using VNC or rdesktop, I then log on to X on the machine, do
some stuff, then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH
On 05/05/2023 18:58, zithro wrote:
# loginctl list-sessions
SESSION UID USER SEAT TTY
111 1000 zithro
112 1000 zithro
141 1000 zithro pts/0
I do not see anything suspicious. I suppose, dbus-user-session
hypothesis by David may be more productive. Perhaps you may
On 05 May 2023 16:10, to...@tuxteam.de wrote:
I have now full logs of before/after GUI logon/logoff, I posted them in the
other post.
Will try to make sense of it with this lead ... after a needed break ^^
I saved that for a look during weekend, now I'm supposed to fix
an update of... forget
On Fri, May 05, 2023 at 03:26:12PM +0200, zithro wrote:
> On 05 May 2023 14:11, to...@tuxteam.de wrote:
[...]
> > No DE, just a window manager (fvwm2).
>
> Isn't that fluxbox ? That's the GUI I used on Slackware.
> Simple, lean, efficient !
No, quite a bit older. Fluxbox 2000-ish, fvwm
On 05 May 2023 14:11, to...@tuxteam.de wrote:
On Fri, May 05, 2023 at 01:58:55PM +0200, zithro wrote:
On 05 May 2023 06:32, to...@tuxteam.de wrote:
dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
no dbus (still, Debian buster, and X).
I'm on bullseye, I know how to
So, previous post was BEFORE logging in into GUI via VNC.
Now, I have outputs from after GUI LOGIN and after GUI LOGOFF.
I've removed the maximum of useless lines (audio, GUI apps, gvfs stuff,
etc), but tried to keep the most about systemd and dbus, as I'm clueless
about what you wanna read
On Fri, May 05, 2023 at 01:58:55PM +0200, zithro wrote:
> On 05 May 2023 06:32, to...@tuxteam.de wrote:
> > dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
> > no dbus (still, Debian buster, and X).
>
> I'm on bullseye, I know how to switch back to old init, but have no
On 05 May 2023 07:33, David wrote:
On Thu, 4 May 2023 at 19:07, zithro wrote:
this is a rather strange problem, I hope the title is explicit enough.
Subject: Logging off an X session closes all ssh -X connections
started previously from outside X
Yeah, I meant title==subject, I was hoping
On 05 May 2023 06:32, to...@tuxteam.de wrote:
dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
no dbus (still, Debian buster, and X).
I'm on bullseye, I know how to switch back to old init, but have no clue
about Dbus (kinda a Linux-GUI-with-systemd noob).
Which DE/DM
On 05 May 2023 05:30, David Wright wrote:
Isn't it this issue?
https://news.ycombinator.com/item?id=19023885
Looks like it, yes !
I'm afraid I can't replicate the problem, though, as I don't have
a "log off" button or menu entry. That might suggest that the
problem is in something I don't
r .slice
and .scope), "loginctl list-users", "loginctl list-sessions" on each step.
I'm a systemd noob, don't really know what you talking about ^^
But seems like the culprit.
Ran those commands (fucking auto pager though, way to break scrolling
... another fail)
So *before
On Thu, 4 May 2023 at 19:07, zithro wrote:
> this is a rather strange problem, I hope the title is explicit enough.
Subject: Logging off an X session closes all ssh -X connections
started previously from outside X
> Here is what happens chronologically :
>
> 1. I start various SSH
On Fri, May 05, 2023 at 09:13:04AM +0700, Max Nikulin wrote:
> On 05/05/2023 02:07, zithro wrote:
> > 2. using VNC or rdesktop, I then log on to X on the machine, do some
> > stuff, then hit "log off" from the desktop menu.
[...]
> Perhaps it may be related to user D-Bus sessions, however I
On Fri 05 May 2023 at 09:13:04 (+0700), Max Nikulin wrote:
> On 05/05/2023 02:07, zithro wrote:
> > 2. using VNC or rdesktop, I then log on to X on the machine, do
> > some stuff, then hit "log off" from the desktop menu.
> > Immediately, ALL the previous SSH connections started in step 1
> > get
On 05/05/2023 02:07, zithro wrote:
2. using VNC or rdesktop, I then log on to X on the machine, do some
stuff, then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH connections started in step 1 get
closed, hence all the shells and the GUI apps (firefox, etc) !
Have you
Hi all,
this is a rather strange problem, I hope the title is explicit enough.
Here is what happens chronologically :
1. I start various SSH connections to a host, some normal, some with X
forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP"
(like firejail firefox,
On Wed, Aug 25, 2021 at 07:24:32AM +0200, Geert Stappers wrote:
> On Tue, Aug 24, 2021 at 11:53:19PM +0200, Martijn van de Streek wrote:
> > Geert Stappers schreef op di 24-08-2021 om 22:53 [+0200]:
> > > Wat ik zoek is software die elk HTTP verzoek in bestand zet
> > > en daarna "200 OK"
On Tue, Aug 24, 2021 at 11:53:19PM +0200, Martijn van de Streek wrote:
> Geert Stappers schreef op di 24-08-2021 om 22:53 [+0200]:
> > Wat ik zoek is software die elk HTTP verzoek in bestand zet
> > en daarna "200 OK" antwoordt. De opgeslagen bestandjes
> > kan ik dan met elkaar vergelijken.
Geert Stappers schreef op di 24-08-2021 om 22:53 [+0200]:
> Wat ik zoek is software die elk HTTP verzoek in bestand zet
> en daarna "200 OK" antwoordt. De opgeslagen bestandjes
> kan ik dan met elkaar vergelijken. Bestandje bevat de HTTP headers
> en message body.
>
> Ik weet dat er een bos (een
Hoi,
Samenvatting:
Gezocht: "webserver" die verzoeken logt en ze met 200 OK beantwoordt.
Probleem waar ik een oplossing voor zoek
ga ik wat algemeen beschrijven
met achterliggend idee dat het niet TE specifiek is.
Een webservice kan ik succesvol aanspreken met curl in een bash
script. Het
On Sunday 14 March 2021 07:50:37 Andy Smith wrote:
> Hello,
>
> On Sat, Mar 13, 2021 at 05:10:42PM -0500, Gene Heskett wrote:
> > OPTIONS="--create-prefs --max-children 5 --helper-home-dir -s
> > ~/log/mail.log"
>
> spamd is a system service and it normally (initially) runs as root,
> so using a
Hello,
On Sat, Mar 13, 2021 at 05:10:42PM -0500, Gene Heskett wrote:
> OPTIONS="--create-prefs --max-children 5 --helper-home-dir -s ~/log/mail.log"
spamd is a system service and it normally (initially) runs as root,
so using a ~ there probably isn't what you want. Storing logs from
such a
On Saturday 13 March 2021 15:13:06 Greg Wooledge wrote:
> On Sat, Mar 13, 2021 at 02:52:05PM -0500, Gene Heskett wrote:
> > adding this "-s ~/gene/log/mail.log" inside the option "double quote
> > pair"> and issueing an /etc/init.d/spamassassin restart, didn't
> > bother it a bit.
> >
> > The way
On Sat, Mar 13, 2021 at 02:52:05PM -0500, Gene Heskett wrote:
> adding this "-s ~/gene/log/mail.log" inside the option "double quote
> pair"> and issueing an /etc/init.d/spamassassin restart, didn't bother
> it a bit.
>
> The way I read that manpage, it should have worked.
First: do you
On Saturday 13 March 2021 07:13:38 Andy Smith wrote:
> Hi Gene,
>
> On Fri, Mar 12, 2021 at 11:25:20PM -0500, Gene Heskett wrote:
> > What file, and where, do I edit to put that log someplace else?
>
> What's unclear or not working about the --syslog= option in "man
> spamd"?
>
>
le you do
> redirect this to.
I expect that a given, giving how verbose its logging is, over 10 lines
of drivel for every incoming message. I'll take a look there, thanks
Andy.
> Cheers,
> Andy
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap,
now anything about this but this guy says that he had a typo
> ( incorrect file name ) to logrotate caused syslog to fill up.
> https://serverfault.com/questions/842082/spamassassin-logging
>
> mick
Thats workiing fine here mick, thanks anyway.
Cheers, Gene Heskett
--
"There are
Hi Gene,
On Fri, Mar 12, 2021 at 11:25:20PM -0500, Gene Heskett wrote:
> What file, and where, do I edit to put that log someplace else?
What's unclear or not working about the --syslog= option in "man
spamd"?
https://manpages.debian.org/stretch/spamassassin/spamd.8p.en.html
You can change
edit to put that log someplace else?
System is updodate amd64 stretch.
Cheers, Gene Heskett
hello,
I don't know anything about this but this guy says that he had a typo (
incorrect file name ) to logrotate caused syslog to fill up.
https://serverfault.com/questions/842082/spamassassin-logging
Greetings all;
Somehow, spamd and friends have gotten the idea that they can spam the
syslog to the point where logrotate fires off at least daily, putting so
much trash in the syslog it worthless as a troubleshooting tool.
What file, and where, do I edit to put that log someplace else?
I have since rebooted to a shutdown and logging is back. I don't know
why simple reboots didn't solve the problem but
it's solved now.
--
Frank McCormick
Looking at dmesg I see a bunch of lines like this:
Stopping User Runtime Directory /run/user/118...
[ 55.241395] systemd[897]: user-runtime-dir@118.service: Failed to
connect stdout to the journal socket, ignoring: Connection refused
[ 55.249255] systemd[1]: run-user-118.mount: Succeeded.
On 2/4/20 11:30 AM, john doe wrote:
On 2/4/2020 4:56 PM, Frank McCormick wrote:
Noticed this morning that systemd is no longer logging boots on my machine.
There is a log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find
On 2/4/20 11:31 AM, Peter Ehlert wrote:
On 2/4/20 7:56 AM, Frank McCormick wrote:
Noticed this morning that systemd is no longer logging boots on my
machine.
There is a log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't
On 2/4/2020 4:56 PM, Frank McCormick wrote:
> Noticed this morning that systemd is no longer logging boots on my machine.
> There is a log in /var/log/journal, but it's from yesterday.
> I seem to recall a message here about a change in logging
> but I can't find it.
> I am run
On 2/4/20 7:56 AM, Frank McCormick wrote:
Noticed this morning that systemd is no longer logging boots on my
machine.
There is a log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully
Noticed this morning that systemd is no longer logging boots on my machine.
There is a log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully updated.
Can anyone help?
--
Frank McCormick
1 - 100 of 1073 matches
Mail list logo
