Control: tags -1 + moreinfo Hello Dan Jacobson,
Sorry for the >decade late response. Slowly trying to work my way through open util-linux bug reports when I find the time. On Sat, Aug 27, 2005 at 04:46:45AM +0800, Dan Jacobson wrote: > Package: util-linux > Version: 2.12p-5 > Severity: minor > File: /usr/share/man/man8/getty.8.gz > > > In DIAGNOSTICS and FILES, perhaps mention that in fact errors seem to > go to /var/log/auth.log these days. (Even 'not a tty' ones.) > Else one can hardly find them.A The current manpage already documents that (depending on build-time configuration) the syslog(3) facility is used. What happens after this is completely up to the syslog daemon you have installed and how you have configured it! I don't think it's util-linux place to document all different syslog daemons shipped in debian and their configurations. You'll have to look at the documentation of the specific syslog daemon you're using for this information. > > In ARGUMENTS > port A path name relative to the /dev directory. > Mention what to do in the rare case we want to refer to things outside > the /dev directory. > Climb out with ../? The manpage already says "A path name relative to the /dev directory." This means ../foo would be a valid way to access /foo, as ../foo is the way to give the /foo path relative to /dev. If there was any sandboxing or other restrictions on the relative paths I would expect that to be documented (and if not then I expect no restrictions on relative paths). > use stdin "- < /where/ever"? That's a shell redirect. A pathname is not a shell command. If you execute 'getty - < /where/ever' in a shell it will work, but getty itself will only see the '-' argument and the shell will take care of sending in the /where/ever data over stdin. It thus depends on how you execute it. If you execute it from a shell, then you can ofcourse use shell functions. A notable counter-example is executing something from a systemd unit, which means it's executed directly and not via a shell and will thus fail if you try to use shell features (unless you explicitly launch a shell via "/bin/sh -c 'getty - < /where/ever'". > Also say if full path "/dev/ttyS0" is OK. It already says that the path has to be relative to /dev, which thus gives the answer no. I don't see anything that needs fixing in util-linux in this bug report. I'm thus considering (tagging it wontfix and) closing it. I hope the above information provided above has been atleast a bit informative. What do you think? Regards, Andreas Henriksson
