On 6/26/25 7:51 PM, Todd Zullinger wrote:
Samuel Sieb wrote:
On 6/26/25 3:22 PM, Robert Moskowitz wrote:
Try mailx for starters?
Or does it need more...
To get the terms right, you need an MDA or LDA, not an MTA. :-)
Something that can do local mail delivery and it seems that there are no
o
Samuel Sieb wrote:
> On 6/26/25 3:22 PM, Robert Moskowitz wrote:
>> Try mailx for starters?
>>
>> Or does it need more...
>
> To get the terms right, you need an MDA or LDA, not an MTA. :-)
> Something that can do local mail delivery and it seems that there are no
> options available other than t
users
wrote:
I want to get emails from my Fedora notebook for crontab
activities.
First figure out if your MTA is working, then you can figure out
what you want to *actually* send, whether Logwatch rolled-up
reports, or just the individual crontabs. There's a
Moskowitz via users
wrote:
I want to get emails from my Fedora notebook for crontab
activities.
First figure out if your MTA is working, then you can figure out
what you want to *actually* send, whether Logwatch rolled-up
reports, or just the individual crontabs
from my Fedora notebook for crontab
activities.
First figure out if your MTA is working, then you can figure out
what you want to *actually* send, whether Logwatch rolled-up
reports, or just the individual crontabs. There's almost certainly
a bunch of ways you can
On 6/26/25 3:15 PM, Robert Moskowitz via users wrote:
On 6/26/25 6:09 PM, Will McDonald wrote:
On Thu, 26 Jun 2025 at 23:05, Will McDonald wrote:
On Thu, 26 Jun 2025 at 22:50, Robert Moskowitz via users
wrote:
I want to get emails from my Fedora notebook for crontab
On 6/26/25 6:09 PM, Will McDonald wrote:
On Thu, 26 Jun 2025 at 23:05, Will McDonald wrote:
On Thu, 26 Jun 2025 at 22:50, Robert Moskowitz via users
wrote:
I want to get emails from my Fedora notebook for crontab
activities.
First figure out if your MTA is
On Thu, 26 Jun 2025 at 23:05, Will McDonald wrote:
> On Thu, 26 Jun 2025 at 22:50, Robert Moskowitz via users <
> users@lists.fedoraproject.org> wrote:
>
>> I want to get emails from my Fedora notebook for crontab activities.
>
>
> First figure out if your MTA is wo
t does rsync the files, but no report is
> emailed. Not local or other.
>
> The command seems to send its output to stdout.
>
Do your crontab file has a line as:
MAILTO=root
Ir where you want to send the email?
--
___
users mailing l
ws:
>
> 10 4* * * root/usr/sbin/shutdown
>
> And I get a daily email saying the system will shutdown in ~1min. Nice.
>
> I want to get emails from my Fedora notebook for crontab activities. I
> particular, I want to do a nightly rsync to an rsynd and get the result
I want to get emails from my Fedora notebook for crontab activities. I
particular, I want to do a nightly rsync to an rsynd and get the results
of this printed.
something like:
10 4 * * * rgm /usr/bin/time --password-file=pasw --verbose
/usr/bin/rsync -ah --stats /home/rgm/r/ rsync://rg
gt; [olivares@fedora user]$
> >
> > however, when I try to enable the service I get
> >
> > [olivares@fedora user]$ mcedit poweroff.service
> >
> > [olivares@fedora user]$ mcedit poweroff.timer
> >
> > [olivares@fedora user]$ systemctl --user enable poweroff
template units, the unit is meant to be enabled with some
instance name specified.
[olivares@fedora user]$
I changed 16:20:00 to 07:45:00 for testing purposes. But this is what I get.
I just want a service that powers off machine using this method. The crontab
method of shutting down the m
On Apr 8, 2022, at 08:43, olivares33561 via users
wrote:
>
> [olivares@fedora user]$ systemctl --user enable poweroff.service
If you are editing files in /etc/systemd/system, then take off the “--user” and
use sudo when activating the service. Never use sudo in a systemd Exec line
unless you
ser enable poweroff.service
> The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
> Alias= settings in the [Install] section, and DefaultInstance= for template
> units). This means they are not meant to be enabled using systemctl.
>
> Possible reasons for havin
ctory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled
> On 7 Apr 2022, at 21:22, olivares33561 via users
> wrote:
>
> Sent from ProtonMail, encrypted email based in Switzerland.
>
>
>
> I am getting closer.
>
> [olivares@fedora user]$ cat poweroff.service
> # /etc/systemd/system/poweroff.service
> [Unit]
> Description = Poweroff machine at 16
based in Switzerland.
--- Original Message ---
On Wednesday, April 6th, 2022 at 8:09 PM, Tim via users
users@lists.fedoraproject.org wrote:
On Tue, 2022-04-05 at 20:18 +, olivares33561 via users wrote:
How can I convert a crontab
#
[olivares@fedora Downloads]$ crontab -l
# min hour
Switzerland.
> >
> > --- Original Message ---
> > On Wednesday, April 6th, 2022 at 8:09 PM, Tim via users
> > users@lists.fedoraproject.org wrote:
> >
> > > On Tue, 2022-04-05 at 20:18 +, olivares33561 via users wrote:
> > >
> > > > How can I con
> On 6 Apr 2022, at 00:43, Ranjan Maitra wrote:
>
> So sorry to suddenly wake up on this thread, but is cron going away. I use it
> all the time, hourly for backups and nightly for updates.
>
> Many thanks,
> Ranjan
cron is not going away, but it's got a cryptic syntax and is, in my experien
022-04-05 at 20:18 +, olivares33561 via users wrote:
>>
>>> How can I convert a crontab
>>> #
>>> [olivares@fedora Downloads]$ crontab -l
>>> # min hour day-of-month month day-of-week command
>>> # 0-59 0-23 1-31 1-12 0-6 0=sun 1=mon
>>&g
a crontab
#
[olivares@fedora Downloads]$ crontab -l
# min hour day-of-month month day-of-week command
# 0-59 0-23 1-31 1-12 0-6 0=sun 1=mon
#50 04 * * 1-5 ~/.xalarm >/dev/null 2>&1
#50 04 * * 0,6 ~/.salarm >/dev/null 2>&1
#59 09 * * 0,6 ~/.salarm >/dev/null 2>&1
#00 0
Sent from ProtonMail, encrypted email based in Switzerland.
--- Original Message ---
On Wednesday, April 6th, 2022 at 8:09 PM, Tim via users
wrote:
> On Tue, 2022-04-05 at 20:18 +, olivares33561 via users wrote:
>
> > How can I convert a crontab
> > #
&g
On Tue, 2022-04-05 at 20:18 +, olivares33561 via users wrote:
> How can I convert a crontab
> #
> [olivares@fedora Downloads]$ crontab -l
> # min hour day-of-month month day-of-week command
> # 0-59 0-231-311-12 0-6 0=sun 1=mon
> #50 04 * * 1-5 ~/.xalarm >/d
On Apr 5, 2022, at 16:19, olivares33561 via users
wrote:
>
> [olivares@fedora Downloads]$ crontab -l
> […]
> [olivares@fedora Downloads]$ sudo systemctl list-timers
I noticed you put your crontab entries in your user crontab, but later looked
at system timers. You will want t
On 4/6/22 10:50, olivares33561 via users wrote:
I have a crontab file that I use to play some files about 3 minutes before bell
rings between classes. I had to install anacron with dnf command. I have seen
emails where some folks recommend systemd timers. How can I convert a crontab
25 16
2 22:02:35 +0100
> > To: olivares33561 olivares33...@protonmail.com, Community support for
> > Fedora users users@lists.fedoraproject.org
> > Reply-To: Community support for Fedora users users@lists.fedoraproject.org
> > Subject: Re: convert crontab jobs to systemd timers
>
On Tue Apr05'22 10:02:35PM, Barry wrote:
> From: Barry
> Date: Tue, 5 Apr 2022 22:02:35 +0100
> To: olivares33561 , Community support for
> Fedora users
> Reply-To: Community support for Fedora users
> Subject: Re: convert crontab jobs to systemd timers
>
>
> On 5 Apr 2022, at 21:19, olivares33561 via users
> wrote:
>
> Dear kind Fedora users,
>
> I have a crontab file that I use to play some files about 3 minutes before
> bell rings between classes. I had to install anacron with dnf command. I
> have seen emails wh
Dear kind Fedora users,
I have a crontab file that I use to play some files about 3 minutes before bell
rings between classes. I had to install anacron with dnf command. I have seen
emails where some folks recommend systemd timers. How can I convert a crontab
#
[olivares@fedora Downloads
On 2/18/22 00:22, Barry wrote:
On 18 Feb 2022, at 01:53, Mike Wright wrote:
There is a java app that writes directly to the pulseaudio MASTER channel at
full volume twice a day. I'm pretty sure the neighbors hear it. My idea is to
use crontab to run at 12:59 Monday-Friday. It wai
On Thu, 2022-02-17 at 17:39 -0800, Mike Wright wrote:
> There is a java app that writes directly to the pulseaudio MASTER
> channel at full volume twice a day. I'm pretty sure the neighbors
> hear it. My idea is to use crontab to run at 12:59 Monday-
> Friday. It waits 59 s
> On 18 Feb 2022, at 01:53, Mike Wright wrote:
>
> Hi all,
>
> There is a java app that writes directly to the pulseaudio MASTER channel at
> full volume twice a day. I'm pretty sure the neighbors hear it. My idea is
> to use crontab to run at 12:59 Monday-Fr
On Thu, 17 Feb 2022 17:39:18 -0800
Mike Wright wrote:
> Anybody explain why this doesn't do what I intend?
Odds are good something in your login environment is required.
DBUS_SESSION_BUS_ADDRESS is one good candidate. Lots of linux
tools don't directly do anything, but instead connect to DBUS
to
Hi all,
There is a java app that writes directly to the pulseaudio MASTER
channel at full volume twice a day. I'm pretty sure the neighbors hear
it. My idea is to use crontab to run at 12:59 Monday-Friday. It waits
59 seconds, mutes the audio, waits 6 more seconds and unmutes the
On 11/16/21 2:27 PM, Joe Zeff wrote:
On 11/16/21 2:46 PM, Peter Boy wrote:
Yes indeed, you know that (and I, too). But someone, who is new to Linux? Or to
computers in general?
If I were helping a newcomer to Linux, and pointed them toward nano, I'd
include explaining what ^ means in that c
On Tue, 16 Nov 2021 14:27:49 -0700
Joe Zeff wrote:
> What I don't understand is why so many people think that
> vi/vim is so wonderful unless it's justifying the amount of work it took
> them to learn it.
Bingo! :-). Why would anyone think an editor with separate "modes"
for moving the cursor a
On 11/16/21 2:46 PM, Peter Boy wrote:
Yes indeed, you know that (and I, too). But someone, who is new to Linux? Or to
computers in general?
If I were helping a newcomer to Linux, and pointed them toward nano, I'd
include explaining what ^ means in that context. How much explaining do
you n
On 11/16/21 2:40 PM, Robert Moskowitz wrote:
If I need more that vi, then I use geany. We ARE using a gui interface
on most systems and often gui remote into servers.
Yes, of course you should use your GUI editor of choice if it's
available. That's why I kept talking about emergency edits
> Am 16.11.2021 um 22:27 schrieb Joe Zeff :
>
> On 11/16/21 2:08 PM, Peter Boy wrote:
>> You might see it yourself: K for cut, very intuitive , ^ for „Press
>> key, even more intuitive.
>
> Back it the Old Days when nano was first developed, the standard way to
> signify use of the control k
On 11/16/21 16:27, Joe Zeff wrote:
On 11/16/21 2:08 PM, Peter Boy wrote:
You might see it yourself: K for cut, very intuitive , ^ for „Press
key, even more intuitive.
Back it the Old Days when nano was first developed, the standard way
to signify use of the control key was ^, which is st
On 11/16/21 2:08 PM, Peter Boy wrote:
You might see it yourself: K for cut, very intuitive , ^ for „Press key,
even more intuitive.
Back it the Old Days when nano was first developed, the standard way to
signify use of the control key was ^, which is still used in the various
terminal prog
> Am 16.11.2021 um 22:02 schrieb Robert Moskowitz :
>
>
>
> On 11/16/21 15:01, Samuel Sieb wrote:
>> On 11/16/21 10:18, Robert Moskowitz wrote:
>>> F35 change from F32; may have occurred earlier.
>>>
>>> VI was sooo easy to use.
>>>
>>> Now I have to learn nano?
>>
>> I was using a debian o
> Am 16.11.2021 um 21:10 schrieb Joe Zeff :
>
> On 11/16/21 12:39 PM, Peter Boy wrote:
>> Maybe, but you lose a lot of very powerful functionality. And instead you
>> are supposed to decipher (and memorize) cryptic character combinations that
>> desperately try to imitate a graphical interface
On 11/16/21 15:01, Samuel Sieb wrote:
On 11/16/21 10:18, Robert Moskowitz wrote:
F35 change from F32; may have occurred earlier.
VI was sooo easy to use.
Now I have to learn nano?
I was using a debian or Ubuntu system and I ran "visudo". It took me
a few moments to figure out why I could
On 11/16/21 12:39 PM, Peter Boy wrote:
Maybe, but you lose a lot of very powerful functionality. And instead you are
supposed to decipher (and memorize) cryptic character combinations that
desperately try to imitate a graphical interface.
No. All commands in nano are single strokes, using th
On 11/16/21 10:18, Robert Moskowitz wrote:
F35 change from F32; may have occurred earlier.
VI was sooo easy to use.
Now I have to learn nano?
I was using a debian or Ubuntu system and I ran "visudo". It took me a
few moments to figure out why I couldn't get out of it. I laughed at
the iro
> Am 16.11.2021 um 20:27 schrieb Joe Zeff :
>
> On 11/16/21 11:18 AM, Robert Moskowitz wrote:
>> Now I have to learn nano?
>> Old timer sheesh.
>
> Nano is actually easy to use. The most important commands are at the bottom
> of the screen, including the one to bring up the complete list. No
On 11/16/21 10:18, Robert Moskowitz wrote:
F35 change from F32; may have occurred earlier.
Change in Fedora 33: https://fedoraproject.org/wiki/Changes/UseNanoByDefault
VI was sooo easy to use. Now I have to learn nano?
No, now new users don't have to learn to use vim. You can set what
On 11/16/21 11:18 AM, Robert Moskowitz wrote:
Now I have to learn nano?
Old timer sheesh.
Nano is actually easy to use. The most important commands are at the
bottom of the screen, including the one to bring up the complete list.
No need to memorize anything.
_
> Am 16.11.2021 um 19:56 schrieb Patrick O'Callaghan :
>
> On Tue, 2021-11-16 at 12:30 -0600, Ron Flory wrote:
>> man crontab says VISUAL or EDITOR env vars may affect this. sure
>> hope
>> the default isn't nano now...
>
> IIRC the default ha
On 11/16/21 13:56, Patrick O'Callaghan wrote:
On Tue, 2021-11-16 at 12:30 -0600, Ron Flory wrote:
man crontab says VISUAL or EDITOR env vars may affect this. sure
hope
the default isn't nano now...
IIRC the default has been nano since at least F34 and possibly earlier.
I don
On Tue, 2021-11-16 at 12:30 -0600, Ron Flory wrote:
> man crontab says VISUAL or EDITOR env vars may affect this. sure
> hope
> the default isn't nano now...
IIRC the default has been nano since at least F34 and possibly earlier.
I don't l
man crontab says VISUAL or EDITOR env vars may affect this. sure hope
the default isn't nano now...
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Co
On Tue, Nov 16, 2021 at 11:19 AM Robert Moskowitz wrote:
> F35 change from F32; may have occurred earlier.
>
> VI was sooo easy to use.
>
> Now I have to learn nano?
>
> Old timer sheesh.
Uninstall the nano-default-editor package. Install the
vim-default-editor package. Log out and log back in.
F35 change from F32; may have occurred earlier.
VI was sooo easy to use.
Now I have to learn nano?
Old timer sheesh.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Co
On 2020-05-11 21:45, Robert Moskowitz wrote:
>
>
> On 5/11/20 9:28 AM, Ed Greshko wrote:
>> On 2020-05-11 20:39, Robert Moskowitz wrote:
>>> And now you are paying the memory, cpu, etc. cost of having postfix running
>> Oh, well, I suppose I've never seen an idle postfix take up any noticeable
>>
On 5/11/20 9:28 AM, Ed Greshko wrote:
On 2020-05-11 20:39, Robert Moskowitz wrote:
And now you are paying the memory, cpu, etc. cost of having postfix running
Oh, well, I suppose I've never seen an idle postfix take up any noticeable CPU
time or memory
on any of my systems.
How can it not
On 2020-05-11 20:39, Robert Moskowitz wrote:
> And now you are paying the memory, cpu, etc. cost of having postfix running
Oh, well, I suppose I've never seen an idle postfix take up any noticeable CPU
time or memory
on any of my systems.
--
The key to getting good answers is to ask good quest
On 5/10/20 11:39 PM, Ed Greshko wrote:
On 2020-05-07 06:00, Robert Moskowitz wrote:
I know I can edit the user crontab with:
crontab -e
and display it with
crontab -l
But where is it? I don't see anything like ~/.crontab
Secondly, and more importantly, is getting a email from the
On 2020-05-07 06:00, Robert Moskowitz wrote:
> I know I can edit the user crontab with:
>
> crontab -e
>
> and display it with
>
> crontab -l
>
> But where is it? I don't see anything like ~/.crontab
>
> Secondly, and more importantly, is getting a email f
On 5/10/20 6:51 PM, Cameron Simpson wrote:
On 10May2020 13:36, Robert Moskowitz wrote:
It is entirely true. The collapsing happens when you _use_ the values:
# all safe and reliable
$ a=$( date +'%a %b %d %T %Y')
$ b=$( date +'%a %b %d %T Y')
$ c=$b
# unquoted use
$ ec
On 10May2020 13:36, Robert Moskowitz wrote:
It is entirely true. The collapsing happens when you _use_ the values:
# all safe and reliable
$ a=$( date +'%a %b %d %T %Y')
$ b=$( date +'%a %b %d %T Y')
$ c=$b
# unquoted use
$ echo $a
Sat May 09 14:37:07 2020
$ echo $b
On 5/9/20 12:41 AM, Cameron Simpson wrote:
On 08May2020 20:32, Samuel Sieb wrote:
On 5/8/20 4:32 PM, Cameron Simpson wrote:
On 08May2020 11:15, Robert Moskowitz wrote:
I added inserting a Date: line and switched to using sed:
local]# cat mycron
#!/bin/sh
currentDate="$(date +'%a %b %d %T
On 5/8/20 9:41 PM, Cameron Simpson wrote:
On 08May2020 20:32, Samuel Sieb wrote:
On 5/8/20 4:32 PM, Cameron Simpson wrote:
On 08May2020 11:15, Robert Moskowitz wrote:
I added inserting a Date: line and switched to using sed:
local]# cat mycron
#!/bin/sh
currentDate="$(date +'%a %b %d %T %Y
On 08May2020 20:32, Samuel Sieb wrote:
On 5/8/20 4:32 PM, Cameron Simpson wrote:
On 08May2020 11:15, Robert Moskowitz wrote:
I added inserting a Date: line and switched to using sed:
local]# cat mycron
#!/bin/sh
currentDate="$(date +'%a %b %d %T %Y')"
You don't need the double quotes. The
On 5/8/20 4:32 PM, Cameron Simpson wrote:
On 08May2020 11:15, Robert Moskowitz wrote:
I added inserting a Date: line and switched to using sed:
local]# cat mycron
#!/bin/sh
currentDate="$(date +'%a %b %d %T %Y')"
You don't need the double quotes. The shell parser recognises the
assignment
On 08May2020 11:15, Robert Moskowitz wrote:
I added inserting a Date: line and switched to using sed:
local]# cat mycron
#!/bin/sh
currentDate="$(date +'%a %b %d %T %Y')"
You don't need the double quotes. The shell parser recognises the
assignment statement _before_ breaking things on white
add it to
the crontab output.
Yes, it's a requirement of the format. That's why there's an "echo"
after "cat". :)
Oops. That is right. And I need to change this to do a sed to insert
a Date: line in the right place...
"The right place"?
On 08May2020 06:56, Robert Moskowitz wrote:
On 5/8/20 2:08 AM, Cameron Simpson wrote:
You _do_ need to ensure the message at least ends with a newline, of
the From_ won't be at the start of a line. So the previously posted
script ensures that with the "echo" in "( cat; echo )". If you want to
On 5/8/20 11:08 AM, Robert Moskowitz wrote:
On 5/8/20 1:58 PM, Mike Wright wrote:
There's a tiny MDA called femtomail that delivers into a Maildir.
Well first I need mbox, not maildir format.
mutt can read Maildir as well. Maildir is a much better mail storage
method than mbox.
Provide i
On 5/8/20 2:01 PM, Samuel Sieb wrote:
On 5/8/20 10:58 AM, Mike Wright wrote:
On 5/8/20 9:55 AM, Robert Moskowitz wrote:
On 5/8/20 12:39 PM, Tim via users wrote:
On Fri, 2020-05-08 at 06:56 -0400, Robert Moskowitz wrote:
Plus I have always thought of this as a deficiency in cron on a
works
On 5/8/20 1:58 PM, Mike Wright wrote:
On 5/8/20 9:55 AM, Robert Moskowitz wrote:
On 5/8/20 12:39 PM, Tim via users wrote:
On Fri, 2020-05-08 at 06:56 -0400, Robert Moskowitz wrote:
Plus I have always thought of this as a deficiency in cron on a
workstation. Cron should work (report in thi
On 5/8/20 10:58 AM, Mike Wright wrote:
On 5/8/20 9:55 AM, Robert Moskowitz wrote:
On 5/8/20 12:39 PM, Tim via users wrote:
On Fri, 2020-05-08 at 06:56 -0400, Robert Moskowitz wrote:
Plus I have always thought of this as a deficiency in cron on a
workstation. Cron should work (report in this
On 5/8/20 9:55 AM, Robert Moskowitz wrote:
On 5/8/20 12:39 PM, Tim via users wrote:
On Fri, 2020-05-08 at 06:56 -0400, Robert Moskowitz wrote:
Plus I have always thought of this as a deficiency in cron on a
workstation. Cron should work (report in this case) properly
without needing somethin
On 5/8/20 12:39 PM, Tim via users wrote:
On Fri, 2020-05-08 at 06:56 -0400, Robert Moskowitz wrote:
Plus I have always thought of this as a deficiency in cron on a
workstation. Cron should work (report in this case) properly
without needing something else (MTA) installed.
Does it though? Th
On Fri, 2020-05-08 at 06:56 -0400, Robert Moskowitz wrote:
> Plus I have always thought of this as a deficiency in cron on a
> workstation. Cron should work (report in this case) properly
> without needing something else (MTA) installed.
Does it though? There's always /var/log/cron. Or that ot
it may be necessary to add it to
the crontab output.
Yes, it's a requirement of the format. That's why there's an "echo" after
"cat". :)
except cat is not guarenteed to EOF after a newline.
New script.
I added inserting a Date: line and switched to using se
necessary to add it to
> > the crontab output.
>
>
> Yes, it's a requirement of the format. That's why there's an "echo" after
> "cat". :)
except cat is not guarenteed to EOF after a newline.
--
Jon H. LaBadie jo...@jg
On 5/8/20 6:04 AM, Tim via users wrote:
On Fri, 2020-05-08 at 01:44 -0400, Jon LaBadie wrote:
In my mail files each message is followed by a blank line
before the next "From_" line. Is that a requirement of
mbox format? If so, it may be necessary to add it to
the crontab output.
Hi.
On Fri, 08 May 2020 06:56:58 -0400 Robert Moskowitz wrote:
> On 5/8/20 2:08 AM, Cameron Simpson wrote:
>> You _do_ need to ensure the message at least ends with a newline, of
>> the From_ won't be at the start of a line. So the previously posted
>> script ensures that with the "echo" in "(
On 5/8/20 2:24 AM, Gordon Messmer wrote:
On 5/7/20 10:44 PM, Jon LaBadie wrote:
In my mail files each message is followed by a blank line
before the next "From_" line. Is that a requirement of
mbox format? If so, it may be necessary to add it to
the crontab output.
Y
uot;From_" line. Is that a requirement of
mbox format? If so, it may be necessary to add it to
the crontab output.
Kinda. Depends on the thing parsing the mbox file. To avoid misparsing
message body lines which themselves commance with "From " some things
only consider a From_ li
On 5/8/20 1:16 AM, Tim via users wrote:
On Thu, 2020-05-07 at 09:09 -0500, Roger Heflin wrote:
In general if you set up the cronjobs to redirect stdout and stderr
to a file then typically there is nothing to email.
Just thinking out loud: If your scripts generate their own logs, you
see the
On Fri, 2020-05-08 at 01:44 -0400, Jon LaBadie wrote:
> In my mail files each message is followed by a blank line
> before the next "From_" line. Is that a requirement of
> mbox format? If so, it may be necessary to add it to
> the crontab output.
It's how mbox works,
On 5/7/20 10:44 PM, Jon LaBadie wrote:
In my mail files each message is followed by a blank line
before the next "From_" line. Is that a requirement of
mbox format? If so, it may be necessary to add it to
the crontab output.
Yes, it's a requirement of the format. That
else it prevents filename expansion happening to the value of
$currentDate. (Not that that will happen with the date format chosen, but
again, as a general practice in scripting.)
In my mail files each message is followed by a blank line
before the next "From_" line. Is that a requirement of
m
gt;
> If nothing else it prevents filename expansion happening to the value of
> $currentDate. (Not that that will happen with the date format chosen, but
> again, as a general practice in scripting.)
>
In my mail files each message is followed by a blank line
before the next "
On Thu, 2020-05-07 at 09:09 -0500, Roger Heflin wrote:
> In general if you set up the cronjobs to redirect stdout and stderr
> to a file then typically there is nothing to email.
Just thinking out loud: If your scripts generate their own logs, you
see the results of your scripts. But if cron gen
On 07May2020 15:01, Robert Moskowitz wrote:
/ustr/sbin/mycron:
#!/bin/sh
currentDate="$(date +'%a %b %d %T %Y')"
echo "From cron@localhost "$currentDate >> /var/spool/mail/$USER
Put $currentDate inside the quotes. With echo it is less of an issue,
but for many other commands you should exer
On 07May2020 12:43, Joe Zeff wrote:
On 05/07/2020 08:04 AM, Robert Moskowitz wrote:
So all I need is a script at /usr/bin/mycron
Actually, you can put it wherever you want, including ~/bin, as long
as you give the complete path. /usr/bin may be the best place, but
it's not the only place.
. "rpm -qf /usr/sbin/sendmail" used
to be the go, not sure of the matching dnf or yum incantation.
I looked at man crontab.5 and did not see a way to specify the mail
command to run for the cron output.
There isn't. It uses the "system mail", use _is_ /usr/sbin/send
On 07May2020 09:25, Robert Moskowitz wrote:
The bottom of that manual entry describes the "mta" setting, and
says that esmtp relies on a local MTA for local delivery (addresses
without an "@"). So you'll need something additional anyway. May as
well go straight to a proper MTA.
And then, to
d
# Settings for the CRON daemon.
# CRONDARGS= : any extra command-line startup arguments for crond
CRONDARGS= -m "/usr/sbin/mycron"
And restarted crond
Next I changed my crontab with:
15 * * * * ls /home/rgm
I know have mail waiting in /var/spool/mail/rgm, but mutt can't
proces
On 05/07/2020 08:04 AM, Robert Moskowitz wrote:
So all I need is a script at /usr/bin/mycron
Actually, you can put it wherever you want, including ~/bin, as long as
you give the complete path. /usr/bin may be the best place, but it's
not the only place. Just a thought.
___
crond
# Settings for the CRON daemon.
# CRONDARGS= : any extra command-line startup arguments for crond
CRONDARGS= -m "/usr/sbin/mycron"
And restarted crond
Next I changed my crontab with:
15 * * * * ls /home/rgm
I know have mail waiting in /var/spool/mail/rgm, but mutt can't
pr
On 5/7/20 1:24 PM, Alexander Dalloz wrote:
Am 07.05.2020 um 02:11 schrieb Robert Moskowitz:
Cameron,
Oh I have done a lot with postfix:
http://www.htt-consult.com/Centos7-mailserver.html
Showing a broken / incomplete submission and submissions setup in
master.cf of Postfix.
Notice it sa
Am 07.05.2020 um 02:11 schrieb Robert Moskowitz:
Cameron,
Oh I have done a lot with postfix:
http://www.htt-consult.com/Centos7-mailserver.html
Showing a broken / incomplete submission and submissions setup in
master.cf of Postfix.
Alexander
___
ed crond
Next I changed my crontab with:
15 * * * * ls /home/rgm
I know have mail waiting in /var/spool/mail/rgm, but mutt can't process
it. So I am missing something in the format of mail in
/var/spool/mail. Can someone point me to the proper format?
What I have there from the cron
In general if you set up the cronjobs to redirect stdout and stderr to
a file then typically there is nothing to email.
Often if you have only a few systems this is easier to use.
On Thu, May 7, 2020 at 8:29 AM Robert Moskowitz wrote:
>
>
>
> On 5/7/20 7:48 AM, Robert Moskowitz wrote:
> >
> >
>
1 - 100 of 223 matches
Mail list logo