632 reputation
1317
bio website bit.ly/GFscreener11
location stackoverflow.com@askmarcos.com
age
visits member for 2 years, 10 months
seen Oct 15 at 13:45

Pioneers are the ones with arrows in their backs.

Investment Portfolio Software, Trade Automation

Designer of infinite compression algorithms, and other research projects


Jan
5
revised run a remote process via autossh in background
title typo
Jan
5
comment run a remote process via autossh in background
Silly me, I tried -f right after posting and that worked, but felt bad about answering myself so fast. Thanks. However what's really annoying (and probably a different question) are its frequent disconnects & restarts, whilst another interactive ssh session seems way more tolerant of network hiccups and stays connected to one session.
Jan
5
accepted run a remote process via autossh in background
Jan
5
asked run a remote process via autossh in background
Dec
20
awarded  Yearling
Dec
12
accepted extract last match from logfile till end
Dec
12
comment extract last match from logfile till end
Prefer a regex-based solution (avoiding double-tac on a large file in a fast loop)
Dec
12
comment extract last match from logfile till end
I was trying to avoid that too since the main logfile grows many MB's huge, and the iterations fast (don't want to slow them down by a large fraction), so was looking for a regex-only solution.
Dec
12
revised extract last match from logfile till end
added 106 characters in body
Dec
12
asked extract last match from logfile till end
Nov
8
comment Tell fs to free space from deleted files NOW
Marking as closest answer, although never really "gave back" the space immediately after closing file handles/processes using them. Looking for other kernel/proc/fs-based approaches.
Nov
8
accepted Tell fs to free space from deleted files NOW
Nov
8
awarded  Notable Question
Nov
5
revised crontab and DST disagreement with different timezone
Fixed nasty bash error "15 - 09: value too great for base" when 0* numbers treated as octal
Nov
5
comment crontab and DST disagreement with different timezone
In some cases got /bin/bash: 15 - 09: value too great for base (error token is "09") due to subtle problem of bash treatment of numbers beginning with 0 as octal. Fixed by preceding 10# to numbers.
Nov
4
accepted crontab and DST disagreement with different timezone
Nov
2
revised crontab and DST disagreement with different timezone
logic test was reversed
Nov
1
comment crontab and DST disagreement with different timezone
Um, the opposite of what I last wrote.
Nov
1
comment crontab and DST disagreement with different timezone
I don't like that 1. this isn't a host-timezone-indifferent solution, and 2. assumes the difference will never be greater than six hours, i.e., that DST in Poland will always end first and start last.
Nov
1
comment crontab and DST disagreement with different timezone
The idea is that for most of the year, a 1-hour wait will not be in effect. Only during the few weeks of a 5-hour difference (whether spring or fall), rather than the typical 6, will sleep 3600 be executed.