Re: [gentoo-user] How to find out to what file(...) writes goes on a idle system...
Hi, meino.cra...@gmx.de writes: In the context of preserving the live of flash media by minimizing the count of unessary writes I want to know which application/daemon/etc is continous writing to that media and which entity (file/pipe/fifo...) is receiving those writes... You could use this: # echo 1 /proc/sys/vm/block_dump then every read and write operation on block devices shows up in dmesg with the PID, process name and the block id. (This can be a lot of lines, so dmesg -c might be useful) I'm not exactly sure how to identify which files belong to which block, though. Regards Johannes signature.asc Description: PGP signature
Re: [gentoo-user] Re: hibernation
On Saturday 06 Dec 2014 07:41:18 J. Roeleveld wrote: Hibernation depends on a myriad of CPU variants, setting and the matching memory issues. (U)efi is a good place to start your long, arduous journey of research [1] ; see S4. Not my experience, suspend-to-disk works quite well. The biggest issue was with certain drivers not being able to re-initialize certain hardware. (Yes, I am talking about the likes of Nvidia) With current kernels, it does work though. It is not just Nvidia. Suspend to disk (hybernation) worked fine on my laptop for years. Then something changed in the kernel and now although it will hybernate, waking up causes all sort of failures and crashes. It is a kernel bug, I found out that someone reported it last year, but it has not been fixed yet it seems. On another PC both hybernation and sleep have gone through a cyclical pattern of working or not working over the years. Thankfully now they are working! :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] How to find out to what file(...) writes goes on a idle system...
On Sat, 06 Dec 2014 12:01:16 +0100 Johannes Altmanninger wrote: Hi, meino.cra...@gmx.de writes: In the context of preserving the live of flash media by minimizing the count of unessary writes I want to know which application/daemon/etc is continous writing to that media and which entity (file/pipe/fifo...) is receiving those writes... You could use this: # echo 1 /proc/sys/vm/block_dump then every read and write operation on block devices shows up in dmesg with the PID, process name and the block id. (This can be a lot of lines, so dmesg -c might be useful) I'm not exactly sure how to identify which files belong to which block, though. This depends on filesystem being used. For ext* family debugfs may be used: # debugfs /dev/your_dev ncheck inode1 inode2 ... Best regards, Andrew Savchenko pgpTSVfkHacd7.pgp Description: PGP signature
Re: [gentoo-user] How to find out to what file(...) writes goes on a idle system...
meino.cra...@gmx.de writes: Hi, on different systems I see the write stats (/proc/dikstats) to physical existing disks steadily increasing. Looking at the output of lsof I cannot find any file suspicous for receiving those writes. In the context of preserving the live of flash media by minimizing the count of unessary writes I want to know which application/daemon/etc is continous writing to that media and which entity (file/pipe/fifo...) is receiving those writes... How can I find that information? iotop might tell you. Since you don't see anything in lsof, I'd assume that the file (if it's a file) is opened and closed rather than being kept open. Or could it be a swap partition which is used? -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] urxvt on i3wm as wallpaper
On Sat, Dec 6, 2014 at 5:44 AM, lee l...@yagibdah.de wrote: Omit the window decorations? I liked the picture, but actually I am not sure if that's what I want. I want a terminal that is on the background (wallpaper) of the screen, not in the floating mode or something like that. For example like the conky behaves when it is on the walpaper. However how did you remove the window decorations?! thanks.
Re: [gentoo-user] Re: hibernation
On Sat, 6 Dec 2014 11:15:07 +, Mick wrote: It is not just Nvidia. Suspend to disk (hybernation) worked fine on my laptop for years. Then something changed in the kernel and now although it will hybernate, waking up causes all sort of failures and crashes. It is a kernel bug, I found out that someone reported it last year, but it has not been fixed yet it seems. I had a similar experience and found it as caused by the ethernet driver. I added a line to my hibernate script to unload the module before hibernating and the problem went away. -- Neil Bothwick The Japanese call us lazy, but at least we cook our fish! pgpKOFV8xveyT.pgp Description: OpenPGP digital signature
Re: [gentoo-user] How to find out to what file(...) writes goes on a idle system...
On Sat, Dec 06, 2014 at 12:27:06PM +0100, lee wrote: meino.cra...@gmx.de writes: Hi, on different systems I see the write stats (/proc/dikstats) to physical existing disks steadily increasing. Looking at the output of lsof I cannot find any file suspicous for receiving those writes. […] How can I find that information? iotop might tell you. I frequently use iotop -o. Another possibility might be ftop. -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me on any social network. “Your code is shit.. your argument is shit.” – Linus Torvalds, linux.kernel signature.asc Description: Digital signature
[gentoo-user] Re: How to find out to what file(...) writes goes on a idle system...
meino.cramer at gmx.de writes: on different systems I see the write stats (/proc/dikstats) to physical existing disks steadily increasing. Looking at the output of lsof I cannot find any file suspicous for receiving those writes. Ok so in my experiences you need a (2) pronged approach. (1) Then pursue quantifying with tools just what is causing the writes, strategies for minimization and monitoring as needed. So folks are going down path (1) with you, that is fine. (2) First minimize those write to your non-mechanical memory. Path (2) on any and all minimized gentoo or embedded gentoo systems, I start out with USE=-* to keep things minimum. Yea that tweaks the devs now, but minimal system are just that, minimized, imho, so that is a firm standard I always operation on. Set the minimum number of global flags and the thinest profile that will work for your system. Every flag invokes more code and hence more processes, more files, more writing to media. Also, all log files should be written off the embeded system via NFS or other similar mechanisms. If you want further help, put up a document where folks can spend $20 and get a similar board up and running embedded gentoo. Then they can see exactly what you see have and you can work as a team, or not, your call. I have dozens of tricks to minimize a gentoo system. But it is quite a bit of work, just so you know. It's not a do this and it great. It more like, try this, study the result and then alter the strategy. hth, James
[gentoo-user] emerge --depclean wants to remove active python?
Hi Gentoo-users, I just updated my box (iirc, there was something python-related) but depite of having python 3.4 active, emerge wants to remove it: # eselect python list Available Python interpreters: [1] python2.7 [2] python3.3 [3] python3.4 * # emerge --pretend --depclean Calculating dependencies... done! Calculating removal order... These are the packages that would be unmerged: dev-lang/python selected: 3.4.1 protected: none omitted: 2.7.7 3.3.5-r1 All selected packages: =dev-lang/python-3.4.1 If 3.4.1 gets removed, I will have to run python-updater and compile all against 3.3. But why? 3.4.1 is stable, so why does Portage want to remove it??? Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] emerge --depclean wants to remove active python?
On 12/06/2014 12:18 PM, Jarry wrote: Hi Gentoo-users, I just updated my box (iirc, there was something python-related) but depite of having python 3.4 active, emerge wants to remove it: # eselect python list Available Python interpreters: [1] python2.7 [2] python3.3 [3] python3.4 * # emerge --pretend --depclean Calculating dependencies... done! Calculating removal order... These are the packages that would be unmerged: dev-lang/python selected: 3.4.1 protected: none omitted: 2.7.7 3.3.5-r1 All selected packages: =dev-lang/python-3.4.1 If 3.4.1 gets removed, I will have to run python-updater and compile all against 3.3. But why? 3.4.1 is stable, so why does Portage want to remove it??? Jarry Check out this thread from a day or two ago: http://thread.gmane.org/gmane.linux.gentoo.user/279158. Alec
Re: [gentoo-user] emerge --depclean wants to remove active python?
On 06-Dec-14 18:25, Alec Ten Harmsel wrote: If 3.4.1 gets removed, I will have to run python-updater and compile all against 3.3. But why? 3.4.1 is stable, so why does Portage want to remove it??? Check out this thread from a day or two ago: http://thread.gmane.org/gmane.linux.gentoo.user/279158. Thanks, Alec. How could I have missed that thread??? Mea culpa... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] Re: How to find out to what file(...) writes goes on a idle system...
James wirel...@tampabay.rr.com [14-12-06 18:16]: meino.cramer at gmx.de writes: on different systems I see the write stats (/proc/dikstats) to physical existing disks steadily increasing. Looking at the output of lsof I cannot find any file suspicous for receiving those writes. Ok so in my experiences you need a (2) pronged approach. (1) Then pursue quantifying with tools just what is causing the writes, strategies for minimization and monitoring as needed. So folks are going down path (1) with you, that is fine. (2) First minimize those write to your non-mechanical memory. Path (2) on any and all minimized gentoo or embedded gentoo systems, I start out with USE=-* to keep things minimum. Yea that tweaks the devs now, but minimal system are just that, minimized, imho, so that is a firm standard I always operation on. Set the minimum number of global flags and the thinest profile that will work for your system. Every flag invokes more code and hence more processes, more files, more writing to media. Also, all log files should be written off the embeded system via NFS or other similar mechanisms. If you want further help, put up a document where folks can spend $20 and get a similar board up and running embedded gentoo. Then they can see exactly what you see have and you can work as a team, or not, your call. I have dozens of tricks to minimize a gentoo system. But it is quite a bit of work, just so you know. It's not a do this and it great. It more like, try this, study the result and then alter the strategy. hth, James Hi, thank you very for all help I received regarding my question. The system is already down to a limit. The by default running processes are: root 1 0 0 15:36 ?00:00:00 init [3] root 2 0 0 15:36 ?00:00:00 [kthreadd] root 3 2 0 15:36 ?00:00:01 [ksoftirqd/0] root 5 2 0 15:36 ?00:00:00 [kworker/0:0H] root 7 2 0 15:36 ?00:00:00 [khelper] root 8 2 0 15:36 ?00:00:00 [kdevtmpfs] root 160 2 0 15:36 ?00:00:00 [writeback] root 162 2 0 15:36 ?00:00:00 [crypto] root 164 2 0 15:36 ?00:00:00 [bioset] root 166 2 0 15:36 ?00:00:00 [kblockd] root 168 2 0 15:36 ?00:00:00 [cfg80211] root 169 2 0 15:36 ?00:00:00 [kworker/0:1] root 280 2 0 15:36 ?00:00:00 [kswapd0] root 296 2 0 15:36 ?00:00:00 [fsnotify_mark] root 372 2 0 15:36 ?00:00:00 [ipv6_addrconf] root 398 2 0 15:36 ?00:00:00 [deferwq] root 406 2 0 15:36 ?00:00:12 [mmcqd/0] root 412 2 0 15:36 ?00:00:00 [kworker/0:2] root 415 2 0 15:36 ?00:00:00 [jbd2/mmcblk0p2-] root 416 2 0 15:36 ?00:00:00 [ext4-rsv-conver] root 563 1 0 15:37 ?00:00:00 /lib/systemd/systemd-udevd --daemon root 952 1 0 15:37 ?00:00:00 /usr/sbin/ifplugd --iface=usb0 root 1380 1 0 15:37 ?00:00:00 /usr/sbin/sshd root 1399 1 0 15:37 tty1 00:00:00 /sbin/agetty 38400 tty1 linux root 1400 1 0 15:37 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 1401 1 0 15:37 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 1402 1 0 15:37 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 1403 1 0 15:37 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 1404 1 0 15:37 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 1405 1 0 15:37 ttyS000:00:00 /sbin/agetty -L 9600 ttyS0 vt100 root 1406 1380 0 15:37 ?00:00:02 sshd: root@pts/0 root 1412 1406 0 15:37 pts/000:00:00 screen -R -d root 1414 1412 0 15:37 ?00:00:01 SCREEN -R -d root 1415 1414 0 15:37 pts/100:00:05 -/bin/zsh root 1434 2 0 15:38 ?00:00:00 [kworker/0:1H] root 1866 2 0 15:43 ?00:00:00 [kworker/u2:0] root 8556 2 0 16:49 ?00:00:00 [kworker/u2:2] The count of getty processes may be decreaseable...but the rest is ok, I think. When I do a ftop I get no process, which have an open file handle for writes...sometimes screen writes to utmp but thats it. I suspect the swapfile I mounted as swapdevice for being guilty. I will deactivate that and we will see then. When looking at /proc/diskstats: Will I see writes to FIFOs on the disk as writes to the disk??? If YES...it would explain it... Best regards, Meino
[gentoo-user] Re: Openrc-run
Michael Orlitzky mjo at gentoo.org writes: 'man openrc' nor 'man 8 openrc-run' return anything. So, the reason you can't find their man pages is because they don't exist yet. Try `man 8 rc` or `man 8 runscript` instead. Ah. Yea, my googling often takes me places of curiosity that I find alluring and not often opaque. If you ever need to read a man page that isn't installed, you can give the path to it locally. So if you clone that repo, you can do: $ man ./man/openrc-run.8 to read it. Ok, that's what I thought I had to do. I did not know if there was some form of browser kung_foo I had missed to read these remotely without download/install types of efforts thx, James
[gentoo-user] Re: How to find out to what file(...) writes goes on a idle system...
meino.cramer at gmx.de writes: (1) Then pursue quantifying with tools just what is causing the writes, strategies for minimization and monitoring as needed. So folks are going down path (1) with you, that is fine. Prong (1) includes all issues related to systemd. Probably embedded experience with systemd is rare, just guessing. Certainly I have none of that experience. So post to those iotop responses and remind folks you are using systemd on an embedded (gentoo) micro. root 563 1 0 15:37 ? 00:00:00 /lib/systemd/systemd-udevd --daemon (2) First minimize those write to your non-mechanical memory. I have dozens of tricks to minimize a gentoo system. But it is quite a bit of work, just so you know. It's not a do this and it great. It more like, try this, study the result and then alter the strategy. hth, James Hi, thank you very for all help I received regarding my question. The system is already down to a limit. The by default running processes are: root 1 0 0 15:36 ?00:00:00 init [3] root 2 0 0 15:36 ?00:00:00 [kthreadd] root 3 2 0 15:36 ?00:00:01 [ksoftirqd/0] root 5 2 0 15:36 ?00:00:00 [kworker/0:0H] root 7 2 0 15:36 ?00:00:00 [khelper] root 8 2 0 15:36 ?00:00:00 [kdevtmpfs] root 160 2 0 15:36 ?00:00:00 [writeback] root 162 2 0 15:36 ?00:00:00 [crypto] root 164 2 0 15:36 ?00:00:00 [bioset] root 166 2 0 15:36 ?00:00:00 [kblockd] root 168 2 0 15:36 ?00:00:00 [cfg80211] root 169 2 0 15:36 ?00:00:00 [kworker/0:1] root 280 2 0 15:36 ?00:00:00 [kswapd0] root 296 2 0 15:36 ?00:00:00 [fsnotify_mark] root 372 2 0 15:36 ?00:00:00 [ipv6_addrconf] root 398 2 0 15:36 ?00:00:00 [deferwq] root 406 2 0 15:36 ?00:00:12 [mmcqd/0] root 412 2 0 15:36 ?00:00:00 [kworker/0:2] root 415 2 0 15:36 ?00:00:00 [jbd2/mmcblk0p2-] root 416 2 0 15:36 ?00:00:00 [ext4-rsv-conver] root 563 1 0 15:37 ?00:00:00 /lib/systemd/systemd-udevd --daemon root 952 1 0 15:37 ?00:00:00 /usr/sbin/ifplugd --iface=usb0 root 1380 1 0 15:37 ?00:00:00 /usr/sbin/sshd root 1399 1 0 15:37 tty1 00:00:00 /sbin/agetty 38400 tty1 linux root 1400 1 0 15:37 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 1401 1 0 15:37 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 1402 1 0 15:37 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 1403 1 0 15:37 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 1404 1 0 15:37 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 1405 1 0 15:37 ttyS000:00:00 /sbin/agetty -L 9600 ttyS0 vt100 root 1406 1380 0 15:37 ?00:00:02 sshd: root at pts/0 root 1412 1406 0 15:37 pts/000:00:00 screen -R -d root 1414 1412 0 15:37 ?00:00:01 SCREEN -R -d root 1415 1414 0 15:37 pts/100:00:05 -/bin/zsh root 1434 2 0 15:38 ?00:00:00 [kworker/0:1H] root 1866 2 0 15:43 ?00:00:00 [kworker/u2:0] root 8556 2 0 16:49 ?00:00:00 [kworker/u2:2] I'd research kworker http://askubuntu.com/questions/33640/kworker-what-is-it-and-why-is-it-hogging-so-much-cpu The count of getty processes may be decreaseable...but the rest is ok, I think. Those are static and just sitting incase you need a getty, so not a problem When I do a ftop I get no process, which have an open file handle for writes...sometimes screen writes to utmp but thats it. With a traditional (non systemd) approach, init scripts just fire up things at boot time and such. With systemd, I have no idea what's going on. It's a curious situation and maybe systemd has no issue in your excessive writes; pure speculation on my part. But an embedded system just sitting idle should use very little resource and sit quietly, in my experiences. I suspect the swapfile I mounted as swapdevice for being guilty. I will deactivate that and we will see then. good thing to examine. When looking at /proc/diskstats: Will I see writes to FIFOs on the disk as writes to the disk??? If YES...it would explain it... Also good to look at. I usually use ext2 or one of the newer files systems, just for solid state memory. Here is a good link to get your research your fs options. http://free-electrons.com/blog/managing-flash-storage-with-linux/ Since you have (2) boards, have you considered installing the second one differently (different file system, no systemd etc etc to compare the 2 results? If you can put different install-varients on different usb/sd/? media, then you can just
[gentoo-user] Print PDF or PS files
In: XFCE4 home folder menu: Edit - Configure Custom Action I have entered: Print PDF or PS files command: lpr %N However, the above command: lpr %N is only good if the PDF or PS files have standard Letter size format. If a PDF/PS file contains pages that are different sizes or rotated the output doesn't looks good. Print is cut off etc. I have to open the file with evince and print it. I was trying to sent a print job via evince without opening the file form a commands line, but I don't think it is possible. I've Adobe Reader 9 but I can not even print correctly standard documents, something is messed up; the orientation is not correct. -- Joseph
Re: [gentoo-user] Re: How to find out to what file(...) writes goes on a idle system...
Hi James, ...my board does not use systemd as far as I know...the whole mimic is original gentoo stage3 stuff and Gentoo defaults to openrc/udev and not systemd (or am I wrong?) Cheers Meino James wirel...@tampabay.rr.com [14-12-06 21:16]: meino.cramer at gmx.de writes: (1) Then pursue quantifying with tools just what is causing the writes, strategies for minimization and monitoring as needed. So folks are going down path (1) with you, that is fine. Prong (1) includes all issues related to systemd. Probably embedded experience with systemd is rare, just guessing. Certainly I have none of that experience. So post to those iotop responses and remind folks you are using systemd on an embedded (gentoo) micro. root 563 1 0 15:37 ? 00:00:00 /lib/systemd/systemd-udevd --daemon (2) First minimize those write to your non-mechanical memory. I have dozens of tricks to minimize a gentoo system. But it is quite a bit of work, just so you know. It's not a do this and it great. It more like, try this, study the result and then alter the strategy. hth, James Hi, thank you very for all help I received regarding my question. The system is already down to a limit. The by default running processes are: root 1 0 0 15:36 ?00:00:00 init [3] root 2 0 0 15:36 ?00:00:00 [kthreadd] root 3 2 0 15:36 ?00:00:01 [ksoftirqd/0] root 5 2 0 15:36 ?00:00:00 [kworker/0:0H] root 7 2 0 15:36 ?00:00:00 [khelper] root 8 2 0 15:36 ?00:00:00 [kdevtmpfs] root 160 2 0 15:36 ?00:00:00 [writeback] root 162 2 0 15:36 ?00:00:00 [crypto] root 164 2 0 15:36 ?00:00:00 [bioset] root 166 2 0 15:36 ?00:00:00 [kblockd] root 168 2 0 15:36 ?00:00:00 [cfg80211] root 169 2 0 15:36 ?00:00:00 [kworker/0:1] root 280 2 0 15:36 ?00:00:00 [kswapd0] root 296 2 0 15:36 ?00:00:00 [fsnotify_mark] root 372 2 0 15:36 ?00:00:00 [ipv6_addrconf] root 398 2 0 15:36 ?00:00:00 [deferwq] root 406 2 0 15:36 ?00:00:12 [mmcqd/0] root 412 2 0 15:36 ?00:00:00 [kworker/0:2] root 415 2 0 15:36 ?00:00:00 [jbd2/mmcblk0p2-] root 416 2 0 15:36 ?00:00:00 [ext4-rsv-conver] root 563 1 0 15:37 ?00:00:00 /lib/systemd/systemd-udevd --daemon root 952 1 0 15:37 ?00:00:00 /usr/sbin/ifplugd --iface=usb0 root 1380 1 0 15:37 ?00:00:00 /usr/sbin/sshd root 1399 1 0 15:37 tty1 00:00:00 /sbin/agetty 38400 tty1 linux root 1400 1 0 15:37 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 1401 1 0 15:37 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 1402 1 0 15:37 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 1403 1 0 15:37 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 1404 1 0 15:37 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 1405 1 0 15:37 ttyS000:00:00 /sbin/agetty -L 9600 ttyS0 vt100 root 1406 1380 0 15:37 ?00:00:02 sshd: root at pts/0 root 1412 1406 0 15:37 pts/000:00:00 screen -R -d root 1414 1412 0 15:37 ?00:00:01 SCREEN -R -d root 1415 1414 0 15:37 pts/100:00:05 -/bin/zsh root 1434 2 0 15:38 ?00:00:00 [kworker/0:1H] root 1866 2 0 15:43 ?00:00:00 [kworker/u2:0] root 8556 2 0 16:49 ?00:00:00 [kworker/u2:2] I'd research kworker http://askubuntu.com/questions/33640/kworker-what-is-it-and-why-is-it-hogging-so-much-cpu The count of getty processes may be decreaseable...but the rest is ok, I think. Those are static and just sitting incase you need a getty, so not a problem When I do a ftop I get no process, which have an open file handle for writes...sometimes screen writes to utmp but thats it. With a traditional (non systemd) approach, init scripts just fire up things at boot time and such. With systemd, I have no idea what's going on. It's a curious situation and maybe systemd has no issue in your excessive writes; pure speculation on my part. But an embedded system just sitting idle should use very little resource and sit quietly, in my experiences. I suspect the swapfile I mounted as swapdevice for being guilty. I will deactivate that and we will see then. good thing to examine. When looking at /proc/diskstats: Will I see writes to FIFOs on the disk as writes to the disk??? If YES...it would explain it... Also good to look at. I usually use ext2 or one of the newer files systems, just for solid state memory.
