On 04/19/2013 01:10 PM, Michael Schwendt wrote:
I've been very busy recently and only had a brief look at some procmail
filtered folders, where the question you had asked was still unanswered.
So, I replied.
Oh. OK, asked and answered. And, I'd like to mention that I didn't
mean to imply tha
On Wed, 17 Apr 2013 10:49:45 -0700, Joe Zeff wrote:
> What I don't understand is why you're bothering with this three weeks
> later. It's just like over at fedoraforum.org where somebody made a
> foolish suggestion today about an issue I'd marked as [SOLVED] six days
> ago, with a complete exp
On 04/17/2013 02:57 AM, Michael Schwendt wrote:
I'm not sure I understand the question, because above example already
shows how the $EDITOR environment variable is set to nano for crontab
to pick it up.
What I don't understand is why you're bothering with this three weeks
later. It's just lik
On Sun, 24 Mar 2013 10:02:31 -0700, Joe Zeff wrote:
> On 03/24/2013 03:12 AM, Michael Schwendt wrote:
> > Verify that $EDITOR is set actually. $EDITOR is evaluated here just fine.
> > And
> >
> >$ echo $EDITOR
> >emacs
> >$ EDITOR=nano crontab -e
> >
> >crontab: no changes made
On Sat, 23 Mar 2013 23:12:44 -0700, Joe Zeff wrote:
> On 03/23/2013 10:47 PM, Garry T. Williams wrote:
>> On 3-23-13 15:21:37 Joe Zeff wrote:
>>> [joe@khorlia ~]$ echo $EDITOR nano
>>
>> This is your problem. You're missing a full path and crontab(1)
>> requires it.
>>
>>
> If so, why does this w
Am 24.03.2013 18:03, schrieb Joe Zeff:
> On 03/24/2013 03:19 AM, Michael Schwendt wrote:
>> I'm also not surprised, but I've asked about /var/log/cron early.
>
> Yes, and I've reported before that all it showed was my examining (and
> editing) crontab
if someone aks for a log file he asks for
On 03/24/2013 03:19 AM, Michael Schwendt wrote:
I'm also not surprised, but I've asked about /var/log/cron early.
Yes, and I've reported before that all it showed was my examining (and
editing) crontab.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription
On 03/24/2013 03:12 AM, Michael Schwendt wrote:
Verify that $EDITOR is set actually. $EDITOR is evaluated here just fine.
And
$ echo $EDITOR
emacs
$ EDITOR=nano crontab -e
crontab: no changes made to crontab
As I'm sure I've written before, I've checked this with echo, and
the
On Sat, 23 Mar 2013 18:00:22 -0700, Joe Zeff wrote:
> On 03/23/2013 04:36 PM, Reindl Harald wrote:
> > and what says "ps aux | grep cron"?
>
> Neither cron nor anacron is listed. Somehow, I'm not surprised.
I'm also not surprised, but I've asked about /var/log/cron early.
It tells much about wh
On Sat, 23 Mar 2013 14:43:44 -0700, Joe Zeff wrote:
> Somebody suggested adding something new to crontab and seeing if it
> works. I tried it. Alas, even though I have both EDITOR and VISUAL set
> in both .bashrc and .bash_profile, crontab -e insists on invoking vi, an
> editor that I despise
On 03/23/2013 10:47 PM, Garry T. Williams wrote:
On 3-23-13 15:21:37 Joe Zeff wrote:
[joe@khorlia ~]$ echo $EDITOR
nano
This is your problem. You're missing a full path and crontab(1)
requires it.
If so, why does this work:
EDITOR=nano crontab -e
--
users mailing list
users@lists.fedorapr
On 3-23-13 15:21:37 Joe Zeff wrote:
> [joe@khorlia ~]$ echo $EDITOR
> nano
This is your problem. You're missing a full path and crontab(1)
requires it.
--
Garry T. Williams
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedorap
On 03/23/2013 06:54 PM, Reindl Harald wrote:
it's strange that you have so many years experience as
you say but such basic things are always a long thread
by not check basics
I have many years of experience with computers in general, and over a
decade with Linux, but I've never used it profess
Am 24.03.2013 02:37, schrieb Joe Zeff:
> On 03/23/2013 06:25 PM, Reindl Harald wrote:
>> pfff - and why do you not start crond?
>>
>> systemctl enable crond.service
>> systemctl start crond.service
>> systemctl status crond.service
>
> As it happens, I was just running around the Fedora document
On 03/23/2013 06:25 PM, Reindl Harald wrote:
pfff - and why do you not start crond?
systemctl enable crond.service
systemctl start crond.service
systemctl status crond.service
As it happens, I was just running around the Fedora documentation and
found those lines. It's now active. Thanx any
Am 24.03.2013 02:00, schrieb Joe Zeff:
> On 03/23/2013 04:36 PM, Reindl Harald wrote:
>> and what says "ps aux | grep cron"?
>
> Neither cron nor anacron is listed. Somehow, I'm not surprised
pfff - and why do you not start crond?
systemctl enable crond.service
systemctl start crond.service
s
On 03/23/2013 04:36 PM, Reindl Harald wrote:
and what says "ps aux | grep cron"?
Neither cron nor anacron is listed. Somehow, I'm not surprised.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/u
Am 24.03.2013 00:34, schrieb Joe Zeff:
> Sorry, but I don't use sudo. Ever. In fact, when I did a clean install on
> my laptop, I made sure it wasn't
> included. If I need to be root, I know and understand how su works
so just do it
>> Start the cron process
>
> Better yet:
>
> EDITOR=nan
On 03/23/2013 04:20 PM, Steven Stern wrote:
Sometimes we just have to bite the bullet. You're trying to add ONE
LINE to crontab. Just do it. Or
Stop the cron process
edit /var/spool/yourid (with your favorite editor as root via sudo)
Sorry, but I don't use sudo. Ever. In fact, when
On 03/23/2013 06:13 PM, Joe Zeff wrote:
> On 03/23/2013 04:06 PM, Steven Stern wrote:
>> Suck it up!
>>
>
> FOAD
>
> Just because you like using an obsolete, antique editor that was
> designed before CRTs were in use doesn't mean that everybody else has to
> use it. Yes, I started out with punch
Am 24.03.2013 00:04, schrieb Mark Eggers:
> On Sat, 23 Mar 2013 15:21:37 -0700, Joe Zeff wrote:
>
>> On 03/23/2013 02:59 PM, Ed Greshko wrote:
>>> egreshko@meimei ~]$ export EDITOR=/usr/bin/nano [egreshko@meimei ~]$
>>> crontab -e
>>
>> [joe@khorlia ~]$ echo $EDITOR nano
>>
>> And, if I just run
On 03/23/2013 04:06 PM, Steven Stern wrote:
Suck it up!
FOAD
Just because you like using an obsolete, antique editor that was
designed before CRTs were in use doesn't mean that everybody else has to
use it. Yes, I started out with punched cards, but I've also moved on.
Maybe it's time fo
On 03/23/2013 04:43 PM, Joe Zeff wrote:
> On 03/23/2013 11:56 AM, Steven Stern wrote:
>> One of those things that can bite you in the butt is that the
>> environment for /bin/sh might be different than than in /bin/bash,
>> especially as invoked by cron.
>
> Somebody suggested adding something new
On Sat, 23 Mar 2013 15:21:37 -0700, Joe Zeff wrote:
> On 03/23/2013 02:59 PM, Ed Greshko wrote:
>> egreshko@meimei ~]$ export EDITOR=/usr/bin/nano [egreshko@meimei ~]$
>> crontab -e
>
> [joe@khorlia ~]$ echo $EDITOR nano
>
> And, if I just run nano from the command line, it works, because
> /usr
On 03/23/2013 03:25 PM, Reindl Harald wrote:
besides the fact that /var/log/cron has nothing to do with vi
so do not use it - what is your problem?
I wasn't writing about examining /var/log/cron, I was trying to modify
my crontab with the editor that I want to use.
--
users mailing list
users
Am 23.03.2013 23:19, schrieb Joe Zeff:
> On 03/23/2013 02:57 PM, Michael D. Setzer II wrote:
>> What is showing in the /var/log/cron file?
>>
> Just that I began editing it. I don't know vi, I don't want to, and I've no
> idea how to exit except for killing
> the terminal, which I did. I say, "
On 03/23/2013 02:59 PM, Ed Greshko wrote:
egreshko@meimei ~]$ export EDITOR=/usr/bin/nano
[egreshko@meimei ~]$ crontab -e
[joe@khorlia ~]$ echo $EDITOR
nano
And, if I just run nano from the command line, it works, because
/usr/bin is on my PATH.
--
users mailing list
users@lists.fedoraprojec
On 03/23/2013 02:57 PM, Michael D. Setzer II wrote:
What is showing in the /var/log/cron file?
Just that I began editing it. I don't know vi, I don't want to, and
I've no idea how to exit except for killing the terminal, which I did.
I say, "Fi on vi!"
--
users mailing list
users@lists.fe
Am 23.03.2013 23:00, schrieb Joe Zeff:
> On 03/23/2013 02:47 PM, Reindl Harald wrote:
>> why do you not simply place your cronjobs in/etc/cron.d/?
>>
>> i maintain a lot of servers with tons of cronjobs running as
>> different users and never in my life called the contab-command
>
> Because cron
On 03/23/2013 02:47 PM, Reindl Harald wrote:
why do you not simply place your cronjobs in/etc/cron.d/?
i maintain a lot of servers with tons of cronjobs running as
different users and never in my life called the contab-command
Because crontab is specifically written for this, and I saw no reas
would you please strip your quotes
especially footers and signatures
a 7 KB message for a one-liner is ridiculus
Am 23.03.2013 22:57, schrieb Michael D. Setzer II:
> [stripped fullquote]
> What is showing in the /var/log/cron file?
>
>> To unsubscribe or change subscription options:
>> https://adm
On 03/24/13 05:43, Joe Zeff wrote:
> On 03/23/2013 11:56 AM, Steven Stern wrote:
>> One of those things that can bite you in the butt is that the
>> environment for /bin/sh might be different than than in /bin/bash,
>> especially as invoked by cron.
>
> Somebody suggested adding something new to cr
On 23 Mar 2013 at 14:43, Joe Zeff wrote:
Date sent: Sat, 23 Mar 2013 14:43:44 -0700
From: Joe Zeff
To: Community support for Fedora users
Subject:Re: Problem with cron
> On 03/23/2013 11:56 AM, Steven Stern wrote:
> &g
Am 23.03.2013 22:43, schrieb Joe Zeff:
> On 03/23/2013 11:56 AM, Steven Stern wrote:
>> One of those things that can bite you in the butt is that the
>> environment for /bin/sh might be different than than in /bin/bash,
>> especially as invoked by cron.
>
> Somebody suggested adding something ne
On 03/23/2013 11:56 AM, Steven Stern wrote:
One of those things that can bite you in the butt is that the
environment for /bin/sh might be different than than in /bin/bash,
especially as invoked by cron.
Somebody suggested adding something new to crontab and seeing if it
works. I tried it. A
On 03/23/2013 11:56 AM, Steven Stern wrote:
One of those things that can bite you in the butt is that the
environment for /bin/sh might be different than than in /bin/bash,
especially as invoked by cron.
It worked fine in F 16, and it works from a command line. I'm not
saying you're wrong, b
On 03/23/2013 11:36 AM, Michael Schwendt wrote:
On Sat, 23 Mar 2013 10:39:00 -0700, Joe Zeff wrote:
On 03/23/2013 02:48 AM, Michael Schwendt wrote:
Well, as I've asked: Do other cron jobs work for you if you install them
in the same way? And it would be normal (default) behaviour for them to
b
On 03/23/2013 12:47 PM, Joe Zeff wrote:
> On 03/23/2013 08:58 AM, Steven Stern wrote:
>> On 03/22/2013 03:16 PM, Joe Zeff wrote:
>>> I have my computers registered with the Linux Counter, and my main
>>> desktop machine is supposed to update its status once a week, using a
>>> cron job:
>>>
>>> # a
On Sat, 23 Mar 2013 10:39:00 -0700, Joe Zeff wrote:
> On 03/23/2013 02:48 AM, Michael Schwendt wrote:
> > Well, as I've asked: Do other cron jobs work for you if you install them
> > in the same way? And it would be normal (default) behaviour for them to
> > be logged in /var/log/cron - grep joe /
Am 23.03.2013 18:43, schrieb Richard Vickery:
> On Fri, Mar 22, 2013 at 10:03 PM, David G. Miller wrote:
> Perchance you're not in crontab.allow?
>
> where is crontab.allow? I just went to locate the file and couldn't
it simply does not exist
updatedb and locate are your friend
[root@srv-rh
On 03/23/2013 08:58 AM, Steven Stern wrote:
On 03/22/2013 03:16 PM, Joe Zeff wrote:
I have my computers registered with the Linux Counter, and my main
desktop machine is supposed to update its status once a week, using a
cron job:
# added by lico-update.sh version 0.3.14
58 11 * * 4 /home/joe/b
On Fri, Mar 22, 2013 at 10:03 PM, David G. Miller wrote:
> Joe Zeff zeff.us> writes:
>
> >
> > I have my computers registered with the Linux Counter, and my main
> > desktop machine is supposed to update its status once a week, using a
> > cron job:
> >
> > # added by lico-update.sh version 0.3.1
On 03/23/2013 02:48 AM, Michael Schwendt wrote:
Well, as I've asked: Do other cron jobs work for you if you install them
in the same way? And it would be normal (default) behaviour for them to
be logged in /var/log/cron - grep joe /var/log/cron would tell.
I don't have any other, so I can't tel
On 03/22/2013 03:16 PM, Joe Zeff wrote:
> I have my computers registered with the Linux Counter, and my main
> desktop machine is supposed to update its status once a week, using a
> cron job:
>
> # added by lico-update.sh version 0.3.14
> 58 11 * * 4 /home/joe/bin/lico-update.sh -m
>
> The permi
On Fri, 22 Mar 2013 14:12:02 -0700, Joe Zeff wrote:
> As the included comment says,
I'm not familiar with any lico-update.sh script (and have never used it
for the LiCo project), so I could not guess what it does, especially not
since it added an absolute path for the command to execute. Hence my
On 03/22/2013 10:03 PM, David G. Miller wrote:
Perchance you're not in crontab.allow?
That's only relevant if the file exists, and it doesn't on my system.
The file /etc/cron.deny does exist, but it's empty.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscrip
Joe Zeff zeff.us> writes:
>
> I have my computers registered with the Linux Counter, and my main
> desktop machine is supposed to update its status once a week, using a
> cron job:
>
> # added by lico-update.sh version 0.3.14
> 58 11 * * 4 /home/joe/bin/lico-update.sh -m
>
> The permissions
On 03/22/2013 01:49 PM, Michael Schwendt wrote:
On Fri, 22 Mar 2013 13:16:16 -0700, Joe Zeff wrote:
I have my computers registered with the Linux Counter, and my main
desktop machine is supposed to update its status once a week, using a
cron job:
# added by lico-update.sh version 0.3.14
58 11
On 03/22/2013 01:40 PM, suvayu ali wrote:
On Fri, Mar 22, 2013 at 9:16 PM, Joe Zeff wrote:
Does anybody know what's happened, or how to find out?
Maybe save the output to a log file.
/home/joe/bin/lico-update.sh -m &> /tmp/mycron.log
There isn't any output. However, I've been thinking
On Fri, 22 Mar 2013 13:16:16 -0700, Joe Zeff wrote:
> I have my computers registered with the Linux Counter, and my main
> desktop machine is supposed to update its status once a week, using a
> cron job:
>
> # added by lico-update.sh version 0.3.14
> 58 11 * * 4 /home/joe/bin/lico-update.sh -m
On Fri, Mar 22, 2013 at 9:16 PM, Joe Zeff wrote:
> Does anybody know what's happened, or how to find out?
Maybe save the output to a log file.
/home/joe/bin/lico-update.sh -m &> /tmp/mycron.log
--
Suvayu
Open source is the future. It sets us free.
--
users mailing list
users@lists.fedorapro
I have my computers registered with the Linux Counter, and my main
desktop machine is supposed to update its status once a week, using a
cron job:
# added by lico-update.sh version 0.3.14
58 11 * * 4 /home/joe/bin/lico-update.sh -m
The permissions on the script are right, and if run manually,
52 matches
Mail list logo
