* enyc meows | 10:59 | |
drawkula | eeek! | 12:38 |
---|---|---|
FatPhil | OK, this will rank as one of the stupidest questions I've asked for a while - how do I find out how a (normal user's) cron job is being invoked? | 16:37 |
surrounder | crontab -l | 16:38 |
Beerbelott | Hello, anyone having trouble reaching on of the mirrors for Devuan (deb.devuan.org) on 141.84.43.19, TCP/80? | 16:38 |
Beerbelott | one* | 16:38 |
Beerbelott | Reverse is devuan.bio.lmu.de | 16:38 |
surrounder | works here | 16:39 |
* onefang points my mirror checker script at it... | 16:39 | |
FatPhil | surrounder: that fails for the same reason the cron job itself is failing - the user its running as no longer exists (this machine doesn't know the new location of my NIS server) | 16:39 |
Beerbelott | It seems to be back... | 16:39 |
r3boot | surrounder: is that you? :) | 16:39 |
surrounder | FatPhil: check /var/spool/cron/crontabs ? | 16:40 |
Beerbelott | Thx for the quick answer ;) | 16:40 |
surrounder | r3boot: ckah | 16:40 |
FatPhil | the fact that a tool is used, rather than you just pointing me to a file implies sometjhing's in /var... | 16:40 |
FatPhil | yup | 16:40 |
r3boot | small world, jwtz :) | 16:40 |
Beerbelott | That makes me wonder... | 16:40 |
onefang | devuan.bio.lmu.de passed my checker. | 16:40 |
Beerbelott | onefang: Yup it seems it was a temporary unavailability | 16:41 |
FatPhil | surrounder: yup - indeed, there the file is - thanks! | 16:41 |
Beerbelott | TCP/433 was fin all along though | 16:42 |
Beerbelott | 443* | 16:42 |
surrounder | FatPhil: :) | 16:43 |
FatPhil | is there a simple package that sends out naggy emails when your mailbox gets too large? I don't want to actually block mails like a hard quota, just to nag. | 18:11 |
FatPhil | i'm postfix/postgrey-based. | 18:11 |
slvr | sounds like a cronjob to me. | 18:13 |
gnarface | yea, that's what cron is for | 18:13 |
gnarface | basically you tell cron to run any command at any arbitrary interval | 18:16 |
gnarface | well, minimum resolution 1 minute | 18:16 |
rwp | Hmm... If their mailbox is too big then they are ignoring the emails already so emailing them does not seem like it would be productive. :-( | 18:18 |
gnarface | hehe | 18:18 |
gnarface | well you could send a sms | 18:18 |
gnarface | or email a second address that gets less traffic... | 18:19 |
gnarface | or just have a command play audio real loud of the mail server screaming in pain or something | 18:19 |
r3boot | Send a notification at, say, 75~85% full, another one around 95%, and once it's full, just dont accept any emails for that acct anymore. That'll make them call support so you can get them to cleanup their mailbox :) | 18:43 |
Beerbelott | I created a script to check every IP address of the deb.devuan.org pool every 5 minutes | 18:53 |
slvr | thanks | 18:53 |
Beerbelott | It seems 141.84.43.19 rings the bell for not responding to connections on TCP/80 very regularly... | 18:53 |
Beerbelott | Is its maintainer around here? | 18:53 |
Beerbelott | Between 1600Z & 1635Z every check was a fail for 141.84.43.19:80 | 18:55 |
FatPhil | they are not ignoring their emails - they just sometimes get tens of megabytes per day, and sometimes forget to move them to a done folder. I can write a simple "shame" script to mail the abusers daily, I guess, as a cron job. | 22:39 |
FatPhil | which reminds me, I need to check on the results of the other thing I crontabbed up this afternoon. | 22:41 |
FatPhil | and it's a fail, as '.' wasn't in @INC | 22:43 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!