Re: nother problem I can't access my crontab, no perms

2019-05-20 Thread Étienne Mollier
On 5/20/19 8:40 PM, Gene Heskett wrote: >> I would tend to believe that execution of "crontab" related >> commands will benefit from the proper UIDs when operating. On >> my machine, at the same working directory, I have: >> >> $ sudo ls -lR >> .: >> total 0 >> drwx-wx--T 2 roo

Re: nother problem I can't access my crontab, no perms

2019-05-20 Thread Gene Heskett
On Monday 20 May 2019 02:21:20 pm Étienne Mollier wrote: > Good Day Gene, > > On coyote, /var/spool/cron contained: > > drwx-wx--T 2 root systemd-timesync 4096 Mar 31 09:15 crontabs > > ^^^ > You can't go through this "crontab" directory if you are not > root, or a member of the group

Re: nother problem I can't access my crontab, no perms

2019-05-20 Thread Étienne Mollier
Good Day Gene, On coyote, /var/spool/cron contained: > drwx-wx--T 2 root systemd-timesync 4096 Mar 31 09:15 crontabs ^^^ You can't go through this "crontab" directory if you are not root, or a member of the group systemd-timesync. That includes that you can't read any file below, even

Re: nother problem I can't access my crontab, no perms

2019-05-20 Thread Gene Heskett
On Monday 20 May 2019 11:58:45 am Gene Heskett wrote: > Gut an ls -lR of /var/spool shows they are an exact copy of the wheezy > files. With mine own by me. > > What did I screw up now. I had noticed my kmail spam folder was > filling up because my cron scripts aren't running as scheduled. > Othe

nother problem I can't access my crontab, no perms

2019-05-20 Thread Gene Heskett
Gut an ls -lR of /var/spool shows they are an exact copy of the wheezy files. With mine own by me. What did I screw up now. I had noticed my kmail spam folder was filling up because my cron scripts aren't running as scheduled. Otherwise I haven't touched it since installing stretch. Any clues