Re: Problems with HylaFax 4.0pl1 on Solaris 2.4

["C.K." <cwk@ceres.fwcnetworks.com>]

I have had a similiar thing happen to me. All of a sudden my machine will

sync & crash and print some freaked out message about device xxxxx

and reboot, and boot back up in Single user mode and require for me to run

fsck manually on the faulty patition. Should I make the same device

(mknod ticlts c 105 2) for Solaris 2.4 in ~fax/dev ???

email : cwk@fwcnetworks.com
URL   : http://www.fwcnetworks.com/


On 23 Jul 1997, Morten Skjelland wrote:

> Nico Garcia <raoul@cirl.meei.harvard.edu> writes:
> 
> | *OOOOHHH*. Yes, you definitely cannot mount devices over the network.
> | It took me a bit of time under SunOS to find that one, and I didn't
> | even think of that problem for your situation.
> 
> Well, I figured it out, and it works ok now.  Is this in the doc
> somewhere?  If it isn't, it should be.
> 
> | >  There is also a missing device node: '$SPOOLDIR/dev/ticlts' 
> | > (mknod ticlts c 105 2) 
> | 
> | Hmm. It's not in the HylaFAX source code. What is this device for ?
> 
> It's used by flock and fcntl(...,F_SETLK,...).  If the device isn't there, this happens:
> 
> panic: lm_get_me: no ticlts
> syncing file systems... [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 [2] 2 done
>  4177 static and sysmap kernel pages
> ^MSunOS Release 5.5.1 Version Generic_103640-08 [UNIX(R) System V Release 4.0]
> [..]
> 
> :)
> 
> Morten
> -- 
> mortens@pvv.org
> Jeg lukker et øye og ser halvt.  Jeg lukker begge og ser alt.
>