214 reputation
113
bio website github.com/clime/lit
location Czech Republic
age 29
visits member for 2 years, 7 months
seen May 30 at 17:28

pretty much me


Jul
23
awarded  Popular Question
Jul
2
awarded  Curious
Jun
23
awarded  Popular Question
Nov
11
awarded  Popular Question
Nov
4
revised my wifi Wireless-N 2230 can't connect occassionally
edited title
Nov
4
accepted my wifi Wireless-N 2230 can't connect occassionally
Nov
4
comment my wifi Wireless-N 2230 can't connect occassionally
Thank you! It is not that often that it happens so ill go with removing/adding the wifi kernel module (they say it is iwlang, in my case it is iwldvm).
Nov
3
asked my wifi Wireless-N 2230 can't connect occassionally
Nov
3
awarded  Informed
Oct
14
comment output of top gets truncated to 80 columns when run by cron
I use this to keep information about processes that were running at any time during last five days. These are 1-min snapshots so something might get lost but I think it is good enough for me. I want to have some data available when I discover there was a peak in resource usage (I use munin for that). I haven't found a better way to keep track of past processes (tried psacct).
Oct
13
accepted output of top gets truncated to 80 columns when run by cron
Oct
13
awarded  Yearling
Oct
13
comment output of top gets truncated to 80 columns when run by cron
Ye, /1 does not need to be there. I have changed it. The problem persists though.
Oct
13
asked output of top gets truncated to 80 columns when run by cron
Apr
18
accepted find . .[^.]* -type f -print0 | xargs -0 sudo chmod 664; does not work
Apr
17
comment find . .[^.]* -type f -print0 | xargs -0 sudo chmod 664; does not work
Thank your for your in-depth explanation!
Apr
17
comment find . .[^.]* -type f -print0 | xargs -0 sudo chmod 664; does not work
You are right about that .[^.]* being redundant but there is not a symlink on the path to to that file. As I pointed out the file is being found by find and adding -n5 solved that problem. Also I didn't mention that but even files in the current directory were untouched. I am sure that the command was exiting prematurely. If I try to run the same command with the same data on another system, I get sudo: unable to execute /bin/chmod: Argument list too long Strangely I did not get this error on the system in question.
Apr
17
comment find . .[^.]* -type f -print0 | xargs -0 sudo chmod 664; does not work
.[^.]* includes hidden files and directories but not .. directory. -print0 and -0 options are useful if you have got filenames with spaces. It was not buffer overflow. It was just some limit on how many parameters chmod accepts (the rest is probably trashed).
Apr
17
comment find . .[^.]* -type f -print0 | xargs -0 sudo chmod 664; does not work
-n5 worked for my original command! And with -n100 it still works and is also fast. Thank you! If you could make that an answer...
Apr
17
comment find . .[^.]* -type f -print0 | xargs -0 sudo chmod 664; does not work
the variant with -exec works, and the command execution is much longer. It seems that my original command crashes somewhere in the process.