Hi Tomas, Cheers for the response.
Ok - seems it would be useful to get to grips with 'chroot'. Also from recent posts it's not just me that finds printers a ball-ache. Would be happy with a quick dirty fix tbh. I know the Right thing would be to track it down and sort it properly but could I, for example, locate what's setting the 'no limit' and set that to 10ms? Or something. Jb On 12 June 2015 at 12:01, <to...@tuxteam.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, Jun 12, 2015 at 09:55:53AM +0100, Julian Brooks wrote: > > Hi all, > > > > I have this message > > "a start job is running for create volatile files and directories" > > when booting. There is then a "n's/no limit" while it counts up to approx > > 1m30'ish and then carries on booting. > > > > I'm pretty sure it's to do with installing printer drivers (from > searching > > around) but I'd like to keep the printer driver. > > > > How can I make this go away? > > Duckducking around, I find these, which might be relevant: > > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766092> > <http://forums.debian.net/viewtopic.php?f=10&t=118008> (currently > unreachable) > < > http://www.reddit.com/r/debian/comments/2jyquk/systemd_issue_at_boot_a_start_job_is_running_for/ > > > <https://forum.manjaro.org/index.php?topic=20077.0> > < > http://xyzmind.blogspot.com/2015/01/solving-start-job-is-running-for-create.html > > > > I didn't dive into all, but a very superficial perusal seems to suggest > an unhappy combination of systemd, wrong kernel version and/or too many > files in /tmp (yes, it sounds crazy). > > Oh, and... keep us posted :-) > > Hope that helps > - -- t > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > > iEYEARECAAYFAlV6vCQACgkQBcgs9XrR2kYOvQCaA4pMI1X2Xtr+rFAwipeVvCeK > ZxkAnjNjjoVPvkDuf9kL1e+0L2KN4E+S > =IzfU > -----END PGP SIGNATURE----- >
