>> On Thu, 19 Sep 2024, fxkl4...@protonmail.com wrote:
> in my iptables i havetcp LOG flags 0 level 4 prefix "REJECT: "
> this does what i want but how to direct the logging
> it gets written to multiple file in /var/log
> syslog, messages, kern, debug
> can i restrict this to a single file
On Thu, 19 Sep 2024, fxkl4...@protonmail.com wrote:
in my iptables i havetcp LOG flags 0 level 4 prefix "REJECT: "
this does what i want but how to direct the logging
it gets written to multiple file in /var/log
syslog, messages, kern, debug
can i restrict this to a single file
*.*;auth,a
Hi,
On Thu, Sep 19, 2024 at 02:35:24PM +, fxkl4...@protonmail.com wrote:
> in my iptables i havetcp LOG flags 0 level 4 prefix "REJECT: "
> this does what i want but how to direct the logging
> it gets written to multiple file in /var/log
> syslog, messages, kern, debug
> can i restrict th
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 moment
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 com
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 conne
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 inclu
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: Conne
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 - ther
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
terminal.
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 w
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 render
On 8/8/23 00:51, to...@tuxteam.de wrote:
On Mon, Aug 07, 2023 at 05:32:03PM -0400, gene heskett wrote:
[...]
Ohhhkaaay, but why then do I get a message if looking at the journal as user
1000, that the user must be a member of the adm group to see all the log,
...unless you use sudo.
AND ad
On 8/7/23 23:17, Greg Wooledge wrote:
On Mon, Aug 07, 2023 at 10:57:41PM -0400, gene heskett wrote:
On 8/7/23 22:08, Max Nikulin wrote:
I have no idea which way you may break journald and why you have not
just installed rsyslog yet if you trust it more and have a hope to find
there more info th
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:
> > > > >
On Mon, Aug 07, 2023 at 05:32:03PM -0400, gene heskett wrote:
[...]
> Ohhhkaaay, but why then do I get a message if looking at the journal as user
> 1000, that the user must be a member of the adm group to see all the log,
...unless you use sudo.
> AND adding me to the adm group doesn't change
On Mon, Aug 07, 2023 at 10:57:41PM -0400, gene heskett wrote:
> On 8/7/23 22:08, Max Nikulin wrote:
> > I have no idea which way you may break journald and why you have not
> > just installed rsyslog yet if you trust it more and have a hope to find
> > there more info than in journalctl output. jou
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 pe
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 option
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 unlimited.
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 dram
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 click
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 butt
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 r
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 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 raid10 lock, stock and bar
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 wrote:
[...]
In some cases, the release notes actually do tell you how to get back
to no
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."
N
On 06/08/2023 02:03, Joe wrote:
I use 'tail -f ' at least
once a week
journalctl -f
Hello,
On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> On Sat, 5 Aug 2023 15:09:41 +
> Andy Smith wrote:
> > For those of us who do care, installing rsyslog takes seconds.
> > Disabling the systemd journal (if you want to)_ takes another few
> > seconds. This email took longer.
>
> Bu
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 just
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 deeply about logging it's gener
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 using journal
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 understand
* 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 li
On 8/5/23 14:56, Carl Fink wrote:
On 8/5/23 02:54, Michel Verdier wrote:
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
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 i
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. I'm more interested in
> *using* my
> computer than learning whole new paradigms about, say, logging
On Sat 05 Aug 2023 at 08:56:36 -0400, Carl Fink wrote:
> On 8/5/23 02:54, Michel Verdier wrote:
> > 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.
> > >
> > > Wel
On 8/5/23 02:54, Michel Verdier wrote:
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 journa
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 /var/log
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/very little logging
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 undocumen
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:
https
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 sc
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 scr
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 ha
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 sshd[14246
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 fir
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). Ther
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.
But it won't
On 06 May 2023 06:45, David Wright wrote:
*I login to VC1 and startx for an Xserver*
I think that's why you don't have my problem, your user is always logged
in, even when you close X.
Is the greeter just deferring the ssh command until you login?
Nope, they work without X "direct" login.
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
(origi
On Sat, May 06, 2023 at 10:24:52AM +0700, Max Nikulin wrote:
> 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...
>
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 session closes all ssh -X connections
> > 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, t
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 connecti
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 prev
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 it
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 199-smal
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 sw
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 cl
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 y
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
On 05 May 2023 04:13, 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
closed, hence all the shells and
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 connections t
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 would
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 c
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 i
On Thursday 06 June 2019 08:27:28 am Greg Wooledge wrote:
> On Wed, Jun 05, 2019 at 10:25:07PM -0400, Gene Heskett wrote:
> > So syslog is growing rapidly and gets rotated in just a day or so,
> > and that means a "tail -fn xxx" watching it is stuck looking at the
> > old file,
>
> That's what tai
On Wed, Jun 05, 2019 at 10:25:07PM -0400, Gene Heskett wrote:
> So syslog is growing rapidly and gets rotated in just a day or so, and
> that means a "tail -fn xxx" watching it is stuck looking at the old
> file,
That's what tail -F (capital F) is for.
On Wed 05 Jun 2019 at 22:25:07 (-0400), Gene Heskett wrote:
>
> Since upgrading to stretch, my syslog is being spammed by freshclam,
> clamav, and spamd. These has their own logs in wheezy, so syslog was how
> I kept track of the hardware.
>
> So syslog is growing rapidly and gets rotated in ju
On Wednesday, 23 April 2014 19:10:11 -0700,
ty wrote:
> A ambiguous redirect sounds like the variable is empty.
> To demonstrate:
> a=" "
> echo hello > $a
> bash: $a: ambiguous redirect
> Make sure ${VPN_APP_LOG[$N]}is not being set inside the sub-proccess ( )
> and is a valid variable.
Hello, T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/23/2014 05:34 AM, Daniel Bareiro wrote:
> Hi, Ty.
>
> On Tuesday, 22 April 2014 22:34:29 -0700,
> ty wrote:
>
>> Perhaps this will work?
>> #!/bin/bash
>> echo 1 #Non Logged Commands
>> echo 2
>> echo 3
>> echo 4
>> (
>> set -x
>> echo 5 #Logge
Forwarded Message
From: Ralf Mardorf
To: debian-user lists.debian.org
Subject: Re: Logging of commands in a bash script to a file
Date: Wed, 23 Apr 2014 20:33:14 +0200
Mailer: Evolution 3.10.4
PPS:
If you're using #!/bin/sh for Linux you at least should take care that
On Wed, 2014-04-23 at 19:42 +0200, Ralf Mardorf wrote:
> On Wed, 2014-04-23 at 13:10 -0400, Patrick Chkoreff wrote:
> > Good, but I think you can avoid the positional params by just using $@
>
> If you use $1 $2 $3 ..., then you at least should use a loop, by taking
> care of the count of paramete
On Wed, 2014-04-23 at 13:10 -0400, Patrick Chkoreff wrote:
> Good, but I think you can avoid the positional params by just using $@
If you use $1 $2 $3 ..., then you at least should use a loop, by taking
care of the count of parameters, using $# which does show how much
parameters are used.
I usu
Steve Litt wrote, On 04/23/2014 12:07 PM:
> On Tue, 22 Apr 2014 19:06:41 -0300
> Daniel Bareiro wrote:
>
>>
>> Hi all!
>>
>> I'm writing a bash script that runs several routing commands. I would
>> like these commands, on a part of the script, plus run, are saved to a
>> log file.
>>
>> I guess m
Daniel Bareiro wrote:
> What I meant is to have a group of commands in a script that, in
> addition to being executed, I want these commands are stored in a log.
LOG=/var/log/...logfile...
ExecAndLog()
{
# Season with date, PID, user, etc., to taste
echo "$*" >>"$LOG"
On Tue, 22 Apr 2014 19:06:41 -0300
Daniel Bareiro wrote:
>
> Hi all!
>
> I'm writing a bash script that runs several routing commands. I would
> like these commands, on a part of the script, plus run, are saved to a
> log file.
>
> I guess maybe it could be done by putting the commands in a va
Hi, Ty.
On Tuesday, 22 April 2014 22:34:29 -0700,
ty wrote:
> Perhaps this will work?
> #!/bin/bash
> echo 1 #Non Logged Commands
> echo 2
> echo 3
> echo 4
> (
> set -x
> echo 5 #Logged Commands
> echo 6
> echo 7
> echo 8
> ) 2>> log
> echo 9 #Non Logged Commands
> echo 10
>
> Output of termina
On 23/04/14 08:06, Daniel Bareiro wrote:
>
> Hi all!
>
> I'm writing a bash script that runs several routing commands. I would
> like these commands, on a part of the script, plus run, are saved to a
> log file.
>
> I guess maybe it could be done by putting the commands in a variable and
> then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Perhaps this will work?
#!/bin/bash
echo 1 #Non Logged Commands
echo 2
echo 3
echo 4
(
set -x
echo 5 #Logged Commands
echo 6
echo 7
echo 8
) 2>> log
echo 9 #Non Logged Commands
echo 10
Output of terminal:
1
2
3
4
5
6
7
8
9
10
Output of log:
++ echo
On Tue, Apr 22, 2014 at 07:06:41PM -0300, Daniel Bareiro wrote:
>
> Hi all!
>
> I'm writing a bash script that runs several routing commands. I would
> like these commands, on a part of the script, plus run, are saved to a
> log file.
>
If you have bsdutils installed have a look at the "logger"
On Wed, Apr 23, 2014 at 10:46 AM, Daniel Bareiro wrote:
> I want to send the commands itself to a file instead of the output
> generated by the commands.
>
> In fact, in the four cases mentioned above, if these are executed
> successfully, it does not produce any output.
If you're okay with the c
Hi, Adam.
On Tuesday, 22 April 2014 18:40:19 -0500,
K. Adam Wolfe wrote:
> Use redirects:
>
> $IP route add ${VPN_NET[$N]} dev ${VPN_IFACE[$N]} src ${VPN_IP[$N]} table $N
> >> /some/log/file
> $IP route add default via ${VPN_GW[$N]} table $N >> /some/log/file
>
>
> $IP route add ${VPN_NET[$N]
exec > filename redefines standard out as filename
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87a9bcgbng@aptiva.optonline.net
Use redirects:
$IP route add ${VPN_NET[$N]} dev ${VPN_IFACE[$N]} src ${VPN_IP[$N]} table $N >>
/some/log/file
$IP route add default via ${VPN_GW[$N]} table $N >> /some/log/file
$IP route add ${VPN_NET[$N]} dev ${VPN_IFACE[$N]} src ${VPN_IP[$N]} >>
/some/log/file
$IP rule add from ${VPN_IP[$N
Hi, Tom.
On Tuesday, 22 April 2014 23:18:30 +0100,
Tom Furie wrote:
> > I'm writing a bash script that runs several routing commands. I would
> > like these commands, on a part of the script, plus run, are saved to a
> > log file.
> I'm having trouble processing this paragraph. Are you saying th
On Wed, Apr 23, 2014 at 8:06 AM, Daniel Bareiro wrote:
>
> I'm writing a bash script that runs several routing commands. I would
> like these commands, on a part of the script, plus run, are saved to a
> log file.
>
> I guess maybe it could be done by putting the commands in a variable and
> then
1 - 100 of 351 matches
Mail list logo
