On 14 July 2014 6:53:30 AM AEST, Joseph wrote:
>On 07/13/14 23:25, Dimitri Semitsoglou-Tsiapos wrote:
>>On Sun, 13 Jul 2014 14:03:41 -0600
>>Joseph wrote:
>>
>>> I'm trying to clean up my home directory by locating large disk
>>> files. I used: find / -type f -size +2k -exec ls -lh {} \; | aw
Instead of '-exec ls' I recommend the -ls or -printf switches. If you
really require the human-formatted size, you can also just quote {} properly.
Joseph writes:
> I'm trying to clean up my home directory by locating large disk files. I used:
> find / -type f -size +2k -exec ls -lh {} \; |
On 07/13/14 23:25, Dimitri Semitsoglou-Tsiapos wrote:
On Sun, 13 Jul 2014 14:03:41 -0600
Joseph wrote:
I'm trying to clean up my home directory by locating large disk
files. I used: find / -type f -size +2k -exec ls -lh {} \; | awk
'{ print $8 ": " $5 }'
Take a look here regarding why yo
On Sun, 13 Jul 2014 14:03:41 -0600, Joseph wrote:
> I'm trying to clean up my home directory by locating large disk files.
> I used: find / -type f -size +2k -exec ls -lh {} \; | awk '{ print
> $8 ": " $5 }'
>
> but I'm getting strange output:
> 13:57: 194M
> 2011: 57M
> 17:05: 31M
File name
On Sun, 13 Jul 2014 14:03:41 -0600
Joseph wrote:
> I'm trying to clean up my home directory by locating large disk
> files. I used: find / -type f -size +2k -exec ls -lh {} \; | awk
> '{ print $8 ": " $5 }'
Take a look here regarding why you should never parse ls' output:
http://mywiki.woole
2014-07-13 14:19 GMT-06:00 Michael Orlitzky :
> On 07/13/2014 04:03 PM, Joseph wrote:
>> I'm trying to clean up my home directory by locating large disk files. I
>> used:
>> find / -type f -size +2k -exec ls -lh {} \; | awk '{ print $8 ": " $5 }'
>>
>> but I'm getting strange output:
>
> Just
On 140713 1403, Joseph wrote:
> I'm trying to clean up my home directory by locating large disk files. I used:
> find / -type f -size +2k -exec ls -lh {} \; | awk '{ print $8 ": " $5 }'
>
> but I'm getting strange output:
> 13:57: 194M
> ...
Try
find / -type f -size +2k -exec ls -lh {} \
On 07/13/2014 04:03 PM, Joseph wrote:
> I'm trying to clean up my home directory by locating large disk files. I used:
> find / -type f -size +2k -exec ls -lh {} \; | awk '{ print $8 ": " $5 }'
>
> but I'm getting strange output:
Just use "du -h" instead of "ls -lh" and awk:
find / -type f
On Sunday 13 July 2014 17:30:43 Mick wrote:
> On Sunday 13 Jul 2014 16:54:54 Dale wrote:
> > Dale wrote:
> > > Mick wrote:
> > >> Please try this: Go the PC that keeps getting these messages in its
> > >> logs. Run: $ chrony chronyc> password password:
> > >> If the passwd is wrong, or some
> > >>
I'm trying to clean up my home directory by locating large disk files. I used:
find / -type f -size +2k -exec ls -lh {} \; | awk '{ print $8 ": " $5 }'
but I'm getting strange output:
13:57: 194M
2011: 57M
17:05: 31M
2011: 27M
06:02: 41M
11:31: 21M
11:39: 28M
22:02: 62M
2012: 26M
12:53: 104M
On Sunday 13 Jul 2014 16:54:54 Dale wrote:
> Dale wrote:
> > Mick wrote:
> >> Please try this: Go the PC that keeps getting these messages in its
> >> logs. Run: $ chrony chronyc> password password:
> >> If the passwd is wrong, or some
> >> characters are incompatible with the terminal, then you w
Alan McKinnon wrote:
> On 10/07/2014 21:42, Dale wrote:
>> Alan McKinnon wrote:
>>> On 10/07/2014 20:11, List Reader wrote:
Okay, I see. Thank you so much. Soo so much. I thought I was going round
the twist, or hopelesly ignorant. I couln't understand why emerge didn't
offer me
Dale wrote:
> Mick wrote:
>> Please try this: Go the PC that keeps getting these messages in its
>> logs. Run: $ chrony chronyc> password password:
>> If the passwd is wrong, or some
>> characters are incompatible with the terminal, then you will get:
>> "Password: 501 Not authorised --- Reply not
Mick wrote:
> Please try this: Go the PC that keeps getting these messages in its
> logs. Run: $ chrony chronyc> password password:
> If the passwd is wrong, or some
> characters are incompatible with the terminal, then you will get:
> "Password: 501 Not authorised --- Reply not authenticated" You
I've been experimenting slow texstudio startup for long time, now I manage to
figure out why this would have happend.
using strace texstudio I was supprised that texstudio is scanning my while
disks ! I see a lot of statefs and openat and texstudio iterates the whole
root filesystem! no wonder
On Sunday 13 Jul 2014 10:20:47 Peter Humphrey wrote:
> On Tuesday 01 July 2014 15:01:33 I wrote:
> > On Tuesday 01 July 2014 12:13:39 Mick wrote:
> > > On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote:
> > > > Hell list,
> > > >
> > > > I don't know when it started, but recently I've been gett
Le 12/07/2014 16:59, James a écrit :
> Hervé Guillemet guillemet.org> writes:
>
>
>>> Reading these posts may suggest a compiled solution as your remedy?
>>> Naturally, you'll have to adjust what steps taken to your gentoo
>> environment.
>
>>> http://radu.cotescu.com/how-to-install-canon-lb
On Tuesday 01 July 2014 15:01:33 I wrote:
> On Tuesday 01 July 2014 12:13:39 Mick wrote:
> > On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote:
> > > Hell list,
> > >
> > > I don't know when it started, but recently I've been getting error
> > > e-mails
> > > from cron, thus:
> > >
> > > Passw
18 matches
Mail list logo
