Community discussions

MikroTik App
 
User avatar
favincen
just joined
Topic Author
Posts: 21
Joined: Mon Jun 08, 2015 1:56 pm
Location: Grenoble, France

/file edit content shows empty content

Fri Jul 03, 2015 7:11 pm

Hello all,

This is my first post, as I'm digging into rOS for a pilot deployment.

I fail to edit content of big .rsc files in the CLI: a '/file edit filename.rsc content' provides me with an empty content, even-though the file in not empty. If I transfer the file to my laptop I can see and edit normally, but editing right within the rOS CLI doesn't work for large files.

Suspecting my files could be the issue I tested also with files generated by rOS, with same result: files generated by '/system default-configuration print file=default-conf' (8.1KiB) or '/export verbose file=export-verbose' (22.7KiB) also show empty content when usinf /file edit. :(
A smaller file (3.4KiB), export generated with non verbose export, is editable (although with a blank line between each line).

I'm running RouterOS 6.27 on 951G-2HnD.
I ssh to the box from the standard terminal of OSX 10.10.4 .

In a similar pattern, /file print details also fails to print content of the same 'large' files.

Any clue about what's going on ?
Thanks
Fabrice
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7167
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: /file edit content shows empty content

Mon Jul 06, 2015 12:54 pm

Edit from console is limited to 4KB.
 
User avatar
favincen
just joined
Topic Author
Posts: 21
Joined: Mon Jun 08, 2015 1:56 pm
Location: Grenoble, France

Re: /file edit content shows empty content

Mon Jul 06, 2015 1:31 pm

Edit from console is limited to 4KB.
Thanks for the answer, even though I would have prefer a solution... :shock:
I suggest this information to be added in http://wiki.mikrotik.com/wiki/Manual:System/File .
 
alexjhart
Member Candidate
Member Candidate
Posts: 198
Joined: Thu Jan 20, 2011 8:03 pm

Re: /file edit content shows empty content

Tue Jan 05, 2016 1:14 am

The better way to handle this (or in addition to wiki) is to throw an error in the console saying the file is too large.

I wish there was a way to handle reading larger files from the router...

Who is online

Users browsing this forum: greyline, MilanCermak, Mosmos and 22 guests