It's worse than I thought. Increments of 2 fail even when aa factor of 100 away from the limit:
kevin@plato-x:~$ seq 170141183460469231731687303715884105721 1 170141183460469231731687303715884105725 | head -10 170141183460469231731687303715884105721 170141183460469231731687303715884105722 170141183460469231731687303715884105723 170141183460469231731687303715884105724 170141183460469231731687303715884105725 kevin@plato-x:~$ seq 1701411834604692317316873037158841051 2 1701411834604692317316873037158841055 | head -10 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 kevin@plato-x:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799868 Title: seq command has problems near its max integer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1799868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
